Differences between revisions 2 and 16 (spanning 14 versions)
Revision 2 as of 2009-02-20 17:03:34
Size: 7198
Editor: 71
Revision 16 as of 2009-04-08 18:40:54
Size: 4898
Editor: c-68-40-250-14
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

Line 3: Line 6:
 * '''Where:''' Palau de Congressos de Catalunya, http://www.hrjuancarlos.com/en/600.htm Barcelona, Spain  * '''Where:''' Palau de Congressos de Catalunya, http://www.pcongresos.com/en/index.php Barcelona, Spain
Line 19: Line 22:
== Lodgings ==

Sponsored attendees will be staying at the Palau de Congressos de Catalunya, http://www.hrjuancarlos.com/en/600.htm. Please see Jorge's email for more details.

For those of you who wish to attend on your own, we have a special rate that is available on a first come, first serve basis based on availability. Please fill out _this form_ and email or fax it to the contact information on the form.
Line 31: Line 28:
== Attendance ==
Line 33: Line 29:
 1. Make sure you have a Launchpad account. == Proposing Blueprints for Discussion ==
Line 35: Line 31:
   Visit https://launchpad.net/, if you don't have an account click "Log in / Register" in the top-right and enter your e-mail address in the appropriate box. If you do have an account, make sure you can Log in.

 1. Confirm your attendance.

   Visit https://launchpad.net/sprints/uds-karmic/+attend and check that the dates and times match when you'll be at UDS. Click the "Register" button. It's safe to do this even if you've done it before, so it's a good idea to do it anyway.

 1. Express interest in tracks and topics.

   Visit http://summit.ubuntu.com/uds-karmic/interest (you may have to wait a few minutes if you've just confirmed your attendance). Select any tracks and topics that interest you - we'll use this to
   generate a personal schedule for you with matching meetings on it.

 1. Subscribe to specifications.

   While it's a bit bare at the moment, as we put together the UDS schedule, https://blueprints.launchpad.net/sprints/uds-karmic will be filled with the blueprints that will be discussed there. Select blueprints that interest you, and click the "Subscribe yourself" link on the right hand side of the blueprint page.

   You'll be mailed of any changes to the blueprint, and we'll make sure it appears on your personal schedule.

 1. Add yourself to the [[UDSKarmic/Attendees|detailed list]] - This helps to plan ride sharing to and from the airport, and let's people know who you are affiliated with when you attend.

If you cannot attend in person, you can still listen to the conferences or take part in them remotely. More information will be made available close to the conference date.

For example, listen in via icecast: http://icecast.ubuntu.com/

== Blueprints and discussions ==

We're still putting together the schedule for the seven usual tracks, but we have ten rooms to fill with discussions! That's where you come in.

There's almost certainly a development project that interests you that is not already on the UDS specification list:
If there is a blueprint that you would like to propose for discussion that is not already on the UDS specification list:
Line 78: Line 46:
The deadline for proposals to be received is 4 March, at that time I'll begin reviewing the proposed list and accepting discussions onto the schedule. 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.

Room specific IRC channels:

  • Fill room in here


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:

  1. 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)
  2. Go to https://blueprints.launchpad.net/sprints/uds-karmic and make sure that your specification (or a similar one) has not already been scheduled.

  3. Go to https://blueprints.launchpad.net/ubuntu/ and click the "Register a blueprint" button.

  4. 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).

  5. Add a link to your spec to /Discussions

  6. 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!

UDSKarmic (last edited 2009-07-08 18:01:19 by host-163-62-107-208)