Difference between revisions of "Open"
(Grammar and a few clarifications) |
|||
| Line 5: | Line 5: | ||
We will '''not''' produce "open core" software. | We will '''not''' produce "open core" software. | ||
| − | We are committed to creating truly open source 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. This will be no "Enterprise Edition".tg |
We use the Apache License, 2.0. | We use the Apache License, 2.0. | ||
| Line 23: | Line 23: | ||
We make the following promises: | We make the following promises: | ||
* '''The community will be involved in the design process.''' You can help make this software meet your needs. | * '''The community will be involved in the design process.''' You can help make this software meet your needs. | ||
| − | * '''The community will have representation''' on the technical board, which has the ability to override decisions by the project lead | + | * '''The community will have representation''' on the technical board, which has the ability to override decisions by the project lead. |
| − | * '''This will always be truly free software.'' We will never purposefully limit the functionality or scalability | + | * '''This will always be truly free software.''' We will never purposefully limit the functionality or scalability or the software to try and sell you an "enterprise" version |
| − | * '''All project meetings will be held | + | * '''All project meetings will be held in public IRC channels and recorded.''' |
Revision as of 20:35, 28 June 2010
What Does Openness Mean?
Open Source
We will 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. This will be no "Enterprise Edition".tg
We use the Apache License, 2.0.
Open Design
We are committed to an open design process. Every six months the development community will hold a design summit to gather requirements and write specifications for upcoming release. The summits, which are open to the public, will include users, developers, and upstream projects. We will gather requirements and produce an approved roadmap used to guide development for the next six months.
Open Development
We will maintain a publicly available source code repository through the entire development process. This will make participation simpler and will allow users to follow the development process, and participate in QA at an early stage.
Open Community
One of our core goals is to produce a healthy, vibrant developer and user community. Most decisions will be made using a lazy consensus model. All processes will be documented, open and transparent.
We make the following promises:
- The community will be involved in the design process. You can help make this software meet your needs.
- The community will have representation on the technical board, which has the ability to override decisions by the project lead.
- This will always be truly free software. We will never purposefully limit the functionality or scalability or the software to try and sell you an "enterprise" version
- All project meetings will be held in public IRC channels and recorded.
