Difference between revisions of "Design Summit"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | At | + | 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 == |
| − | The | + | The next Design Summit will happen April 27th-29th at the [http://santaclara.hyatt.com/hyatt/hotels/index.jsp Hyatt Regency] in Santa Clara, CA, USA ([http://maps.google.fr/maps?f=q&source=s_q&hl=fr&geocode=&q=5101+Great+America+Parkway,+Santa+Clara,+CA+95054&sll=46.75984,1.738281&sspn=12.239987,13.666992&ie=UTF8&hq=&hnear=5101+Great+America+Pkwy,+Santa+Clara,+California+95054,+%C3%89tats-Unis&ll=37.40521,-121.976566&spn=0.110861,0.106773&z=13 5101 Great America Parkway, Santa Clara, CA 95054]) |
| − | == | + | == How does the summit work ? == |
| − | 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 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. |
| − | You can | + | Each session is moderated by a ''session lead''. You can identify him as being the ''Drafter'' of the corresponding Launchpad blueprint. |
| + | |||
| + | == Session types == | ||
| − | + | The sessions come in two different flavors: | |
| − | The | + | * The ''discussion'' sessions are 45-55 min. sessions used to barinstorm and come up with a design for complex issues |
| − | + | * The ''review'' sessions are 15-20 min. sessions used to present and rubberstamp an already-designed plan | |
| − | + | Session leads decide, based on how advanced is their design, to pick one type or the other. | |
== Summit preparation, for session leads == | == Summit preparation, for session leads == | ||
| − | * You should file a Launchpad blueprint for each subject | + | * You should file a Launchpad blueprint for each subject |
| − | ** Click [https://blueprints.launchpad.net/sprints/ods- | + | ** Click [https://blueprints.launchpad.net/sprints/ods-d/+addspec here] to register a new blueprint for the OpenStack Diablo Design Summit |
** Under ''For'', choose the appropriate project ('''nova''', '''swift''', '''glance''', or '''openstack-dev''' for common discussions) | ** Under ''For'', choose the appropriate project ('''nova''', '''swift''', '''glance''', or '''openstack-dev''' for common discussions) | ||
| − | ** Under ''Name'' | + | ** Under ''Name'' and ''Title'', name the feature. The ''Title'' 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 ''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 ''Definition Status'', choose '''Discussion''' for a discussion session, and '''Review''' for a review session. | ||
** Under ''Drafter'', enter the Launchpad ID of the session lead (that should be you) | ** Under ''Drafter'', enter the Launchpad ID of the session lead (that should be you) | ||
| − | + | ** If you registered the spec directly under the project, you'll have a ''Propose for sprint'' drop-down. Select '''Openstack Design Summit - Diablo''' (this step is not necessary if you used the above link). | |
| − | ** If you registered the spec directly under the project, you'll have a ''Propose for sprint'' drop-down. Select | ||
** Click ''Register Blueprint'', and you're done ! | ** Click ''Register Blueprint'', and you're done ! | ||
| − | * The blueprint will be reviewed by the | + | * The blueprint will be reviewed by the summit drivers and accepted or denied for the summit. |
* You should use the ''Whiteboard'' area on the blueprint to outline the agenda of the session. | * You should use the ''Whiteboard'' area on the blueprint to outline the agenda of the session. | ||
| − | == Summit registration | + | == Summit registration == |
| + | |||
| + | You first need to register on the general Openstack Conference and Design Summit registration site (link coming up) | ||
| − | + | Additionally, you should register on Launchpad, by following this link: https://launchpad.net/sprints/ods-d/+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. | 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: | To mark yourself ''essential'' to a discussion: | ||
| − | * Look up the list of [https://blueprints.launchpad.net/sprints/ods- | + | * Look up the list of [https://blueprints.launchpad.net/sprints/ods-d already scheduled blueprints] |
* For the blueprints where your participation to the session is essential, click on the '''Subscribe''' link | * For the blueprints where your participation to the session is essential, click on the '''Subscribe''' link | ||
* Check the '''Participation essential (Required)''' checkbox | * Check the '''Participation essential (Required)''' checkbox | ||
| Line 52: | Line 53: | ||
== At the summit == | == At the summit == | ||
| − | * The schedule | + | * The schedule will be available at: (URL pending) |
* The session should start on time, be there or be square | * 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 | * 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 | * It is the responsibility of the session lead to keep the discussion live and on-topic | ||
| − | * Make the best use of | + | * 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 | * 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 | * 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 | + | * 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 | * End on time, to give participants the time to switch rooms to the next session if needed | ||
| − | |||
== History == | == History == | ||
Revision as of 16:55, 10 March 2011
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
The next Design Summit will happen April 27th-29th at the Hyatt Regency in Santa Clara, CA, USA (5101 Great America Parkway, Santa Clara, CA 95054)
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. You can identify him as being the Drafter of the corresponding Launchpad blueprint.
Session types
The sessions come in two different flavors:
- The discussion sessions are 45-55 min. sessions used to barinstorm and come up with a design for complex issues
- The review sessions are 15-20 min. sessions used to present and rubberstamp an already-designed plan
Session leads decide, based on how advanced is their design, to pick one type or the other.
Summit preparation, for session leads
- You should file a Launchpad blueprint for each subject
- Click here to register a new blueprint for the OpenStack Diablo Design Summit
- Under For, choose the appropriate project (nova, swift, glance, or openstack-dev for common discussions)
- Under Name and Title, name the feature. The Title 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 Definition Status, choose Discussion for a discussion session, and Review for a review session.
- Under Drafter, enter the Launchpad ID of the session lead (that should be you)
- If you registered the spec directly under the project, you'll have a Propose for sprint drop-down. Select Openstack Design Summit - Diablo (this step is not necessary if you used the above link).
- Click Register Blueprint, and you're done !
- The blueprint will be reviewed by the summit drivers 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
You first need to register on the general Openstack Conference and Design Summit registration site (link coming up)
Additionally, you should register on Launchpad, by following this link: https://launchpad.net/sprints/ods-d/+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 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 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
- Add a link to the etherpad doc from the session blueprint whiteboard, for reference
- 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
History
These pages contain information and notes from the Summits so far:
