From MusicBrainz Wiki
< Development
Revision as of 11:58, 2 February 2017 by Gentlecat (talk | contribs) (Sysadmin)

This page attempts to outline the development team's priorities in broad strokes -- this priority list should serve as a general guideline for our team to decide what to work on when the weekly dev meetings don't provide enough guidance.

For Winter 2017, the following priorities exist for the dev team, in order of most important to least important:

Ongoing tasks

  1. Site stability and performance issues: If the site is misbehaving or not performing as it should, the dev team should focus on resolving those issues as the first priority.
  2. ModBot/Nagios: If ModBot or Nagios sends periodic emails about an issue, the dev team should address these issues quickly. ModBot fixes may not require hot-fixes, but they should be addressed as soon as possible.

Focus areas


  1. SOLR: Finish debugging and deploy new search infrastructure
  2. Site performance: Use insights from analytics to prioritize tasks for site performance improvements
  3. Fixes/Features: Continue fixing issues and implement new features based on community feedback.
  4. MBS-1801: Write new specification document about site-wide communication and notifications.


  1. Beta site: Finish the beta re-write of ListenBrainz.
  2. Test Beta site: Create a public review site for the new version of ListenBrainz
  3. Release Beta site: Push the new beta site live, with support for importing from alpha site.
  4. Big Query: Start feeding data to BigQuery and start making data available to the public.
  5. Big Query based features: Once data is available in BigQuery, start making end user features that give insights to user about their listening habits.


Gentlecat: please add items.


Alastairp: please add items.


  1. Roadmap: Plan roadmap to bring BB to minimally viable product to grow community.

LordSputnik: Please add items.


  1. Analytics: Setup piwik to gain insights into our traffic
  2. Site performance: Use insights from analytics to prioritize tasks for site performance improvements
  3. Backups: Set up comprehensive back-ups of our NewHost servers (and make sure that they work).
  4. API Keys: Support API keys and different rate limits on our APIs.