Difference between revisions of "Design Summit"
| Line 6: | Line 6: | ||
== 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 | + | 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 track leads. Those sessions can include formal presentations but are usually an 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. |
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. | ||
| Line 15: | Line 15: | ||
The sessions come in three different flavors: | The sessions come in three different flavors: | ||
| − | * '''Brainstorm''' sessions are | + | * '''Brainstorm''' sessions are used to discuss and come up with a solution for complex issues |
| − | * ''' | + | * '''Presentation''' sessions are formal talks (with slides) presenting a given plan |
| − | * ''' | + | * '''Workshop''' sessions are hands-on workshops or tutorials around a given task or part of code |
| − | + | Those sessions can last 25min, 55min or 85min. | |
| − | |||
| − | + | == Tracks == | |
| − | + | The summit sessions fall into the following pre-defined tracks (and track leads): | |
| − | + | * '''Common development''': Development processes and tools, release schedule, openstack-common (ttx) | |
| + | * '''Swift''': OpenStack Object Storage (notmyname) | ||
| + | * '''Nova core''': OpenStack Compute core features, APIs, message queue... (vishy) | ||
| + | * '''Nova hypervisors''': Compute API, supported hypervisors and feature parity (soren) | ||
| + | * '''Nova scaling''': Scaling OpenStack Compute: cells, datastore, threading... (comstud) | ||
| + | * '''Nova volumes''': Future improvements in OpenStack Compute volumes (john-griffith) | ||
| + | * '''Nova networking''': Networking in OpenStack Compute and transition to Quantum (tr3buchet) | ||
| + | * '''Nova other''': Other Nova stuff that doesn't fit in the previous categories (vishy) | ||
| + | * '''Keystone''': OpenStack Identity (heckj) | ||
| + | * '''Glance''': OpenStack Image service (bcwaldon) | ||
| + | * '''Horizon''': OpenStack Dashboard (devcamcar) | ||
| + | * '''Quantum''': Quantum project, including the potential Melange merge (danwent) | ||
| + | * '''Documentation''': Future efforts on documentation (annegentle) | ||
| + | * '''QA''': Quality assurance, unit tests, integration tests, Tempest... (jaypipes) | ||
| + | * '''Deployment/Ops''': Packaging, integration issues, operational needs, tooling... (anotherjesse) | ||
| + | * '''Ecosystem''': Non-core projects around [[OpenStack]] (lloydde) | ||
| + | |||
| + | The ''Ecosystem'' track doubles as an '''unconference''', with a schedule that is completely open and decided at the event itself (first come first serve). | ||
| + | |||
| + | Finally we also propose a set of 5min-long '''Lightning talks''' every day after lunch (first come first serve). | ||
== Before the summit == | == Before the summit == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Propose sessions === | === Propose sessions === | ||
* Details being worked on | * Details being worked on | ||
Revision as of 18:48, 13 March 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 track leads. Those sessions can include formal presentations but are usually an 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.
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 used to discuss and come up with a solution for complex issues
- Presentation sessions are formal talks (with slides) presenting a given plan
- Workshop sessions are hands-on workshops or tutorials around a given task or part of code
Those sessions can last 25min, 55min or 85min.
Tracks
The summit sessions fall into the following pre-defined tracks (and track leads):
- Common development: Development processes and tools, release schedule, openstack-common (ttx)
- Swift: OpenStack Object Storage (notmyname)
- Nova core: OpenStack Compute core features, APIs, message queue... (vishy)
- Nova hypervisors: Compute API, supported hypervisors and feature parity (soren)
- Nova scaling: Scaling OpenStack Compute: cells, datastore, threading... (comstud)
- Nova volumes: Future improvements in OpenStack Compute volumes (john-griffith)
- Nova networking: Networking in OpenStack Compute and transition to Quantum (tr3buchet)
- Nova other: Other Nova stuff that doesn't fit in the previous categories (vishy)
- Keystone: OpenStack Identity (heckj)
- Glance: OpenStack Image service (bcwaldon)
- Horizon: OpenStack Dashboard (devcamcar)
- Quantum: Quantum project, including the potential Melange merge (danwent)
- Documentation: Future efforts on documentation (annegentle)
- QA: Quality assurance, unit tests, integration tests, Tempest... (jaypipes)
- Deployment/Ops: Packaging, integration issues, operational needs, tooling... (anotherjesse)
- Ecosystem: Non-core projects around OpenStack (lloydde)
The Ecosystem track doubles as an unconference, with a schedule that is completely open and decided at the event itself (first come first serve).
Finally we also propose a set of 5min-long Lightning talks every day after lunch (first come first serve).
Before the summit
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
