Jump to: navigation, search

Difference between revisions of "Forum"

(Session types)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
At the Forum the entire community gathers
+
At the Forum the entire OpenStack community (users and developers in equal parts) gathers to to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The OpenStack Foundation offers a [[Travel_Support_Program|Travel Support Program]] to help cover travel expenses.
 
 
<!-- 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 Forum ==
 
== Next Forum ==
Line 11: Line 7:
  
 
== How does the Forum work? ==
 
== How does the Forum work? ==
The Forum is a part of the OpenStack Summit. It is '''not''' a classic conference track with speakers and presentations.  
+
The Forum is a part of the OpenStack Summit. It is '''not''' a classic conference track with speakers and presentations.
 +
Development teams, working groups and interested individuals brainstorm the topics they want to cover and get alignment on.
  
 
<!--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). -->
 
<!--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). -->
Line 40: Line 37:
  
 
== At the Forum ==
 
== At the Forum ==
* The schedule will be available online about a month before the Design Summit starts. Refer to it early, refer to it often
+
* The schedule will be available online about a month before the Summit starts. 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

Revision as of 00:01, 8 December 2016

At the Forum the entire OpenStack community (users and developers in equal parts) gathers to to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The OpenStack Foundation offers a Travel Support Program to help cover travel expenses.

Next Forum

  • OpenStack Summit, May 8-11, 2017 in Boston, USA.
    • Gather feedback on Ocata, start drawing Queen's requirements, venue for Pike midcycles

How does the Forum work?

The Forum is a part of the OpenStack Summit. It is not a classic conference track with speakers and presentations. Development teams, working groups and interested individuals brainstorm the topics they want to cover and get alignment on.


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 Forum 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

Sessions generally happen in rooms organized in fishbowl style (concentric rings of chairs). People wanting to participate to the discussion should move to the inner rings. There are three main types of sessions at the Forum:

Project-specific sessions

Where developers can ask users specific questions about their experience, users can provide feedback from the last release and cross-community collaboration on the priorities and 'blue sky' ideas for the next release can occur.

Strategic, whole-of-community discussions

To think about the big picture, including beyond just one release cycle and new technologies

Cross-project sessions

In a similar vein to what has happened at past design summits, but with increased emphasis on issues that are of relevant to all areas of the community

Before the Forum: propose sessions

At the Forum

  • The schedule will be available online about a month before the 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
  • End on time, to give participants the time to switch rooms to the next session if needed

After the Forum: 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

Forum tips

  • We organize a special "Forum 101" session to serve as an introduction to how things work.
  • Experienced OpenStack contributors share their tips on how to moderate a successful session on this video.