Trello migration preparations

[sado1]

We want to migrate from Trello to Github. Let's discuss and fix current pain points. Disclaimer, I do not have much experience with Github's toolset.

1. I (and Ritter?) lack following permissions, without which I won't be able to manage tickets anymore:

• closing issues
• setting issue details - assigning myself/others, labels, etc.
• access to create and use Milestones (to manage our release cycle)
• Projects (to manage dashboards/roadmaps)

2. Issues don't have a description field.

• I think we could just edit first post.
• In case of user-created issues, it's good to keep the original post's copy at the bottom.

3. Shame there's no such thing as issue priorities, actually Trello has the same issue now (a plugin we used became paid).
   But we can use Projects, Milestones and/or priority-like issue labels - need to figure out a comfortable workflow.

[Kromster80]

Trello pros:

• good for certain workflows when amount of cards is small (e.g. pre-release planning)
• allows for spatial management (cards can be manually placed and ordered in categories)
  Trello cons:
• it struggles performance-wise with the amount of tickets we have
• it has a lot of unnecessary visual noise
• is a Kanban board, not an issue tracker by heart
• filtering and search are somewhat clumsy

Unrelated to that Trello board is used for several different purposes now (bug tracker, work planner, legend, instructions, drafts). This could be a good time to sort that out.

For the github issues we have two options:

• use Reys repo
• use separate repo (new or at KP-Wiki org)

Permissions to edit and manage issues will be easy to give out.
Editing first post is fine here (posts retain edit history too).
User-posts can be kept above the line and our details can be edited after the line.
Priorities can be done with labels (e.g. "top priority" label)