Difference between revisions of "Open"
(Grammar and a few clarifications) |
m |
||
| (8 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <!-- #acl [[AdminGroup]]:read,write,revert All:read --> | |
| − | + | <languages /> | |
| + | <translate> | ||
| − | == | + | = What Does Openness Mean? = <!--T:1--> |
| − | |||
| − | We | + | == Open Source == <!--T:2--> |
| + | We do '''not''' produce "open core" software. | ||
| + | <!--T:3--> | ||
| + | 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". | ||
| + | |||
| + | <!--T:4--> | ||
We use the Apache License, 2.0. | We use the Apache License, 2.0. | ||
* [http://www.opensource.org/licenses/alphabetical OSI] approved, | * [http://www.opensource.org/licenses/alphabetical OSI] approved, | ||
| Line 12: | Line 17: | ||
* [http://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines DFSG] compatible | * [http://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines DFSG] compatible | ||
| − | == Open Design == | + | == Open Design == <!--T:5--> |
| − | '''We are committed to an open design process.''' Every six months the development community | + | '''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 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. |
| + | |||
| + | == Open Development == <!--T:6--> | ||
| + | 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 == <!--T:7--> | ||
| + | One of our core goals is to maintain a healthy, vibrant developer and user community. Most decisions are made using a [http://www.apache.org/foundation/glossary.html#LazyConsensus lazy consensus] model. All processes are documented, open and transparent. | ||
| − | + | <!--T:8--> | |
| − | We | + | We follow those principles: |
| + | * '''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.''' | ||
| − | == | + | == Are we doing it wrong? == <!--T:9--> |
| − | |||
| − | + | <!--T:10--> | |
| − | + | We're trying our very best to do things the right way, be properly open, free, etc. If you see anything that suggests otherwise, '''please''' don't hesitate to [[Contact|tell us]] or [http://twitter.com call us out on it]. There's a good chance we simply haven't thought about whatever it is that you've identified. | |
| − | + | </translate> | |
| − | + | [[Category:OpenStackFoundation]] | |
| − | |||
Latest revision as of 16:20, 20 October 2014
Contents
What Does Openness Mean?
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.
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 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.
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 model. All processes are documented, open and transparent.
We follow those principles:
- 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.
Are we doing it wrong?
We're trying our very best to do things the right way, be properly open, free, etc. If you see anything that suggests otherwise, please don't hesitate to tell us or call us out on it. There's a good chance we simply haven't thought about whatever it is that you've identified.
