Categorization of Issues on Github

[kareila]

Hi all! During Saturday's dev chat, one of the discussions that came up was the current status of our work on improving the process of using Github Issues as our bug tracker.

Here is where we are right now:

It is now possible for anyone to use inline text tags to categorize new issues. fu has put up a rough draft of the instructions for this process, along with a list of the labels that are currently recognized. We are also planning to allow issues to be "claimed" in a similar manner, although the format for doing that hasn't been finalized yet.

Another part of Github Issues that we've been experimenting with is the use of milestones. If you look at the milestones on dw-free you can see, for example, the status of open bugs on certain major projects like Foundation and mobile styles. I think this could be really useful, especially in light of recent comments saying that we haven't been doing a good job of communicating the progress of our major development projects within the development community.

There are also other milestones currently displayed on that page such as "unclaimed", "curated", and "in progress" - a lively discussion ensued as to whether these would be better used as tags instead of milestones, and I'd like to continue that discussion below. The main issue with milestones on Github in general is that a bug cannot be assigned to more than one milestone. From a workflow perspective, we would expect to see a progression of untriaged -> unassigned -> claimed/in progress -> pull request -> closed, and the fact that an issue cannot exist in more than one of those states at a time makes it a good candidate for the use of milestones - but could conflict with using milestones for the purpose of tracking large projects.

There was also a great deal of confusion as to what "curated" was supposed to mean in this context. mark said what he desired was a list of three or so "top priority" unclaimed bugs, so that he could easily decide what to spend his limited time on. Again, this may be a better candidate for a tag than a milestone, and maybe with a label that is easier to interpret.

The last issue mentioned is that we still haven't come up with tags for indicating which area of the code is involved with a bug (e.g. styles, notifications, etc.), which is something we relied on pretty heavily with our previous Bugzilla setup in order to find new things to work on.

Please continue the discussion in comments!

Comments

[alierak]

Something tells me the milestones page won't necessarily help with communication if it thinks we're 100% done with the Foundation conversion. I guess we'd have to plan out all the changes and open bugs for them ahead of time to conform with the implied expectations of GitHub.

[kareila]

I think it's less important to conform with the implied expectations of Github, and more important to manage our own expectations. In this case I believe the project of getting Foundation ready to use on the live site /is/ 100% done, and migrating other pages can happen gradually, adding to the milestone as more issues/PRs are opened.

[afuna]

I am not too fussed by that; I think it's useful to give a sense of progress if you've been working on something long-running, but we should be able to just open new bugs in a milestone at any time.

I'm against opening an issue for all pages that need foundation conversion though. That would flood our bug tracker unfortunately.