github vs. trello

github-trello.md

Github

Pros

• Pull requests are the thing for getting dev done, seeing what others have done, and discussing it. I love pull requests.

Cons

• Developer-centric workflow that doesn't provide much value to the rest of the business, because it has no interest in that at all.
• Not particularly flexible organization of anything, milestones are a bit clunky to use, so it's mostly just labels.

Neutral

• Individual issues are a pretty good place for discussion, but not a killer feature at all like PRs.

Trello

Pros

• Great for all sorts of business processes, including, but far from limited to, product related things.
• Very flexible organization with three dimensions: board, list, label.
• Ordering of things within lists is killer feature.

Cons

• No pull requests and weak integration ("just post a link!").
• Code snippets don't look as good (no syntax highlighting).

Neutral (or perhaps still cons, not sure yet)

• Are cards as good for discussion as issues are? Maybe, but I'm not sure. Comments flow the opposite direction, everything is narrower because it's a modal instead of a page, and you can only attach images to cards themselves, rather than inline them in comments

As of today would you recommend using Trello for managing code projects (I'm concerned that GitHub issues are gone if I move my repo elsewhere), or it's 100% GitHub issues now? I'm managing a bunch of minor FOSS projects.

Still relevant?

GitHub now has projects and milestones that allow for categorising and ordering issues.