8d028bbba9
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
54 lines
2.0 KiB
ReStructuredText
54 lines
2.0 KiB
ReStructuredText
==============
|
|
The Four Opens
|
|
==============
|
|
|
|
Open Source
|
|
-----------
|
|
|
|
We do **not** produce "open core" software.
|
|
|
|
We are committed to creating truly open source software that is usable and
|
|
scalable. Truly open source software is not feature or performance limited and
|
|
is not crippled. There will be no "Enterprise Edition".
|
|
|
|
We use the Apache License, 2.0.
|
|
|
|
* `OSI <http://www.opensource.org/licenses/alphabetical>`_ approved
|
|
* `GPLv3 <http://www.gnu.org/licenses/license-list.html#apache2>`_ compatible
|
|
* `DFSG <http://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines>`_ compatible
|
|
|
|
Open Design
|
|
-----------
|
|
|
|
**We are committed to an open design process.** Every six months the
|
|
development community holds a design summit to gather requirements and write
|
|
specifications for the upcoming release. The design summits, which are **open
|
|
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
|
|
----------------
|
|
|
|
We maintain a publicly available source code repository through the entire
|
|
development process. We do public code reviews. We have public roadmaps. This
|
|
makes participation simpler, allows users to follow the development process and
|
|
participate in QA at an early stage.
|
|
|
|
Open Community
|
|
--------------
|
|
|
|
One of our core goals is to maintain a healthy, vibrant developer and user
|
|
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.
|
|
|
|
The technical governance of the project is a community meritocracy with
|
|
contributors electing technical leads and members of the Technical Committee.
|
|
|
|
All project meetings are held in public IRC channels and recorded. Additional
|
|
technical communication is through public mailing lists and is archived.
|