Oskari Incubation Checklist

Open

Open: projects are expected to function in an open and public manner and include:
- Open source license (s): MIT & EUPL, see GitHub
- Open communication channels: Gitter, OSGeo -mailing list
- Open decision making process: See GitHub
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.
  - See GitHub
- Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations.
  - See GitHub

All project source code is available under an Open Source license.
- see GitHub
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 (All code has been developed by the registered developers listed on github who have signed the CLA. All external libraries have project compatible licenses. The project has been started as a regular Open Source project following the guidelines as set out by OSGeo. A file-per-file code review was therefore deemed superfluous.)
The project maintains a list of all copyright holders identified in the Provenance Review Document.
- n/a
All code contributors have agreed to abide by the project’s license policy, and this agreement has been documented and archived.
- The archived original versions of CLAs are at the National Land Survey of Finland

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

The project has user documentation
- Including sufficient detail to guide a new user through performing the core functionality provided by the application:
  - See oskari.org/documentation
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.
  - See GitHub
- Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project’s programming conventions.
  - Developers Documentation

The project follows a defined release process:
- 4-8 releases annually
- Which includes execution of the testing process before releasing a stable release.
  - Automated tests and manual testing before each release
The project follows a documented testing process.
- JUnit tests for server builds
- Jest tests for frontend builds
Release and testing processes provide sufficient detail for an experienced programmer to follow.
- See documentation

Provide a Project Officer as a contract point:
- Timo Aarnio ([email protected])

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.
- A ready to run version bundled with Jetty is available from oskari.org/download
- OSGeo Live - n/a

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