Development/Priorities: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
RobertKaye (talk | contribs) No edit summary |
RobertKaye (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
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. |
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. |
||
| ⚫ | |||
== Summer/Autumn 2016 == |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
# '''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. |
# '''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. |
||
# '''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. |
# '''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 == |
|||
=== MusicBrainz/CAA === |
|||
# '''Move all services into Docker''': Work to dockerize all of our services. Follow our [https://docs.google.com/document/d/1PEc2Qst2plvuAuU9VvfQIBFAY9Q7FPDwzyaUg7me3uM/edit planning here]. |
|||
# '''Test new services in Docker''': Test at Google Cloud, initially. Then order machines from New Hosting company and start moving in there. |
|||
# '''SOLR''': Finish debugging and deploy new search infrastructure |
|||
# '''Move to New Hosting company''': Fully move all services to new host. |
|||
# '''Site performance''': Use insights from analytics to prioritize tasks for site performance improvements |
|||
# '''Fixes/Features''': Continue fixing issues and implement new features based on community feedback. |
|||
# '''MBS-1801''': Write new specification document about site-wide communication and notifications. |
|||
=== ListenBrainz/MessyBrainz === |
|||
# '''Beta site''': Finish the beta re-write of ListenBrainz. |
|||
# '''Test Beta site''': Create a public review site for the new version of ListenBrainz |
|||
# '''Release Beta site''': Push the new beta site live, with support for importing from alpha site. |
|||
# '''Big Query''': Start feeding data to BigQuery and start making data available to the public. |
|||
# '''Big Query based features''': Once data is available in BigQuery, start making end user features that give insights to user about their listening habits. |
|||
=== CritiqueBrainz === |
|||
Gentlecat: please add items. |
|||
=== AcousticBrainz === |
|||
Alastairp: please add items. |
|||
=== BookBrainz === |
|||
# '''Roadmap''': Plan roadmap to bring BB to minimally viable product to grow community. |
|||
LordSputnik: Please add items. |
|||
=== Sysadmin === |
|||
# '''Analytics''': Setup piwik to gain insights into our traffic |
|||
# '''Site performance''': Use insights from analytics to prioritize tasks for site performance improvements |
|||
# '''Backups''': Set up comprehensive back-ups of our NewHost servers. |
|||
# '''API Keys''': Support API keys and different rate limits on our APIs. |
# '''API Keys''': Support API keys and different rate limits on our APIs. |
||
[[Category:Development]] |
[[Category:Development]] |
||
Revision as of 11:53, 2 February 2017
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
- 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.
- 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
MusicBrainz/CAA
- SOLR: Finish debugging and deploy new search infrastructure
- Site performance: Use insights from analytics to prioritize tasks for site performance improvements
- Fixes/Features: Continue fixing issues and implement new features based on community feedback.
- MBS-1801: Write new specification document about site-wide communication and notifications.
ListenBrainz/MessyBrainz
- Beta site: Finish the beta re-write of ListenBrainz.
- Test Beta site: Create a public review site for the new version of ListenBrainz
- Release Beta site: Push the new beta site live, with support for importing from alpha site.
- Big Query: Start feeding data to BigQuery and start making data available to the public.
- Big Query based features: Once data is available in BigQuery, start making end user features that give insights to user about their listening habits.
CritiqueBrainz
Gentlecat: please add items.
AcousticBrainz
Alastairp: please add items.
BookBrainz
- Roadmap: Plan roadmap to bring BB to minimally viable product to grow community.
LordSputnik: Please add items.
Sysadmin
- Analytics: Setup piwik to gain insights into our traffic
- Site performance: Use insights from analytics to prioritize tasks for site performance improvements
- Backups: Set up comprehensive back-ups of our NewHost servers.
- API Keys: Support API keys and different rate limits on our APIs.
