Design Summit

At OpenStack Design Summits the community gathers to discuss the requirements for the next release, learn more about OpenStack, and connect with community members.

Next summit

The next Design Summit is planned for November 9th-12th at the Weston Centre in Downtown San Antonio, TX (112 E. Pecan St. San Antonio, TX 78205).

How do the developer tracks of the summit work ?

The developer tracks at the Openstack Design Summit are modeled after Ubuntu Developer Summits. Features for the next release cycle are discussed in summit sessions. A set of 55-min sessions are scheduled. Those sessions are not formal presentations but rather open discussions on a given subject or feature. If you care about a particular subject, please join. Due to the nature of the event, the schedule is a bit dynamic, so check out the summit schedule pages often (link pending).

Each session is moderated by a session lead. You can identify him as being the Drafter of the corresponding Launchpad blueprint.

Summit preparation, for session leads

You should file a Launchpad blueprint for each subject (one blueprint = one 55-min session)
- Click here to register a new blueprint for ODS Bexar
- Under For, choose the appropriate project (nova, swift, or openstack-dev for common discussions)
- Under Name, enter $release-$feature (with dashes for space). For example, bexar-release-schedule or austin-stats-utilization
- Under Title, name the feature. The name will appear in the schedule, so try to keep it concise :)
- Under Summary, write a short description of the feature. This should give people a good idea of what the feature is about and what will be discussed during that session.
- Under Drafter, enter the Launchpad ID of the session lead (that should be you)
- Under Approver, choose dendrobates (our very own Rick Clark)
- If you registered the spec directly under the project, you'll have a Propose for sprint drop-down. Select the Openstack Design Summit. This is done automatically if you used the above link.
- Click Register Blueprint, and you're done !
The blueprint will be reviewed by the meeting organizer and accepted or denied for the summit.
You should use the Whiteboard area on the blueprint to outline the agenda of the session.

Summit registration, for all attendees

Unfortunately, you need to register in two places:

In the general Openstack Design Summit registration at http://www.openstack.org/register
On Launchpad, by following this link: https://launchpad.net/sprints/ods-b/+attend

This secondary registration will allow you to subscribe to the technical sessions you're interested in. The sessions scheduling system will try to avoid double-booking you in parallel sessions in which you're marked essential to the discussion.

To mark yourself essential to a discussion:

Look up the list of already scheduled blueprints
For the blueprints where your participation to the session is essential, click on the Subscribe link
Check the Participation essential (Required) checkbox
Click on Subscribe, and you're done.

Remember, this will only work if you register yourself in Launchpad as attending the summit (see above).

At the summit

The schedule for the technical tracks will be available at: (URL pending)
The session should start on time, be there or be square
The session lead starts by introducing clearly what the session is about (and what it is not about) to set expectations
It is the responsibility of the session lead to keep the discussion live and on-topic
Make the best use of those high-bandwidth 55 minutes !
Collaborative note taking during the session should be done through http://etherpad.openstack.org, please participate and make sure your points are reported there
Add a link to the etherpad doc from the session blueprint whiteboard, for reference
15 minutes before the end of the session, the session lead should start making sure he gets clear outcomes, work items and actions from the session
End on time, to give participants the time to switch rooms to the next session if needed
If you want to continue that discussion, you should schedule an informal session during the hacking days (Thursday & Friday) with interested folks

History

These pages contain information and notes from the Summits so far: