OSGEO Graduation

TEAM Engine is in incubation at OSGEO. We never moved it forward. The questions in this checklist need to be filled: https://www.osgeo.org/wp-content/uploads/graduation_checklist.pdf

GeoServer Incubation Checklist

Page to be filled in based on: Project Graduation Checklist

Note: This is a template. Replace comment_here and link_to_... texts with your own responses.

Open: projects are expected to function in an open and public manner and include:
- Open source license (s): comment_here
- Open communication channels: comment_here
- Open decision making process: comment_here
Active and healthy community:
- The project should have a community of developers and users who actively collaborate and support each other in a healthy way.
  - comment_here
- Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations.
  - comment_here

All project source code is available under an Open Source license.
- XYZ License Page
Project documentation is available under an open license.
- User Manual
- License of user Manual
The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included.
- Provenance Review
The project maintains a list of all copyright holders identified in the Provenance Review Document.
- comment_here
All code contributors have agreed to abide by the project’s license policy, and this agreement has been documented and archived.
- comment_here

The project has code under configuration management:
- comment_here
The project uses an issue tracker and keeps the status of the issue tracker up to date:
- comment_here
The project has documented its management processes:
- comment_here

The project has user documentation
- Including sufficient detail to guide a new user through performing the core functionality provided by the application:
  - comment_here
The project has developer documentation:
- [Developers Documentation](link _to_developers_documentation)
- Including checkout and build instructions:
  - [Check out and build instructions](link _to_checkout_build_instructions)
- Including commented code, ideally published for developer use.
  - comment_here
- Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions.
  - comment_here

The project follows a defined release process:
- comment_here
- Which includes execution of the testing process before releasing a stable release.
  - comment_here
The project follows a documented testing process.
- comment_here
- comment_here
Release and testing processes provide sufficient detail for an experienced programmer to follow.
- comment_here

Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee’s Marketing Artefacts.

Ideally, stable version (s) of executable applications are bundled with appropriate distributions.
- comment_here
- OSGeo Live - comment_here

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

The following should be set up: http://geoserver.osgeo.org domain name
- comment_here_can_say_no_requested_if_project_allready_has_it
A project may optionally request SAC help to make use of:
- OSGeo issue tracker - comment_here_can_say_no_requested_if_project_allready_has_it
- OSGeo mailing list - comment_here_can_say_no_requested_if_project_allready_has_it
- OSGeo svn - comment_here_can_say_no_requested_if_project_allready_has_it
- http://downloads.osgeo.org - comment_here_can_say_no_requested_if_project_allready_has_it