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 == |
||
For |
For Summer/Autumn 2016, 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. |
# '''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. |
||
# '''Making more edits auto-edits''': We've started the process of making more edits auto-edits. This will require a number of new features/tweaks to existing features in order to ensure that our data quality does not suffer as a result of this. Bitmap is taking charge of this process and listening to community feedback. |
|||
# '''In-site communication/notifications''': MBS-1801 implementation using XMPP to allow users of all of ours sites to easily use in-site communication. This is Gentlecat's primary project, currently. |
|||
# '''Bug fixing/finishing existing features:''' Fixing bugs or finishing tasks left over from the May 2015 schema change. |
|||
# '''Apply new branding to musicbrainz.org:''' In lieu of moving to a full bootstrapped site, we should do minor cosmetic changes to the existing header bar and update the site to use the new MusicBrainz colors. |
|||
# '''New features:''' Creating new features or starting new sub-projects should not be considered this summer, since we have a lot of things that are higher priorities. |
|||
# '''New schema change features:''' Our next schema change release will be May 2016, so we have nothing really new on this front for right now. |
|||
=== Focus tasks === |
|||
# '''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. |
|||
# '''Move to New Hosting company''': Fully move all services to new host. |
|||
# '''API Keys''': Support API keys and different rate limits on our APIs. |
|||
[[Category:Development]] |
[[Category:Development]] |
||
Revision as of 09:51, 19 August 2016
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
For Summer/Autumn 2016, 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 tasks
- Move all services into Docker: Work to dockerize all of our services. Follow our planning here.
- Test new services in Docker: Test at Google Cloud, initially. Then order machines from New Hosting company and start moving in there.
- Move to New Hosting company: Fully move all services to new host.
- API Keys: Support API keys and different rate limits on our APIs.
