Hacker News Reader

Comment by rushabh | Hacker News Reader

This may sound crazy but we manage our entire SAAS and open source project with GitHub Issues. We have monthly milestones and assignments and seems to work well for our team of 15 devs. Where we are hurting is managing multiple projects.

It would be awesome is if GitHub would allow us to set milestones across repos. Then we don’t really need anything else.

View on HN

It sounds entirely reasonable. One way of reading the popularity of Agile is simply that it is a vehicle for non-creators to get their head around dealing with todo lists, testing, documentation and releases. Github is great at all of that.

There are tools to help you with multi repo GitHub issue management. A little bit of a plug but https://codetree.com is built to solve your exact problem - we sync up milestones (and labels) across many repos and allow you to visualize and work with cross-repo issues in either kanban or list view.

Right, we've been using ZenHub's issue board on top of our dozens of GitHub repos to do something that is Kanban-ish. It works well enough for the teams that actually want to follow a process.

With open source, it can be frustrating when other loosely coupled teams and silos have a dependency for a release, but their overall issue-tracking process is mostly an abandoned in place mock-up or fiction. If their repo is included in our board, their issues show up as noise across the whole pipeline. You start remembering to ignore certain issues that you know don't reflect reality, then ignoring everything for certain assignees or reporters, and eventually decide to toggle off their repo from your board view.

Reply on news.ycombinator.com