SpecProcess

Differences between revisions 1 and 12 (spanning 11 versions)
Revision 1 as of 2005-04-27 03:12:30
Size: 2486
Editor: intern146
Comment: Initial submission for editing
Revision 12 as of 2006-09-12 10:01:15
Size: 46
Editor: host58-228-static
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= SpecProcess =

== Status ==

 * Created: 2005-04-27 by TollefFogHeen
 * Priority: NeedsPriority
 * People: ColinCharlesQueue
 * Contributors: TollefFogHeen
 * Interested:
 * Status: BrainDump, UbuntuSpecification, NewSpec
 * Branch:
 * Malone Bug:
 * Packages:
 * Depends:
 * Dependents:
 [[FullSearch(SpecProcess)]]
 * UduSessions: 0

== Introduction ==

From a spec is "born" until it is accepted and implemented is a big and underdocumented process. Every specification should go through the life cycle as described in this specification.

== Rationale ==

As the Ubuntu community move to a more specification-based process, a specification for the process itself is needed so everybody knows what the process should work like. The current process is fragmented and people seem to be confused with regards to what the proper process is. This causes excessive overhead and may cause specifications to be delayed unneededly.

== Scope and Use Cases ==

The implementation of a spec is out of scope at this point.

 * A new idea is proposed and goes through the full process.

== Implementation Plan ==

 * A new specification is made, based on the SpecSpec template.

 * One or more BOFs are conducted. Discussion takes place.

 * The lead and/or second writes up the notes for the BOF. At this point the Status field should include "DraftSpec" and CommunitySpecification, DistroSpecification or LaunchPadSpecification. ColinCharlesQueue or SimonSharwoodQueue should be added to the list of People. They will review and edit the specification for clarity, spelling and grammar.

    * If the specification needs further cleanup, it will be sent back by the editors. This is done by adding "Queue" to the end of the name of the lead and the second along with comments on what changes are needed.

 * Once the lead and second are happy with the changes as they come back from the editors, they change the state to EditedSpecification and go to the Global room and move the post-it note.

 * MattZimmerman or MarkShuttleworth then review the specification and move it to the ApprovedSpecification state by moving the post-it note and changing the state on the wiki.

 * The specification is implemented.

=== Data Preservation and Migration ===

N/A

=== Packages Affected ===

N/A

=== User Interface Requirements ===

Using the wiki.

== Outstanding Issues ==

=== UDU BOF Agenda ===

=== UDU Pre-Work ===
See FeatureSpecifications and SpecLifeCycle.

SpecProcess (last edited 2008-08-06 16:39:29 by localhost)