Marble Incubation Status

The project representative and mentor uses this template to inform the IncCom of the project status on a periodic basis. The state of the project, as reported using this template, will be the initial indication that a project is reaching graduation.

General

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

Yes

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 projectname.osgeo.org domain been populated with the projects web presence?

Yes. The project http://www.osgeo.org/marble 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 https://bugs.kde.org/

Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?

No, the project uses the KDE mailing list: https://mail.kde.org/mailman/listinfo/marble-devel

Is the OSGeo SVN being used for the project?

No, the project uses the KDE git repository: http://marble.kde.org/sources.php

Are binary and source downloads available from http://download.osgeo.org ?

No, binaries and sources are available from the project page at: http://marble.kde.org/install.php

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: http://forum.kde.org/viewforum.php?f=217

Are source and binary downloads for the package available?

Yes:

http://marble.kde.org/install.php

http://marble.kde.org/sources.php

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

An (in)official steering committee is formed by the maintainers, core contributors who have contributed significantly to the project. It typically requires one or two years of regular code contributions to become a maintainer. The group has so far managed to solve all issues in a consensus process and there is currently seen no need to change this. 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:

http://techbase.kde.org/Projects/Marble/GoMarble/Manifesto

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 (in)formal Project Steering Committee currently has x members. 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?

In progress.

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 http://marble.kde.org/.

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?

indicate outstanding issues.

Are Commiter Responsibilities Guidelines covering legal issues in place?

yes/no - point to the guidelines and indicate if it is adopted by PSC, and accepted by all commiters.