GeoServer : GeoServer Incubation Checklist
This page last changed on Feb 28, 2013 by jive.
Page to be filled in based on: Project Graduation Checklist.
1. Open: projects are expected to function in an open and public manner and include:
2. Active and healthy community:
1. All project source code is available under an Open Source license.
1. The project has code under configuration management: http://github.com/geoserver
1. The project has user documentation
2. The project has developer documentation: Geoserver Developers Manual
Each release Stable has API Documentation download, and Source Code download archives.
Developers Manual includes Policies and Procedures covers the nuts and bolts of committing, submitting patches, code reviews. Community process including formal GSIP change control and the functioning of the steering committee.
There is a relaxed community module sandbox to foster new developers.
1. The project follows a defined release process:
We have long maintained a Release Guide, recently this has been improved with automated release scripts which can be executed on our build box.
2. The project follows a documented testing process.
The build box (http://hudson.opengeo.org/hudson/) contains automated testing as part of the build process.
In addition integration tests with databases are available, and CITE conformance tests.
Test coverage of 40% is required for a community module to be promoted for formal inclusion in the application.
CITE test conformance is required for release.
All large modifications, as well as any contribution outside of the core developer circle are subject to peer review.
3. Release and testing processes provide sufficient detail for an experienced programmer to follow.
The Developers Manual includes the section Release Guide documenting how volunteers can step up and make a release.
1. Provide a Project Officer as a contract point: Andrea has accepted the nomination
1. Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's Marketing Artefacts.
2. Ideally, stable version(s) of executable applications are bundled with appropriate distributions.
Platform independent packages as well as Windows and OSX installers are build for every release, moreover platform independent packages are built every night and made available to the user community for testing.
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.
1. The following should be set up: http://geoserver.osgeo.org domain name
2. A project may optionally request SAC help to make use of:
|Document generated by Confluence on May 14, 2014 23:00|