Ubuntu Developer Summits are twice-annual events where developers from Ubuntu and other projects gather to plan the next Ubuntu release. They usually last one week, and are open to the public, but attendees are expected to participate in highly technical discussions and writing sessions.

Small groups of developers participate in short (45-60 minute) BOF sessions where a single project is discussed, and then document the outcome of the discussion in the form of a written specification. These specifications are used as the basis for planning the subsequent work of developing a new release of Ubuntu, as described in FeatureSpecifications and TimeBasedReleases.

List of Summits

See also EventsGlobal for a list including other events.

Preparing the Agenda

We manage the agenda for the developer summit in Blueprint, the launchpad feature specification tracker. You can check out the BlueprintDocumentation for more information on how you can use Blueprint to keep track of feature development and roadmaps. But the long and the short of it is that you need to register any topic in Blueprint as a spec for your product or for Ubuntu.

Then for each spec, you need to nominate it to the meeting agenda.

Now each meeting has a group of people (or a single person) who controls the agenda, and that person can accept or decline the topic for the meeting. The upshot is that you end up with a well-defined list of topics for this particular meeting.

Registering Attendance

Attendees should register their attendance at the sprint. Essentially they say when they will be there and available for meetings. This information is used for scheduling purposes.

Subscribing to topics

Attendees can look over the list of topics and subscribe to the ones they think are interesting. This tells us who to try and schedule to attend BOF sessions on those topics. We try to make sure that everybody gets to contribute to the topics in which they have an interest.

At the Summit

Generating the timetable

Each day we generate a timetable for the day's discussions, based on progress which was made the previous day and attempting to cover as many of the most important topics as possible. We try to ensure that there is time to write up the conclusions of a particular discussion session so that the ideas covered are written up in a way that everyone can follow and reach agreement on what was said. The idea is to go home with hard plans in writing on each of these topics, so that the community can have a strong sense of what is actually being planned.

BOF sessions

See BOFHowto.

DeveloperSummit (last edited 2012-10-21 21:11:55 by c-76-25-23-72)