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

TEAM Engine Incubation Checklist

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

Incubation Checklist

Open

1. Open: projects are expected to function in an open and public manner and include:
   • Open source license (s): Apache License 2.0
   • Open communication channels: Mailing lists and GitHub issue tracker
   • Open decision making process: comment_here
2. 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.
     • Collaboration is done via GitHub issue tracker.
   • Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations.
   • Multiple companies participate in project.

Copyright and License

1. All project source code is available under an Open Source license.

   • Apache License 2.0

2. Project documentation is available under an open license.

   • User Manual
   • License of user Manual: Apache License 2.0

3. The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included.

   • Provenance Review

4. The project maintains a list of all copyright holders identified in the Provenance Review Document.

   • comment_here

5. All code contributors have agreed to abide by the project’s license policy, and this agreement has been documented and archived.

   • comment_here

Process

1. The project has code under configuration management:

   • Git version control system is used.

2. The project uses an issue tracker and keeps the status of the issue tracker up to date:

   • https://github.com/opengeospatial/teamengine/issues

3. The project has documented its management processes:

   • There are several documents about the management process.
     • Releasing Tests to the OGC Testing Infrastructure
     • Approving a test

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://opengeospatial.github.io/teamengine/

2. The project has developer documentation:

   • Developers Documentation
   • Including checkout and build instructions:
     • Check out and build instructions
   • Including commented code, ideally published for developer use.
     • We don't have commented code requirements because we prefer understandable class and method names.
   • Providing sufficient detail for an experienced programmer to contribute patches or a new module in accordance with the project’s programming conventions.
     • Created CONTRIBUTING.md file

Release Procedure

1. The project follows a defined release process:

   • Release process is documented here: Releasing Tests to the OGC Testing Infrastructure
   • Which includes execution of the testing process before releasing a stable release. Addressed by wiki page on Releasing Tests to the OGC Testing Infrastructure

2. The project follows a documented testing process.

   • The Test Plans are here.

3. Release and testing processes provide sufficient detail for an experienced programmer to follow.

   • The processes are described step-by-step, with details of commands to execute. Therefore any programmer could follow successfully.

OSGeo Committees and Community

Board

1. Provide a Project Officer as a contract point:
   • comment_here

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.

• OSGeo Live - comment_here
• Logo - comment_here

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

Projects

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

• List_interaction_with_other_projects_here

SAC

1. The following should be set up: http://teamengine.osgeo.org domain name
   • comment_here_can_say_no_requested_if_project_allready_has_it
2. 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