OSGeo Incubation Checklist

This page lists the OSGeo graduation checklist status for rasdaman, based on the ​OSGeo graduation checklist v1.0 which was authoritative when incubation started. Comments and discussion are welcome on the ​rasdaman mailing lists. The project has invested considerable resources into establishing this checklist over various versions provided by OSGeo, as well as clarifications.

Overall process coordination / Project Officer: ​Peter Baumann.

Activities management

Open activities have been listed at the beginning of the checklist sections they belong to. At this stage, no open activities are remaining.

Icon legend and media attribution

• Waiting for verification. From ​http://commons.wikimedia.org/wiki/File:Hourglass.png
• OK. From ​http://commons.wikimedia.org/wiki/File:Icons-mini-icon_accept.gif#file
• Warning Note. From ​http://commons.wikimedia.org/wiki/File:Icons-mini-icon_alert.gif
• Not met, yet. From ​http://commons.wikimedia.org/wiki/File:Icons-mini-action_stop.gif#file
• Assigned and ongoing. From ​http://commons.wikimedia.org/wiki/File:Icons-mini-icon_user.gif#file

INCUBATION CHECKLIST (as per OSGeo v1.0 and 2.0)

Open

The project has demonstrated that it has an open, active and healthy user and developer community:

1. Open: projects are expected to function in an open and public manner and include:
   1. Open source license(s): see License
   2. Open communication channels: see MailingLists
   3. Open decision making process: see Governance
2. Active and healthy community:
   1. The project should have a community of developers and users who actively collaborate and support each other in a healthy way: see contributors in ​http://rasdaman.org/patchmanager; further contributors perform OGC WCS suite conformance testing development against rasdaman as WCS Core Reference Implementation, which yields yet another collaboration; one such contributor is Fuzhou University.
   2. Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations: see contributors in ​http://rasdaman.org/patchmanager and authors of wiki edits.

Copyright and License

Ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:

1. All project source code is available under an Open Source license.
2. Project documentation is available under an open license, as documented here: License
3. The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included. Here is the code Provenance Review: ​http://rasdaman.org/wiki/OSGeoCodeProvenance
4. The project maintains a list of all copyright holders identified in the Provenance Review Document; all contributors are automatically listed here: ​http://www.rasdaman.org/patchmanager/all .
5. All code contributors have agreed to abide by the project's license policy, and this agreement has been ​documented and ​archived

Processes

1. The project has code under configuration management, see the ​rasdaman git repository.
2. The project uses an issue tracker and keeps the status of the issue tracker up to date: ​http://www.rasdaman.org/report
3. The project has documented its management processes: ​http://www.rasdaman.org/wiki/Governance
   1. The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner: ​http://www.rasdaman.org/wiki/Governance; developers are actively solicited to have technical discussion directly through the dev list.
   2. The project uses public communication channels for decision making to maintain transparency: ​http://www.rasdaman.org/wiki/MailingLists, ​http://www.rasdaman.org/report

Documentation

1. The project has user documentation, including sufficient detail to guide a new user through performing the core functionality provided by the application: ​http://www.rasdaman.org/wiki/Documentation, ​http://www.rasdaman.org/browser/manuals_and_examples
2. The project has developer documentation:
   1. Including checkout and build instructions: ​http://www.rasdaman.org/wiki/Documentation, ​http://www.rasdaman.org/wiki/Download
   2. Including commented code, ideally published for developer use: there is ample inline documentation, including javadoc and doxygen instrumentation: ​http://www.rasdaman.org/browser
   3. Providing sufficient detail for an experienced programmer to contribute patches or a new module in accordance with the project's programming conventions: see ​http://www.rasdaman.org/wiki/HowToContribute as an entry point for tons of descriptions, hints, and how-tos.

Release Procedure

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

1. The project follows a defined release process:
   1. Which includes execution of the testing process before releasing a stable release: ​http://212.201.49.21:35000/
   • All patches submitted to the repository undergo review before being applied to the code base: ​http://www.rasdaman.org/patchmanager
   • Milestones and tickets are used to prepare releases: ​http://www.rasdaman.org/report, ​http://www.rasdaman.org/timeline
   • Releases adopt semantic versioning (starting from 8.4.0): ​http://rasdaman.org/wiki/RasdamanReleaseProcess
   • Systemtests are to be run by developers before submitting patches: ​http://www.rasdaman.org/wiki/CodeGuide
   • Formal process under review at ​http://rasdaman.org/wiki/RasdamanReleaseProcess

1. The project follows a documented testing process.
   • Release testing has been automated (platforms continuously getting extended); regression testing is available, since inception of open-source rasdaman, through cd ​http://rasdaman.org/browser/systemtest systemtest && make check.
   • README documents and wiki pages provide test system description and information: ​http://rasdaman.org/search?q=systemtest&noquickjump=1&changeset=on&milestone=on&ticket=on&wiki=on systemtest description listing
2. Release and testing processes provide sufficient detail for an experienced programmer to follow.
   • Release process makes use of the project trac roadmap feature, paired with the ticket manager. The latter has been extended to support "feature" tickets to ease tracking high-level features and assign them to release milestones. Testing system has been documented on wiki: ​http://rasdaman.org/wiki/RasdamanTestSuites

OSGeo Committees and Community

Board

1. A project provide a Project Officer as a contact point: (Note: the OSGeo template states "contract point", we interpreted this as "contact"): listed at top of this page, see also ​http://www.rasdaman.org/wiki/Governance
   1. The Project Officer should be listed at Officers and Board of Directors and Contacts
   2. This person is established when the incubation committee recommends the project for graduation
   3. Your community can change the project officer as needed.

Marketing

1. Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's ​Marketing Artefacts: rasdaman is included in OSGeo-Live
2. Ideally, stable version(s) of executable applications are bundled with appropriate distributions: Available with OSGeo-Live, see also ​http://standards.rasdaman.org .

Projects

Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

Related:

• contact with ​PostgreSQL community established, tickets submitted.

PSC

1. Project Steering Committee: has been stablished, see ​http://www.rasdaman.org/wiki/Governance
   • registration to project trac and mailing lists are open: ​http://www.rasdaman.org/wiki/MailingLists, ​http://www.rasdaman.org/admin
   • PSC and governance is established: ​http://www.rasdaman.org/wiki/Governance

1. Projects are expected to function in an open and public manner and include:
   1. Open source license(s): GPL for server, LGPL for client components: ​http://www.rasdaman.org/wiki/CodeProvenance
   2. Open communication channels:
      1. rasdaman-dev list: ​https://groups.google.com/forum/?fromgroups#!forum/rasdaman-dev
      2. rasdaman-user list: ​https://groups.google.com/forum/?fromgroups#!forum/rasdaman-usersras
      3. issue tracker (trac): ​http://rasdaman.org/report/1
   3. Open decision making process: ​Feature table is maintained on wiki, new features can be openly discussed on the mailing lists
2. Active and healthy community:
   1. The project should have a community of developers and users who actively collaborate and support each other in a healthy way: see ​list archives
      1. Committers listed on governance page: there are too many, and new ones coming in frequently, so we have automated this: ​http://www.rasdaman.org/patchmanager
   2. Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations: ​http://www.rasdaman.org/patchmanager

SAC

1. A ​http://projectname.osgeo.org domain name. Note that this is optional - rasdaman has its infrastructure set since long, so this is not needed.
2. A project may optionally request SAC help to make use of:
   1. OSGeo issue tracker : rasdaman tracker used instead: ​http://www.rasdaman.org/report
   2. OSGeo mailing list : rasdaman lists used instead: ​http://www.rasdaman.org/wiki/MailingLists
   3. OSGeo svn : rasdaman git used instead: ​http://www.rasdaman.org/browser
   4. ​http://downloads.osgeo.org : rasdaman download facilities used instead: ​http://www.rasdaman.org/wiki/Download