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. |
||
== |
== Winter 2015/2016 == |
||
For |
For winter 2015/2016, the following priorities exist for the dev team, in order of most important to least important: (most of these have been carried over from summer, since these are big goals) |
||
# '''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. |
|||
# '''Community improvement features:''' The only new features that we're going to focus on in the short term are features that address problems within our community. (e.g. MBS-1801) |
|||
# '''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 |
# '''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. |
# '''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 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:''' |
# '''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. |
||
'''Important note:''' We are not going to have a schema change release near October 15th. We're now well into summer and we still have not finished the schema change release UI from the last release. We really need a break from schema changes to focus on community related features. |
|||
[[Category:Development]] |
[[Category:Development]] |
||
Revision as of 21:10, 23 November 2015
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.
Winter 2015/2016
For winter 2015/2016, the following priorities exist for the dev team, in order of most important to least important: (most of these have been carried over from summer, since these are big goals)
- 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.
- 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.
