Jump to: navigation, search

Difference between revisions of "Design Summit"

m (make link to Forum internal)
 
(47 intermediate revisions by 17 users not shown)
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.  
+
'''The Design Summit has been split into two separate elements''': the [https://www.openstack.org/ptg Project Teams Gathering] and [[Forum]] within the main summit conference.  Therefore not everything on the rest of this page necessarily still holds, but the page is kept here for historical reference.  For more information on this split, please see [https://www.openstack.org/ptg#tab_faq the PTG FAQ].
  
== Last Summit ==
+
At Design Summits the developer community gathered 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.
  
Essex Design Summit, Oct 3-5 in Boston: see details at [[Summit/Essex]]
+
== Past Design Summits ==
 +
* Ocata Design Summit, Oct 25-28, 2016 in Barcelona, Spain.
 +
* [[Design_Summit/Ocata/Etherpads|List of etherpads]] for the Ocata summit
  
== How does the 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. Developer project 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.
  
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.
+
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.
  
Each session is moderated by a ''session lead'', usually the person that proposed the session in the first place.
+
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 [[OpenStackUsersGroup|user groups]] around the world or attend the other conference tracks of the OpenStack Summit.
  
 
== Session types ==
 
== Session types ==
 +
There are three types of sessions at the Design Summits:
  
The sessions come in three different flavors:
+
==== Fishbowl sessions ====
 +
Those are open sessions to discuss a specific feature or issue we have to solve. They happen in large rooms organized in fishbowl style (concentric rings of chairs). People wanting to participate to the discussion should move to the inner rings.
  
* '''Brainstorm''' sessions are 55 min. sessions used to discuss and come up with a solution for complex issues
+
==== Work sessions ====
* '''Rubberstamp''' sessions are 25 min. sessions used to present and review an already-designed plan
+
Work sessions are smaller gatherings of teams (or subteams) members to get specific work planned and done. They happen in smaller rooms organized in boardroom style.
* '''Discovery''' sessions are 25 min. sessions where experts go into deep detail into a section of code or feature
 
  
== Unconference ==
+
==== Contributors meetups ====
 +
On the last day of the summit, developers on a given team 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.
  
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:
+
== Before the Design Summit: propose sessions ==
  
* '''Unconference''' presentations (55 min.) during the whole summit
+
Each project team comes up with its own way of building a schedule, ultimately arbitrated by the team's PTL. Sessions are generally proposed on an open document (etherpad...) announced on the openstack-dev mailing-list, and then discussed at team meetings.
* '''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.
+
== At the Design Summit ==
 
+
* The schedule will be available online a few weeks before the Design Summit starts. Refer to it early, refer to it often
== Before the summit ==
 
 
 
=== Registration ===
 
 
 
* 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.
 
* Provide the requested information
 
 
 
=== Propose sessions ===
 
 
 
* Any attendee (even on the waiting list) can propose a session
 
* Go to http://summit.openstack.org to propose sessions (click on "Proposed sessions")
 
* Note that the ''Unconference'' will be proposed and scheduled directly on-site on whiteboards, first come, first serve.
 
* Click on '''Proposed sessions''' on the main page to access the list of proposed sessions
 
* Click on '''Propose session''' on the sessions list screen to submit your own session topic
 
** See ''Session types'' above to choose the right session type
 
** 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:
 
** '''Accepted''': Your session was accepted and will be scheduled
 
** '''WaitingList''': Your session is accepted in a secondary list and will be scheduled if room is left in the schedule
 
** '''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
 
 
 
== 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 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
Line 60: Line 38:
 
* Make the best use of the available time !
 
* 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
* 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
+
* In fishbowl sessions, 5 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
 
* End on time, to give participants the time to switch rooms to the next session if needed
 +
 +
== After the Design Summit: document outcomes ==
 +
* Document significant outcomes and post them to the mailing-list, so that the people who could not join the event can still influence the decision
 +
 +
== Design Summit tips ==
 +
* We organize a special "Design Summit 101" session to serve as an introduction to how things work. You can find a write-up of such a session [http://superuser.openstack.org/articles/how-to-get-the-most-from-your-first-design-summit here].
 +
* Experienced OpenStack contributors share their tips on how to moderate a successful session on [https://www.youtube.com/watch?v=M4cDyM2s2bc this video].
 +
 +
 +
[[Category:Connect]]

Latest revision as of 18:28, 8 May 2017

The Design Summit has been split into two separate elements: the Project Teams Gathering and Forum within the main summit conference. Therefore not everything on the rest of this page necessarily still holds, but the page is kept here for historical reference. For more information on this split, please see the PTG FAQ.

At Design Summits the developer community gathered 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.

Past Design Summits

  • Ocata Design Summit, Oct 25-28, 2016 in Barcelona, Spain.
  • List of etherpads for the Ocata summit

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 project 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 conference tracks of the OpenStack Summit.

Session types

There are three types of sessions at the Design Summits:

Fishbowl sessions

Those are open sessions to discuss a specific feature or issue we have to solve. They happen in large rooms organized in fishbowl style (concentric rings of chairs). People wanting to participate to the discussion should move to the inner rings.

Work sessions

Work sessions are smaller gatherings of teams (or subteams) members to get specific work planned and done. They happen in smaller rooms organized in boardroom style.

Contributors meetups

On the last day of the summit, developers on a given team 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.

Before the Design Summit: propose sessions

Each project team comes up with its own way of building a schedule, ultimately arbitrated by the team's PTL. Sessions are generally proposed on an open document (etherpad...) announced on the openstack-dev mailing-list, and then discussed at team meetings.

At the Design Summit

  • The schedule will be available online a few weeks before the Design Summit starts. 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 fishbowl sessions, 5 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

After the Design Summit: document outcomes

  • Document significant outcomes and post them to the mailing-list, so that the people who could not join the event can still influence the decision

Design Summit tips

  • We organize a special "Design Summit 101" session to serve as an introduction to how things work. You can find a write-up of such a session here.
  • Experienced OpenStack contributors share their tips on how to moderate a successful session on this video.