Blueprints are vital inputs into Ubuntu planning. They serve the following purposes:

  1. Transparently communicate the possibility of doing some work.
  2. Offer a place for the community and users to comment on the possible work.
  3. Facilitate discussion at UDS.
  4. Capture desicions at UDS.
  5. Provide a link to details about the work (a "spec")
  6. Communicate commitement the community, to users, and to partners within Canonical to accomplish such work.
  7. Provide a means for tracking progress against that work.


Blueprint List: April 13th

By this date everyone should have a list of one or more blueprints they would like to pursue, and have reviewed that list with their techlead (seb128).

Blueprints registered: April 20

We've reviewed our list of blueprints. Now it's time to register them. To register a blueprint, please do the following:

  1. Go to

  2. use the correct convention for naming. Start each name "desktop-maverick-". So for example, I might name a blueprint "desktop-maverick-fun-ubuntu-pygtk-support". This naming convention is critical for supporting the planning steps later.
  3. Write a nice descriptive title.
  4. You may skip the summary for now, but it is typical to include a few sentences to explain the thrust of the blueprint.
  5. Typically, you will set yourself as the assignee and the drafter and seb128 as the approver
  6. Then choose "Propose for sprint: Ubuntu developer summit for the M release"

Click Register

Blueprints prioritized and accepted: April 23

seb128 and rickspencer3 will scrub priorities and accept for UDS.

The list of proposed blueprints will be viewable at this link:

seb128 and rickspencer3 will set the priorities for each blueprint. Typically blueprints set for Essential or High priority will be discussed at UDS.

However, some blueprints will get rejected for UDS, though the work will still happen. This typically occurs when:

  1. There is nothing to discuss on the blueprint, all decisions have been made or are trivial. No reason to waste time at UDS discussing such things.
  2. The right people to provide input into the blueprint won't be available at UDS. The discussion will happen in other forums.

Some blueprints will be accepted for UDS, but then won't be worked on. This typically happens because:

  1. The work is not deemed important or desirable in discussion at UDS.
  2. The blueprint is superseded by other blueprints.
  3. A lack of agreement on what to do or how to do it.
  4. The complexity, risk, or sheer amount of work is deemed too large for the user benefit.

The blueprints targeted for discussion at UDS will be viewable at this link:

Ultimately, all blueprints accepted for Maverick will be viewable here:

Blueprints complete: April 30

You should now have a set of assigned blueprints that are accepted for UDS. By this date, you need to do the following for each:

  1. Complete the summary so that you can use it to support a good discussion and decision making at UDS
  2. You can stub out specs and link them as appropriate as well
  3. Subscribe people who you would like to attend your session to your blueprint
  4. Subscribe people as essential if it is truly essential that they attend, use this feature in moderation

Schedule Complete: May 7

rickspencer3 and seb128 will schedule sessions up to this date. Note that rescheduling to accomedate last minute changes during UDS is common as well. If you have special scheduling requests, such as certain sessions on days when a certain upstream will be attending, etc... work with rickspencer3 and seb128 to make that happen.

Run your sessions: starting May 10

show up to UDS ready to run great sessions and make deciscions!

DesktopTeam/10.10/BlueprintingSchedule (last edited 2010-04-14 22:02:34 by 97-126-103-251)