Difference between revisions of "General Principles of Incubation"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* <span id="1">1</span>. have a successfully operating open and collaborative development community | * <span id="1">1</span>. have a successfully operating open and collaborative development community | ||
* <span id="2">2</span>. have clear IP oversight of the code base of the project | * <span id="2">2</span>. have clear IP oversight of the code base of the project | ||
| − | * <span id="3">3</span>adopt the OSGeo principles and operating principles | + | * <span id="3">3</span>. adopt the OSGeo principles and operating principles |
* <span id="4">4</span>. are mentored through the incubation process | * <span id="4">4</span>. are mentored through the incubation process | ||
Revision as of 16:37, 28 November 2014
Purpose of Incubation
The purpose of the OSGeo incubation process is to ensure that projects that are officially part of OSGeo:
- 1. have a successfully operating open and collaborative development community
- 2. have clear IP oversight of the code base of the project
- 3. adopt the OSGeo principles and operating principles
- 4. are mentored through the incubation process
Principles of OSGeo Projects (The OSGeo Way)
- 5. Projects should manage themselves, striving for consensus and encouraging participation from all contributors - from beginning users to advanced developers.
- 6. Contributors are the scarce resource and successful projects court and encourage them.
- 7. Projects are encouraged to adopt open standards and collaborate with other OSGeo projects.
- 8. Projects are responsible for reviewing and controlling their code bases to insure the integrity of the open source baselines.
Operating Principles
- 9. Projects should document how they manage themselves.
- 10. Projects should maintain developer and user documentation.
- 11. Projects should maintain a source code management system.
- 12. Projects should maintain a discrepancy tracking system.
- 13. Projects should maintain project mailing lists.
- 14. Projects should actively promote their participation in OSGeo.
- 15. Projects are encouraged to adopt OSGeo look and feel, branding, logos on their project sites.
- 16. Projects are encouraged to participate in OSGeo standardization efforts to present a common interface for OSGeo visitors and members.
- 17. Projects should have automated build and smoke test systems.