Oskari Incubation Status

General

1. Has the project been approved for incubation by the OSGeo board?

Yes. The project passed the incubation motion on 23 April 2017 and was approved and confirmed by the Board of Directors in May (see Board Meeting 2017-05-11).

1. Has an Incubation Mentor been assigned to the project?

Yes. Arnulf Christl volunteered as mentor.

Infrastructure Transition

1. Is the OSGeo bug tracker being used for the project? If not, why? Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project? If not, why?

No. We are using GitHub issues as an existing bug tracker: https://github.com/oskariorg/oskari-documentation/issues

1. Is the OSGeo SVN being used for the project? If not, why?

No. An existing version control system is being used for the project: https://github.com/oskariorg (multiple repositories under the GitHub organization). The use of different repositories are described in https://oskari.org/documentation/docs/latest/1-Introduction

1. Are binary and source downloads available from http://download.osgeo.org ? If not, why?

Binary downloads are available in https://download.osgeo.org/oskari/. The source code is available in GitHub with tags and milestones used to mark releases. Download links are also available on the documentation web site: http://oskari.org/download

Community Functioning

1. Is there a functioning user support mechanisms (ie. mailing list)?

Oskari uses the OSGeo Mailing list https://lists.osgeo.org/mailman/listinfo/oskari-user. It's mainly used to notify about upcoming and new releases, but it's not limited to that as users can and have asked questions on the list as well. We are also using Gitter (http://gitter.im/oskariorg/chat) for more interactive user support.

• Update 2026-09-21: Latest version release announcement: https://lists.osgeo.org/pipermail/oskari-user/2026-April/000294.html

1. Are source and binary downloads for the package available?

Downloads are available from the existing web site: http://oskari.org/download

• Update 2026-09-21: Yes, and announced on OSGeo Mailing List https://lists.osgeo.org/pipermail/oskari-user/2026-April/000294.html

1. Has a Project Steering Committee been formed, and given control of the project?

Yes: https://github.com/oskariorg/oskari-docs/wiki/Project-Steering-Committee And: https://oskari.org/community

1. Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines?

Yes: https://github.com/oskariorg/oskari-docs/wiki/Project-Steering-Committee See also: https://gitter.im/oskariorg/psc

• Update 2026-09-21: This document is 10 years old and still under revision, this is probably not up to date: https://github.com/oskariorg/oskari-docs/wiki/Voting

The old PSC-memos can be found here: https://oskariorg.github.io/blog/psc-memo/ We've migrated them to the new oskari.org as blog-posts. There haven't been formal meetings in a while (so we don't have memos of everything), but things have been discussed on GitHub issues, the Gitter chat and in the developer days and Joint development network meetings. Things like which Java-version we should have as the minimum version for Oskari 3.0 has been discussed in both of these meetings.

1. How many active developers are there? Are they from multiple organizations? Indicate number and some organizations involved.

There are more than ten active developers from multiple organizations, both from the public and private sectors. Examples of organizations are National Land Survey of Finland, Natural Resources Institute Finland, Sitowise Ltd, CGI Finland Ltd.

Find more details at https://github.com/oskariorg/oskari-server/graphs/contributors?all=1, https://github.com/oskariorg/oskari-frontend/graphs/contributors?all=1 and https://oskari.org/community (organizational members)

Foundation Membership

1. Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation? If not, indicate when this will occur.

The project documentation has not yet been modified. It was assumed that this can only happen after graduation as to avoid confusion about the official status.

1. Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks? If not, indicate what is planned.

Yes. The OSGeo incubation logo has been added to oskari.org front page and it links to this document.

License

• Update 2026-09-21: This link produces a 404, please update:

https://github.com/oskariorg/oskari-docs/blob/master/LICENSE.md

Code Copyright Review

1. Has a Code Provenance Review document been prepared for the project?

• 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.

1. Have issues raised in the provenance review been adequately addressed? Indicate outstanding issues.

• Currently no outstanding issues.

1. Are Committer Responsibilities Guidelines covering legal issues in place?

• http://www.oskari.org/documentation/development/how-to-contribute
• https://github.com/oskariorg/oskari-docs/blob/master/documents/CLA.txt
  • Update 2026-09-21: The CLA is totally OK - but we should get this out the door soon before we have to somehow deal with AI contributions - which will be somewhat orthogonal to this CLA. But this is currently completely wild country and nobody knows how to deal with it - so applies to basically and software project anyway.