[upstream] Update of Events Module

With the recent updates to OpenStack events(i.e. the advent of the PTG),
this module needed to be reworked. There are OpenStackDays events now
as well that weren't previously mentioned. This patch adds this
new information to this module. It also renames the module to 'OpenStack
Events' because there are many more events than just the Design Summit that
students should be aware of.

Change-Id: I0ecbde9828e09e0781cbdaf23101da03f785d4e6
This commit is contained in:
Kendall Nelson 2016-10-07 11:36:24 -05:00 committed by KATO Tomoyuki
parent b94105668d
commit 7726c2cd86
5 changed files with 131 additions and 99 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 93 KiB

View File

@ -1,97 +0,0 @@
=======================
OpenStack Design Summit
=======================
.. image:: ./_assets/os_background.png
:class: fill
:width: 100%
OpenStack Design Summit
=======================
Where developers meet face to face to finalize planning for the next release
cycle.
.. image:: ./_assets/05-01-design-summit.png
How does it work?
=================
- Not a classic conference with presenter and audience
- more like a collaborative brainstorming session
- Discuss upcoming features for the next release cycle
- Not suitable to start learning about a topic
.. image:: ./_assets/05-02-design-summit.png
:width: 90%
Etherpads
=========
.. image:: ./_assets/05-03-etherpads.png
Proposing a session
===================
Sessions are proposed on an open document (generally an Etherpad) and
discussed at team meetings.
- https://wiki.openstack.org/wiki/Summit/Liberty
- https://wiki.openstack.org/wiki/Design_Summit/Planning
Types of sessions
=================
- Fishbowl sessions
* Open discussions, chairs organized in concentric rings
* People sitting in the inner circle lead the discussion
* No mics.
- Work sessions
* Like sprints, small groups of people work on specific themes
- Contributor meetups
* Reserved for ad-hoc meetings of project teams
* No predefined agenda.
- Project pods
* Tables informally available for new/small teams
List of sessions
================
- Newton
* https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-29
- Mitaka
* https://mitakadesignsummit.sched.org/#2015-10-30
- Liberty
* https://libertydesignsummit.sched.org/overview/type/design+summit
Selection of sessions
=====================
- TC votes for sessions in cross-project and other-projects tracks
- PTLs vote for sessions in project tracks
At the Design Summit
====================
- Start on time
- Mind the noise
- Clear introductions
- Keep the discussion lively and on-topic
- End on time
Exercise
========
- Add a session proposal regarding your contribution in an etherpad

View File

@ -0,0 +1,128 @@
================
OpenStack Events
================
.. image:: ./_assets/os_background.png
:class: fill
:width: 100%
Regional Events
===============
- OpenStack Days
- OpenStack Birthday Celebration
- User Group Meetups
OpenStack Days
==============
- Regional 'Mini-Summit'
- Hosted annually by local OpenStack User Groups and companies
- Endorsed by the foundation
- Growing in number (26 in 2016)
Exercise 1
==========
- Look up an OpenStack Days event close to where you live that you would be
interested in attending
OpenStack Birthday Celebration
==============================
- Held by local groups to celebrate another year of OpenStack
- 2016 was 6th birthday of OpenStack
User Group Meetups
==================
- Smaller scale than OpenStack Days Events
- Some are more development focused while others are more user and
ops focused
- https://groups.openstack.org/
Global Events and Releases
==========================
.. image:: ./_assets/revised_timeline.png
:class: fill
:width: 100%
Project Team Gathering (PTG)
============================
- A gathering of projects teams and contributors
- Dedicated and detailed technical discussions
- Useful for participants if they are already working with a
project team
- Not good as an entry point
.. note
http://www.openstack.org/ptg
http://www.openstack.org/ptg/ptgfaq/
Exercise 2
==========
- Look up the location and dates of the first PTG
OpenStack Design Summit
=======================
Where developers meet face to face to finalize planning for the next release
cycle.
.. image:: ./_assets/05-01-design-summit.png
.. note
This format is being deprecated and this Summit is the last where this will
be the format.
How does it work?
=================
- Not a classic conference with presenter and audience
- more like a collaborative brainstorming session
- Discuss upcoming features for the next release cycle
- Not suitable to start learning about a topic
.. image:: ./_assets/05-02-design-summit.png
:width: 90%
Etherpads
=========
.. image:: ./_assets/05-03-etherpads.png
Types of sessions
=================
- Fishbowl sessions
* Open discussions, chairs organized in concentric rings
* People sitting in the inner circle lead the discussion
* No mics.
- Work sessions
* Like sprints, small groups of people work on specific themes
- Contributor meetups
* Reserved for ad-hoc meetings of project teams
* No predefined agenda.
List of sessions
================
- Ocata
* https://www.openstack.org/summit/barcelona-2016/summit-schedule/
Forum
=====
- Replacement for Design Summit at future Summits
- More user focused discussion to collect feedback for developers
- Better entry point for new contributors finding their place in the
community

View File

@ -23,8 +23,9 @@ How OpenStack is Made
:maxdepth: 1
howitsmade-official-projects.rst
howitsmade-design-summit.rst
howitsmade-events.rst
howitsmade-metrics.rst
howitsmade-events.rst
howitsmade-release-cycle.rst
howitsmade-technical-committee.rst
howitsmade-communication.rst

View File

@ -106,7 +106,7 @@ How OpenStack is Made
---------------------
* `Official OpenStack projects <howitsmade-official-projects.html>`_
* `OpenStack Design Summit <howitsmade-design-summit.html>`_
* `OpenStack Events <howitsmade-events.html>`_
* `Metrics <howitsmade-metrics.html>`_
* `Release cycle <howitsmade-release-cycle.html>`_
* `OpenStack Governance <howitsmade-technical-committee.html>`_