At Design Summits the developers community gathers to discuss the requirements for the next release and connect with other community members. The OpenStack Foundation offers a Travel Support Program to help cover travel expenses.
Next Design Summit
- "K" release Design Summit, November 3-7, 2014 in Paris, France. See summit-specific details at openstack.org.
Previous Design Summit
- Juno Design Summit, May 13-16, 2014 in Atlanta. See summit-specific details at Summit/Juno.
How does the Design Summit work?
The Design Summit is a part of the OpenStack Summit. It is not a classic conference track with speakers and presentations. Developers suggest session ideas to discuss upcoming features for the next release cycle, which get reviewed and scheduled by the program technical leads (PTLs). Those sessions can include the presentation of a few slides but are generally a 40-min long, open brainstorming discussion 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.
If you suggest a session, you should be ready to moderate that session and make sure the discussion stays on track. Experienced developers will generally help in that endeavor, but you should plan to attend that session yourself.
The Design Summit is not the right place to get started or learn the basics of OpenStack. For that it's better to check the various OpenStack meetups organized by user groups around the world or attend the other tracks of the OpenStack Summit.
The Design Summit sessions fall into several pre-defined topics, generally one for each OpenStack official program. Visit the summit-specific page (link at the top of this page) for a list of the topics for the next Design Summit.
The scheduled sessions are usually just the start of a longer conversation, where the key stakeholders will continue making the most of the limited face-to-face time we have to make quick progress. To enable continuous collaboration, we have designated space reserved for each program, called program pods. Program pods are the natural meeting point for developers from a given program to meet, hang out, or schedule extra discussions and presentations. Those roundtables should all be equipped with a paperboard that can be used for brainstorming, which defaults as a dynamic schedule.
Before the Design Summit
- Go to http://summit.openstack.org to propose sessions. You'll be authenticated through Launchpad SSO.
- Click on Suggest session on the sessions list screen to submit your own session idea
- See summit-specific page (link at the top of this page) to choose the appropriate topic
- For sessions about features, you should create a Launchpad blueprint to track its design and implementation, and add a link to it on the session proposal (example: nova/better-api to link to the better-api Nova blueprint).
- Your proposal will initially be in Unreviewed status. It can then go to the following statuses:
- Scheduled: Your suggestion was accepted and has been scheduled
- Preapproved: Your suggestion was accepted and should be scheduled (or merged with another session) soon
- Incomplete: Your suggestion needs to be fixed before it can be accepted, please address reviewers comments
- Refused: Your suggestion has been rejected, see reviewers comments for an explanation
At the Design Summit
- The schedule will be available online. Refer to it early, refer to it often
- 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 the available time !
- Collaborative note taking during the session should be done through http://etherpad.openstack.org, please participate and make sure your points are reported there, see the summit-specific link at the top to see where the list of session pads is located
- In brainstorm sessions, 10 minutes before the end of the session, the session lead should start making sure (s)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