OpenStack Developer Mailing List Digest September 10-16

Website Automation

8 years ago

The content below is taken from the original (OpenStack Developer Mailing List Digest September 10-16), to continue reading please visit the site. Remember to respect the Author & Copyright.

Nominations for OpenStack PTLs Are Now Open

Will remain open until September 18 23:45 UTC
Submit a text file to the openstack/election repository [1].
- File name convention: $cycle_name/$project_name/$ircname.txt
In order to be an elgible candidate (and be allowed to vote) you need to have contributed an accepted patch to one of the program projects during the Mitaka-Newton timeframe.
Additional information [2].
Approved candidates [3]
Elections will start at September 19, 2016 00:00 UTC until September 25 23:45 UTC
Full thread

Proposed slot allocation for project teams at the Ocata design summit in Barcelona [4] based on requests current PTLs have made and adjusted for limit space available.
Kendall Nelson and Thierry will start laying out those sessions over the available rooms and time slots.
Communicated constraints (e.g. Manila not wanting to overlap with Cinder) should be communicated to Thierry asap.
If you don’t plan to use all of your slots, let Thierry know so they can be given to a team that needs them.
Start working with your team on content you’d like to cover at the summit and warm up those etherpads!
Full thread

A set of OpenStack principles is proposed [5] to accurately capture existing tribal knowledge as a prerequisite for being able to have an open and productive discussions about changing it.
Last time majority of the Technical Committee were together, it was realized that there were a set of unspoken assumptions carried and used to judge things.
- These are being captured to empower everyone to actually be able challenge and discuss them.
The principles were started by various TC members who have governance history and know these principles. This was in attempt to document this history to commonly asked questions. These are not by any means final, and the community should participate in discussing them.
Full thread

Recently merged guidelines
- URIs [6]
- Links [7]
- Version string being parsable [8]
Guidelines Under review
- Add a warning about JSON expectations. [9]
Full thread