In an effort to bring the community into our development process more, I (ocharles) have built a new little application to help the MusicBrainz community decide exactly what we should focus on. I present to you, the Scheduling Game!
The idea behind this little application is to let the community quickly scan through open issues and decide when they believe they should be fixed. Each editor is presented with 3 options:
- Within 3 months. This ticket must absolutely be fixed within 3 months from now.
- Within 12 months. This ticket should be fixed within a year from now. This means the ticket should be fixed within the year, but is not critical for the next 3 months
- Unscheduled. This issue is not pressing and can be fixed much later.
Later, when issues have been voted on by enough people, the developers will try and decide how to schedule work to best fit the needs of the community.
A few disclaimers… Firstly, this is just an experiment! We don’t know how well it will work, though initial testing has shown it to already be quite useful. Secondly, it’s not really much of a game, but I wanted to give it a cute name (I know how picky everyone can be!). Currently only a subset of open tickets are available for voting on – specifically tickets in the “NGS + 1” and “Post NGS” milestones on JIRA, as these milestones are in need of a sorting.
The scheduling game is currently live on my server at http://scheduling.ocharles.org.uk/. You can have a look at the current (anonymous) votes at http://scheduling.ocharles.org.uk/results. If you have any questions or comments, you can reach me in IRC as ocharles or email firstname.lastname@example.org. Happy voting!