Difference between revisions of "Design Summit"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | At Design Summits the developers community gathers to | + | At Design Summits the developers community gathers to brainstorm the requirements for the next release, discuss the implementation details and connect with other community members. The OpenStack Foundation offers a [[Travel_Support_Program|Travel Support Program]] to help cover travel expenses. |
== Next Design Summit == | == Next Design Summit == | ||
| − | * | + | * Kilo Design Summit, November 4-7, 2014 in Paris, France. See kilo-specific details at [[Summit/Kilo]]. |
| − | |||
| − | |||
| − | |||
== How does the Design Summit work? == | == 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. | + | The Design Summit is a part of the OpenStack Summit. It is '''not''' a classic conference track with speakers and presentations. Developer teams brainstorm the topics they need to cover and get alignment on. The agenda is collaboratively reviewed and then scheduled by the program technical leads (PTLs). Those scheduled 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. | 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. | ||
| Line 17: | Line 14: | ||
== Topics == | == Topics == | ||
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 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. | ||
| + | |||
| + | == Contributors meetups == | ||
| + | On the last day of the summit, developers for a given program will gather for a half-day or a full-day of open discussions without a pre-defined theme. Depending on how the previous days went, the agenda might evolve. | ||
== Program pods == | == Program pods == | ||
| − | + | We also have a number of '''program pods''' available. 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 == | == Before the Design Summit == | ||
=== Propose sessions === | === Propose sessions === | ||
| − | + | Sessions are proposed on an open document (generally an Etherpad) and discussed at team meetings. See [[Summit/Planning]] for a list of such documents. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== At the Design Summit == | == At the Design Summit == | ||
Revision as of 14:17, 17 September 2014
At Design Summits the developers community gathers to brainstorm the requirements for the next release, discuss the implementation details and connect with other community members. The OpenStack Foundation offers a Travel Support Program to help cover travel expenses.
Next Design Summit
- Kilo Design Summit, November 4-7, 2014 in Paris, France. See kilo-specific details at Summit/Kilo.
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. Developer teams brainstorm the topics they need to cover and get alignment on. The agenda is collaboratively reviewed and then scheduled by the program technical leads (PTLs). Those scheduled 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.
Topics
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.
Contributors meetups
On the last day of the summit, developers for a given program will gather for a half-day or a full-day of open discussions without a pre-defined theme. Depending on how the previous days went, the agenda might evolve.
Program pods
We also have a number of program pods available. 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
Propose sessions
Sessions are proposed on an open document (generally an Etherpad) and discussed at team meetings. See Summit/Planning for a list of such documents.
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
