Marble Incubation Status

From OSGeo
Jump to: navigation, search

Marble has succesfully graduated form Incubation and is now an official OSGeo project.


Has the project been approved for incubation by the OSGeo board?
Has an Incubation Mentor been assigned to the project?
Yes, Arnulf Christl has been assigned as mentor.

Infrastructure Transition

Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.

Has the domain been populated with the projects web presence?
Yes. The project has been populated with the OSGeo Live info sheet. The project has access to a well established environment and there is no need to migrate anything to OSGeo infrastructure.
Is the OSGeo bug tracker being used for the project?
No. The project is happy using the KDE bug tracking infrastructure at
Is the OSGeo mailing list manager ( being used for the project?
No, the project uses the KDE mailing list:
Is the OSGeo SVN being used for the project?
No, the project uses the KDE git repository:
Are binary and source downloads available from ?
No, binaries and sources are available from the project page at:

Community Functioning

Is there a functioning user support mechanisms (ie. mailing list)?
There is a developer mailing list (see above)
The user forum has a daily activity record:
Are source and binary downloads for the package available?
Has a Project Steering Committee been formed, and given control of the project?
Yes. The steering committee is formed by developers who have contributed significantly to the project. In Marble words they are called "maintainer" and the "Maintainer Group" is what OSGeo calls the PSC. It typically requires one or two years of regular code contributions to become a maintainer. The group solve issues in a consensus process. There is currently no formal voting process in place and no apparent need to change this.

Current maintainer (PSC) are:

Current core developers are:

  • Torsten Rahn (Education, Science)
  • Dennis Nienhüser (navigation, routing, devices, cloud)
  • Bernhard Beschow (OpenGL, rendering)
  • Thibaut Gridel (internal data structure)
  • Jens-Michael Hoffmann (OpenStreetMap)

The list of all authors and contributors is available on the project web site at:

The liaison officer for OSGeo will be Torsten Rahn.

Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
Yes. The Marble Manifesto summarizes all processes and points to relevant documents. The KDE Policies are part of the Marble project and include contributor guidelines, etc. The QA
The full history of all decisions that have been taken since inception in 2006 are available through the mailing list archives.
How many active developers are there? Are they from multiple organizations?
The steering group has 3 members from three different organizations. Most code is currently developed by 5 core developers. In total 21 developers have contributed to the project over the past years. Marble is completely built by volunteers which is why there is no single commercial entity currently involved. Contributors come from many different types of organizations the list is available here:

Foundation Membership

Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
Yes, the front page of the public web site has the OSGeo logo in place and links back to OSGeo web site. The core values of the Marble Project can be found here: They line up nicely with OSGeo's mission including efforts of the Education Committee. The OSGeo Live effort is referenced on:
Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
Branding and link back to OSGeo has been added to the Marbke website footer at

Code Copyright Review

Has a Code Provenance Review document been prepared for the project?
Yes, starting point is here: Marble Code Provenance Review
Have issues raised in the provenance review been adequately addressed?
Yes. The History page of the Code Provenance Review shows when individual issues have been addressed, look for things switched from (CHECK) to (clean).
Are Commiter Responsibilities Guidelines covering legal issues in place?
Yes: Adherence to the manifesto is required to become a maintainer / part of the PSC, see above. It has been accepted and is adhered to by all committers.