Difference between revisions of "General Principles of Incubation"
Jump to navigation
Jump to search
| 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: | ||
| − | * <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. Ref: [[Project_Graduation_Checklist#open.2]] |
| − | * <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. Ref: [[Project_Graduation_Checklist#Copyright_and_License]] |
| − | * <span id="3">3</span>. adopt the OSGeo principles and operating principles. | + | * <span id="3">3</span>. adopt the OSGeo principles and operating principles. Ref: [[#Operating_Principles]] |
* <span id="4">4</span>. are mentored through the incubation process. | * <span id="4">4</span>. are mentored through the incubation process. | ||
== Principles of OSGeo Projects (The OSGeo Way) == | == Principles of OSGeo Projects (The OSGeo Way) == | ||
| − | * <span id="5">5</span>. Projects should manage themselves, striving for consensus and encouraging participation from all contributors - from beginning users to advanced developers. | + | * <span id="5">5</span>. Projects should manage themselves, striving for consensus and encouraging participation from all contributors - from beginning users to advanced developers. Ref: [[Project_Graduation_Checklist#open.2]] |
| − | * <span id="6">6</span>. Contributors are the scarce resource and successful projects court and encourage them. | + | * <span id="6">6</span>. Contributors are the scarce resource and successful projects court and encourage them. Ref: [[Project_Graduation_Checklist#open.2]] |
| − | * <span id="7">7</span>. Projects are encouraged to adopt open standards and collaborate with other OSGeo projects. | + | * <span id="7">7</span>. Projects are encouraged to adopt open standards and collaborate with other OSGeo projects. Ref: [[Project_Graduation_Checklist#Projects]] . '''TBD: Missing link to Open Standards in Project Graduation Checklist.''' |
| − | * <span id="8">8</span>. Projects are responsible for reviewing and controlling their code bases to insure the integrity of the open source baselines. | + | * <span id="8">8</span>. Projects are responsible for reviewing and controlling their code bases to insure the integrity of the open source baselines. Ref: [[Project_Graduation_Checklist#Copyright_and_License]] |
== Operating Principles == | == Operating Principles == | ||
| − | * <span id="9">9</span>. Projects should document how they manage themselves. | + | * <span id="9">9</span>. Projects should document how they manage themselves. Ref: [[Project_Graduation_Checklist#processes.3]] |
| − | * <span id="10">10</span>. Projects should maintain developer and user documentation. | + | * <span id="10">10</span>. Projects should maintain developer and user documentation. Ref: [[Project_Graduation_Checklist#Documentation]] |
| − | * <span id="11">11</span>. Projects should maintain a source code management system. | + | * <span id="11">11</span>. Projects should maintain a source code management system. Ref: [[Project_Graduation_Checklist#processes.1]] |
| − | * <span id="12">12</span>. Projects should maintain a discrepancy tracking system. | + | * <span id="12">12</span>. Projects should maintain a discrepancy tracking system. Ref: [[Project_Graduation_Checklist#processes.2]] |
| − | * <span id="13">13</span>. Projects should maintain project mailing lists. | + | * <span id="13">13</span>. Projects should maintain project mailing lists. Ref: [[Project_Graduation_Checklist#processes.2b]] |
| − | * <span id="14">14</span>. Projects should actively promote their participation in OSGeo. | + | * <span id="14">14</span>. Projects should actively promote their participation in OSGeo. Ref: [[Project_Graduation_Checklist#Marketing]] |
| − | * <span id="15">15</span>. Projects are encouraged to adopt OSGeo look and feel, branding, [[Logos | logos]] on their project sites. | + | * <span id="15">15</span>. Projects are encouraged to adopt OSGeo look and feel, branding, [[Logos | logos]] on their project sites. Ref: [[Project_Graduation_Checklist#Marketing]] |
| − | * <span id="16">16</span>. Projects are encouraged to participate in OSGeo standardization efforts to present a common interface for OSGeo visitors and members. | + | * <span id="16">16</span>. Projects are encouraged to participate in OSGeo standardization efforts to present a common interface for OSGeo visitors and members. '''TBD: Missing from Project Graduation Checklist.''' |
| − | * <span id="17">17</span>. Projects should have automated build and smoke test systems. | + | * <span id="17">17</span>. Projects should have automated build and smoke test systems. Ref: [[Project_Graduation_Checklist#release.2]] |
[[Category:Incubation]] | [[Category:Incubation]] | ||
Revision as of 05:38, 29 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. Ref: Project_Graduation_Checklist#open.2
- 2. have clear IP oversight of the code base of the project. Ref: Project_Graduation_Checklist#Copyright_and_License
- 3. adopt the OSGeo principles and operating principles. Ref: #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. Ref: Project_Graduation_Checklist#open.2
- 6. Contributors are the scarce resource and successful projects court and encourage them. Ref: Project_Graduation_Checklist#open.2
- 7. Projects are encouraged to adopt open standards and collaborate with other OSGeo projects. Ref: Project_Graduation_Checklist#Projects . TBD: Missing link to Open Standards in Project Graduation Checklist.
- 8. Projects are responsible for reviewing and controlling their code bases to insure the integrity of the open source baselines. Ref: Project_Graduation_Checklist#Copyright_and_License
Operating Principles
- 9. Projects should document how they manage themselves. Ref: Project_Graduation_Checklist#processes.3
- 10. Projects should maintain developer and user documentation. Ref: Project_Graduation_Checklist#Documentation
- 11. Projects should maintain a source code management system. Ref: Project_Graduation_Checklist#processes.1
- 12. Projects should maintain a discrepancy tracking system. Ref: Project_Graduation_Checklist#processes.2
- 13. Projects should maintain project mailing lists. Ref: Project_Graduation_Checklist#processes.2b
- 14. Projects should actively promote their participation in OSGeo. Ref: Project_Graduation_Checklist#Marketing
- 15. Projects are encouraged to adopt OSGeo look and feel, branding, logos on their project sites. Ref: Project_Graduation_Checklist#Marketing
- 16. Projects are encouraged to participate in OSGeo standardization efforts to present a common interface for OSGeo visitors and members. TBD: Missing from Project Graduation Checklist.
- 17. Projects should have automated build and smoke test systems. Ref: Project_Graduation_Checklist#release.2