openstack/training-guides
Code Issues Proposed changes
training-guides/doc/upstream-training/source/slides/howitsmade-design-summit.rst
Akihiro Motoki 383a5bec4b Reorganize directory structure 
Currently for both upstream-training and training-guide directory
slides are stored in the subdirectories of landing web pages.
It is not easy to capture the directory structure and this requires
Sphinx conf file to have unnecessary excluded entries.

This commits reorganizes each directory to the following structure.
It follows the convention in the documentation project.

doc/upstream-training:

(previous)
  +-- README.rst
  +-- website RST files
  +-- conf.py (for website)
  +-- build/
  +-- source/
       +-- slide RST files
       +-- conf.py (for slides)
       +-- _assets/
       +-- _static/
       +-- locale/

(new)
  +-- README.rst
  +-- build/
  +-- source/
       +-- website/
       |    +-- website RST files
       |    +-- conf.py (for website)
       |    +-- _assets/
       +-- slides/
       |    +-- slide RST files
       |    +-- conf.py (for slides)
       |    +-- _assets/
       |    +-- _static/
       +-- locales/

training-guide directory is reorganized similarly.
training-guide _assets/README has been removed as it is used.

Also updates tox.ini to share target command definitions.
We do not need to have same things in many places.

Note that this commit does not change the build document paths.

Change-Id: I5a21f170c06d8f71f1f2d0df354e6d6280cb29d0
2016-10-09 03:35:30 +00:00

2.0 KiB
Raw Blame History

OpenStack Design Summit

image

OpenStack Design Summit

Where developers meet face to face to finalize planning for the next release cycle.

image

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

Etherpads

image

Proposing a session

Sessions are proposed on an open document (generally an Etherpad) and discussed at team meetings.

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

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