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