FeatureDefinition

Differences between revisions 15 and 16
⇤ ← Revision 15 as of 2014-05-08 09:17:46 →
Size: 1831
Editor: 83
Comment:
← Revision 16 as of 2014-05-08 09:19:27 → ⇥
Size: 1864
Editor: 83
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
 * If a feature spec is not objected, it is automatically approved.
 * If a feature is objected by anyone, it needs to be discussed within the community. ubuntustudio-core team has last say - whose responsibility lies in upholding the quality and integrity of Ubuntu Studio.		  * If a feature spec is not objected, it will automatically be approved.
 * If a feature is objected by anyone, it needs to be discussed within the community. If no resolution is found, ubuntustudio-core team, whose responsibility lies in upholding the quality and integrity of Ubuntu Studio, has last say .

In the beginning of a development we do feature definition.

Tasks during feature definition

week 1-8

Discuss on mail list, irc and social channels about feature additions. Collect ideas - preferably directly to lp blueprint specifications. Call for developers to participate during this whole period.

week 8-9

finalize blueprints at around week 4, and have them approved before FeatureDefinitionFreeze

Making Feature Specifications (blueprints)

Planning of feature changes is done primarily by the use of feature specifications in the form of blueprints at http://launchpad.net. See our Blueprints page for an oversight of our active blueprints.

Suggesting changes

Anyone can suggest a feature change/addition. But, to make it a reality, someone needs to implement it. Usually the one who does the work is the same person that makes the suggestion.

Creating Blueprints

Blueprints are created for projects, and the blueprint should be created by the driver of that project (typically ubuntustudio-dev, or ubuntustudio-art), or the owner (typically ubuntustudio-core).

Approving Feature Specs

  • If a feature spec is not objected, it will automatically be approved.
  • If a feature is objected by anyone, it needs to be discussed within the community. If no resolution is found, ubuntustudio-core team, whose responsibility lies in upholding the quality and integrity of Ubuntu Studio, has last say .
  • If a feature spec will break something in Ubuntu, it may be disapproved by the ubuntustudio-core team. Also, it will most probably be disapproved later by Ubuntu devs anyway.

UbuntuStudio/DevEvents/FeatureDefinition (last edited 2014-05-08 09:42:06 by 83)