| 3 | | This page lists the OSGeo graduation checklist status for rasdaman, comments and discussion are welcome on the rasdaman-users mailing list (rasdaman-users _@ googlegroups.com). |
| 4 | | |
| 5 | | = Principles of OSGeo Projects (The OSGeo Way) = |
| 6 | | * Projects should manage themselves, striving for consensus and encouraging participation from all contributors - from beginning users to advanced developers. |
| 7 | | * Contributors are the scarce resource and successful projects court and encourage them. |
| 8 | | * Projects are encouraged to adopt open standards and collaborate with other OSGeo projects. |
| 9 | | * Projects are responsible for reviewing and controlling their code bases to insure the integrity of the open source baselines. |
| 10 | | |
| 11 | | = Operating Principles = |
| 12 | | * Projects should document how they manage themselves. |
| 13 | | * Projects should maintain developer and user documentation. |
| 14 | | * Projects should maintain a source code management system. |
| 15 | | * Projects should maintain an issue tracking system. |
| 16 | | * Projects should maintain project mailing lists. |
| 17 | | * Projects should actively promote their participation in OSGeo. |
| 18 | | * Projects are encouraged to adopt OSGeo look and feel, branding, logos on their project sites. |
| 19 | | * Projects are encouraged to participate in OSGeo standardization efforts to present a common interface for OSGeo visitors and members. |
| 20 | | * Projects should have automated build and smoke test systems. |
| | 3 | This page lists the OSGeo graduation checklist status for rasdaman as per [http://www.osgeo.org/incubator/process/project_graduation_checklist.html OSGeo graduation checklist]; comments and discussion are welcome on the rasdaman-users mailing list (rasdaman-users _@ googlegroups.com). |
