Almost done redoing this badboy ...
|Deletions are marked like this.||Additions are marked like this.|
|Line 9:||Line 9:|
What: Ubuntu Developer Summit for version 9.10
Where: Palau de Congressos de Catalunya, Barcelona, Spain
Hotel: Hotel Rey Juan Carlos
When: Monday 25 May - Friday 29 May 2009
At the beginning of a new development cycle, Ubuntu developers from around the world gather to help shape and scope the next release of Ubuntu. The summit is open to the public, but it is not a conference, exhibition or other audience-oriented event. Rather, it is an opportunity for Ubuntu developers -- who usually collaborate online -- to work together in person on specific tasks.
Small groups of developers will participate in short Forum and Workshop (formerly called "BoF"/Birds-of-a-Feather) sessions. This allow a single project is discussed and documented in a written specification. These specifications will be used for planning the new release of Ubuntu, as described in FeatureSpecifications and TimeBasedReleases.
Proposing Blueprints for Discussion
If there is a blueprint that you would like to propose for discussion that is not already on the UDS specification list:
Subject to a few constraints, it'd be great if you could register your own blueprints and propose them for discussion. We'll have our magic auto-scheduler find time for the required people in one of the spare rooms.
The constraints are:
- the specification must be assigned to somebody attending UDS
- that person must have agreed to implement the specification
- (ie. don't assign it to someone who you saw on a mailing list without asking!)
- all required participants are attending UDS, or able to participate remotely
The deadline for proposals to be received is 31 March, at that time we'll begin reviewing the proposed list and accepting chosen discussions onto the schedule.
(If you miss the deadline, there will likely still be plenty of time and space at UDS to have your discussion - it just won't appear on the official schedule).
Here's what you need to do:
- Make sure you have a Launchpad account, that you've confirmed your attendance to UDS and expressed interest in relevant tracks and topics. (See above)
Go to https://blueprints.launchpad.net/sprints/uds-karmic and make sure that your specification (or a similar one) has not already been scheduled.
Go to https://blueprints.launchpad.net/ubuntu/ and click the "Register a blueprint" button.
Fill out this form, with the following particulars:
Name: the "launchpad name" of the blueprint, it's common practice to begin this with the release name if it's an ongoing development effort. karmic-mono-flamewar
Title: a more human-readable title equivalent of the name. e.g. "Improved iPhone support", "Remove Mono Flamewar"
Specification URL: a wiki URL to the specification, common practice is to turn the "launchpad name" into a Wiki name. e.g. http://wiki.ubuntu.com/Specs/ImprovedIphoneSupport, http://wiki.ubuntu.com/Specs/KarmicMonoFlamewar
The URL should be created with the SpecTemplate but you should *not* start writing it yet! You need to have the discussion first!
Summary: a single paragraph summary to explain what you want to discuss and/or implement.
Definition Status: set this to "Discussion"
Assignee: this must be set to somebody attending UDS, and should often be yourself. Don't assign a spec to someone without asking them if they're willing to implement it first!
Drafter, Approver: leave these blank.
Propose for sprint: UDS Karmic Koala.
(if you already have a blueprint registered, you need to make sure the details match the above, and use the "Propose for sprint") link on the right).
Add a link to your spec to /Discussions
- You probably want more than just yourself to attend, otherwise it'll be a lonely discussion. Give your Launchpad URL to people and ask if they would use the "Subscribe yourself" link to express interest.
- They may use "Participation essential" if they absolutely want to come, this will only allow the discussion to take place when all "essential" parties are available. Beware though, the more essential people, the harder it is to schedule!