Incubation checklist

PROJ Incubation Checklist

Page to be filled in based on: Project Graduation Checklist

Open: projects are expected to function in an open and public manner and include:
- Open source license (s): MIT License
- Open communication channels: Mailing list, Gitter
- Open decision making process: Decisions are taken based on mailing list communications. The Project Steering Commitee has final say.
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.
  - PROJ has existed for 30+ years. The project has handful of core developers and as many occasional contributors. The developers are spread across almost as many organisations as there are developers attached to the project.

All project source code is available under an Open Source license.
- MIT
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:
- GitHub: https://github.com/OSGeo/proj.4
The project uses an issue tracker and keeps the status of the issue tracker up to date:
- https://github.com/OSGeo/proj.4/issues
The project has documented its management processes:
- https://proj4.org/community/rfc/rfc-1.html

The project has user documentation
- Including sufficient detail to guide a new user through performing the core functionality provided by the application:
  - The PROJ documentation is found at the project website provided in the Using PROJ section and Applications section.
The project has developer documentation:
- Developers Documentation
- Including checkout and build instructions:
  - The documentation describes how to build the official releases from source code as part of the installation section
  - The project README details how to build PROJ from the git repository.
- Including commented code, ideally published for developer use.
  - Det development section of the documentation includes commented examples of using the PROJ API. Additionally, many code examples can be found the test suite and the command line applications that are bundled with PROJ.
- Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions.
  - General contributor guidelines are published here and guidelines for code contributions are available 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.