Difference between revisions of "Design Summit"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | At OpenStack Design Summits the developers community gathers to discuss the requirements for the next release, learn more about OpenStack, and connect with community members. | + | At OpenStack Design Summits the developers community gathers to discuss the requirements for the next release, learn more about OpenStack, and connect with community members. |
== Next Summit == | == Next Summit == | ||
| − | |||
Folsom Design Summit, Apr 16-18 in San Francisco: see details at [[Summit/Folsom]] | Folsom Design Summit, Apr 16-18 in San Francisco: see details at [[Summit/Folsom]] | ||
== How does the summit work ? == | == How does the summit work ? == | ||
| − | |||
The design summit is not a classic conference with speakers and presentations. Developers submit session ideas to discuss upcoming features for the next release cycle, which get reviewed and scheduled by the summit drivers. 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. | The design summit is not a classic conference with speakers and presentations. Developers submit session ideas to discuss upcoming features for the next release cycle, which get reviewed and scheduled by the summit drivers. 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. | ||
Each session is moderated by a ''session lead'', usually the person that proposed the session in the first place. | Each session is moderated by a ''session lead'', usually the person that proposed the session in the first place. | ||
| + | |||
| + | The [[OpenStack]] 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 [[OpenStackUsersGroup|user groups]] around the world or one of the [[OpenStack]] conferences. | ||
== Session types == | == Session types == | ||
| − | |||
The sessions come in three different flavors: | The sessions come in three different flavors: | ||
| Line 21: | Line 20: | ||
== Unconference == | == Unconference == | ||
| − | |||
The summit also features an unconference, with a schedule that is completely open and decided at the event itself, which allow projects more loosely-related to [[OpenStack]] to get their time of fame: | The summit also features an unconference, with a schedule that is completely open and decided at the event itself, which allow projects more loosely-related to [[OpenStack]] to get their time of fame: | ||
| Line 30: | Line 28: | ||
== Before the summit == | == Before the summit == | ||
| − | |||
=== Registration === | === Registration === | ||
| + | * Details being worked on | ||
| − | |||
<!-- ## * Attendance is free, but seats are limited. We give priority to known [[OpenStack]] contributors. --> | <!-- ## * Attendance is free, but seats are limited. We give priority to known [[OpenStack]] contributors. --> | ||
<!-- ## * Go to http://summit.openstack.org and log in using your Launchpad ID. --> | <!-- ## * Go to http://summit.openstack.org and log in using your Launchpad ID. --> | ||
<!-- ## * Provide the requested information --> | <!-- ## * Provide the requested information --> | ||
| − | |||
=== Propose sessions === | === Propose sessions === | ||
| − | |||
* Details being worked on | * Details being worked on | ||
| Line 54: | Line 49: | ||
<!-- ## * '''NeedsFixing''': Your proposal needs to be fixed before it can be accepted, please address reviewers comments --> | <!-- ## * '''NeedsFixing''': Your proposal needs to be fixed before it can be accepted, please address reviewers comments --> | ||
<!-- ## * '''Refused''': Your proposal has been rejected, see reviewers comments for an explanation --> | <!-- ## * '''Refused''': Your proposal has been rejected, see reviewers comments for an explanation --> | ||
| − | |||
== At the summit == | == At the summit == | ||
| − | |||
* The schedule will be available online. Refer to it early, refer to it often | * 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 should start on time, be there or be square | ||
Revision as of 19:07, 23 February 2012
At OpenStack Design Summits the developers community gathers to discuss the requirements for the next release, learn more about OpenStack, and connect with community members.
Next Summit
Folsom Design Summit, Apr 16-18 in San Francisco: see details at Summit/Folsom
How does the summit work ?
The design summit is not a classic conference with speakers and presentations. Developers submit session ideas to discuss upcoming features for the next release cycle, which get reviewed and scheduled by the summit drivers. 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.
Each session is moderated by a session lead, usually the person that proposed the session in the first place.
The OpenStack 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 one of the OpenStack conferences.
Session types
The sessions come in three different flavors:
- Brainstorm sessions are 55 min. sessions used to discuss and come up with a solution for complex issues
- Rubberstamp sessions are 25 min. sessions used to present and review an already-designed plan
- Discovery sessions are 25 min. sessions where experts go into deep detail into a section of code or feature
Unconference
The summit also features an unconference, with a schedule that is completely open and decided at the event itself, which allow projects more loosely-related to OpenStack to get their time of fame:
- Unconference presentations (55 min.) during the whole summit
- Lightning talks (5 min.) every day after lunch
Both will be scheduled on a first come, first serve basis on big whiteboards at the summit itself.
Before the summit
Registration
- Details being worked on
Propose sessions
- Details being worked on
At the 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
- In discussion sessions, 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
