openstack/governance
Code Issues Proposed changes

Refactor 4 opens as in Project team guide

Browse Source 
The version of the "4 opens" that was in the wiki had been
refactored when copied to the Project Team Guide, to get
rid of the "we follow this principles" section which was
partially redundant and not really one of the "opens". Some
bits were moved to the corresponding sections, and redundant
text was removed.

Now that the wiki version has been imported in governance,
re-propose this same refactoring for inclusion in the reference
document.

Change-Id: I4da77173ce64b1e64106d48c7d9e3262dde561f8
This commit is contained in:
Thierry Carrez 2016-01-06 12:01:06 +01:00
parent 8e5fe36561
commit 8d028bbba9
1 changed files with 7 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
reference/opens.rst
View File

@ -27,6 +27,9 @@ to the public**, include users, developers, and upstream projects. We gather
requirements and produce an approved roadmap used to guide development for the
next six months.
The community controls the design process. You can help make this software
meet your needs.
Open Development
----------------
@ -43,15 +46,8 @@ community. Most decisions are made using a `lazy consensus
<http://www.apache.org/foundation/glossary.html#LazyConsensus>`_ model. All
processes are documented, open and transparent.
We follow those principles:
The technical governance of the project is a community meritocracy with
contributors electing technical leads and members of the Technical Committee.
* **The community controls the design process.** You can help make this
software meet your needs.
* **The technical governance of the project is a community meritocracy** with
contributors electing technical leads and members of the Technical Committee.
* **This will always be truly free software.** We will never purposefully
limit the functionality or scalability of the software to try and sell you
an "enterprise" version
* **All project meetings are held in public IRC channels and recorded.**
* **Additional technical communication is through public mailing lists and is
archived.**
All project meetings are held in public IRC channels and recorded. Additional
technical communication is through public mailing lists and is archived.