Difference between revisions of "Open/es"
(Created page with "Estamos comprometidos a crear código abierto real que sea usable y escalable. Código abierto real no es una caracteristica o representación limitada y no esta deteriorada....") |
(Created page with "Usamos la Licencia Apache, 2.0. * [http://www.opensource.org/licenses/alphabetical OSI] aprobada, * [http://www.gnu.org/licenses/license-list.html#apache2 GPLv3] compatib...") |
||
| Line 9: | Line 9: | ||
Estamos comprometidos a crear código abierto real que sea usable y escalable. Código abierto real no es una caracteristica o representación limitada y no esta deteriorada. No habrá una "Edición Empresarial". | Estamos comprometidos a crear código abierto real que sea usable y escalable. Código abierto real no es una caracteristica o representación limitada y no esta deteriorada. No habrá una "Edición Empresarial". | ||
| − | + | Usamos la Licencia Apache, 2.0. | |
| − | * [http://www.opensource.org/licenses/alphabetical OSI] | + | * [http://www.opensource.org/licenses/alphabetical OSI] aprobada, |
* [http://www.gnu.org/licenses/license-list.html#apache2 GPLv3] compatible | * [http://www.gnu.org/licenses/license-list.html#apache2 GPLv3] compatible | ||
* [http://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines DFSG] compatible | * [http://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines DFSG] compatible | ||
Revision as of 01:15, 11 November 2015
Contents
¿Qué significa ser abierto?
Código Libre
no producimos software "base libre".
Estamos comprometidos a crear código abierto real que sea usable y escalable. Código abierto real no es una caracteristica o representación limitada y no esta deteriorada. No habrá una "Edición Empresarial".
Usamos la Licencia Apache, 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.
