search

Peeragogy / ReadingGroup

Repository for the 2019 Peeragogy Handbook reading group
0 stars 0 forks source link

Create a useful way to manage issues for the Peeragogy project #1

Open holtzermann17 opened 4 years ago

holtzermann17 commented 4 years ago

In discussions and experiments with @skreutzer we have tried:

  1. Tasks inside of a shared Google Group
  2. Tasks inside of a Github issue tracker
  3. Huboard, a kanban-style overlay connected to said issue tracker
  4. Clubhouse, a stand-alone kanban-style system
  5. @skreutzer and I have also both used Org mode, in separate projects

There may be other options. I propose that we go with 2 and 3 for now. This issue is here to discuss these matters further. Meanwhile, new issues can be created in this otherwise empty repository.

holtzermann17 commented 4 years ago

Here is a link to the current repo reflected on HuBoard: https://huboard.com/Peeragogy/ReadingGroup/

Here is a link to the toplevel peeragogy.github.io repo reflected on HuBoard: https://huboard.com/Peeragogy/Peeragogy.github.io/

daytripper commented 4 years ago

Thanks for clarifying that Joe. My feeling is we should use the Google Group for more general discussions and some onboarding of newcomers.

On Sat, Nov 23, 2019, 4:09 PM Joe Corneli notifications@github.com wrote:

In discussions and experiments with @skreutzer https://github.com/skreutzer we have tried:

  1. Tasks inside of a shared Google Group
  2. Tasks inside of a Github issue tracker
  3. Huboard, a kanban-style overlay connected to said issue tracker
  4. Clubhouse, a stand-alone kanban-style system
  5. @skreutzer https://github.com/skreutzer and I have also both used Org mode, in separate projects

There may be other options. I propose that we go with 2 and 3 for now. This issue is here to discuss these matters further. Meanwhile, new issues can be created in this otherwise empty repository.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Peeragogy/ReadingGroup/issues/1?email_source=notifications&email_token=AAZPUM6MEYJPY3VDB4TKOELQVGLXTA5CNFSM4JQ36AH2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3SV5TA, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZPUM5AMHRCTWU3OZ7DEDDQVGLXTANCNFSM4JQ36AHQ .

holtzermann17 commented 4 years ago

In case it’s useful for you too: I just installed a iPhone app called GitHawk that shows all of the issues on GitHub repositories that I have been involved with. This seems kind of nice because it gives a way to keep track of issues that’s similar to an email inbox but that is not clogging up my other email.

Sent with GitHawk

skreutzer commented 4 years ago

Let's just use whatever works to get issues collected, work on them organized/coordinated and tasks actually completed. The problem is of course that there are many different and incompatible personal preferences, and the tools don't work together (for proprietary/business reasons). Ideally, every tool would publicly publish or offer export of issues in a semantic format. GitHub seems to be relatively fine via its API. More problematic is the import (for synchronization of changes made elsewhere, not to speak of merging, where it is beyond me why GitHub isn't managing issues just like regular repositories with forking, pull requests and merging) where one has to do authentication for their API (ideally OAuth) and program against their API logic, while a simple upload or pull from an URL could avoid application logic and make the online/offline tools just operate on semantic data. At least, with the GitHub API, we could create overviews, dashboards, card boards, (RSS) feeds and what not relatively cheaply, to gain/keep overview.