Marble Graduation Checklist

Marble has succesfully graduated form Incubation on 17 October 2013 and is now an official OSGeo project. 
= Incubation Checklist =
More details are linked from the corresponding section on the Marble Incubation Status page. 
== Open ==
	 
The project has demonstrated that it has an open, active and healthy user and developer community:	
# Open: projects are expected to function in an open and public manner and include:
#* Open source license: GNU Lesser General Public License (LGPL) version 2.1
#* Open communication channels: Mailing Lists, IRC, Wiki
#* Open decision making process: Open developer mailing list
# Active and healthy community: Yes
#* The project has a community of developers and users who actively collaborate and support each other in a healthy way. Yes
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. The project is resilient enough to sustain loss of a developer. It has a bus factor of 5. Decisions are made openly, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.
== Copyright and License ==
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license. Yes
# Project documentation is available under an open license, such as Creative Commons. Yes
# The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a Provenance Review. Yes, see Marble Code Provenance Review
# The project maintains a list of all copyright holders identified in the Provenance Review Document. 'Yes
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. 'Yes
== Processes ==
# The project has code under configuration management. Yes
# The project uses an issue tracker and keeps the status of the issue tracker up to date. Yes
# The project has documented its management processes. Yes: http://techbase.kde.org/Projects/Marble/GoMarble
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. Yes
#* The project uses public communication channels for decision making to maintain transparency. Yes
== Documentation ==
# The project has user documentation: Yes: http://marble.kde.org/documentation.php
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application. Yes
# The project has developer documentation:
#* Including checkout and build instructions. Yes: http://marble.kde.org/sources.php
#* Including commented code, ideally published for developer use. Yes
#* Providing sufficient detail for an experienced programmer to contribute patches or a new module in accordance with the project's programming conventions. Yes
==Release Procedure==
In order to maintain a consistent level of quality, the project should follow defined release and testing processes. As a KDE project Marble follows the processes defined in the KDE community.
# The project follows a defined release process: Yes: http://techbase.kde.org/Policies
#* Which includes execution of the testing process before releasing a stable release. Yes
# The project follows a documented testing process. Yes: QA page with code checker
# Release and testing processes provide sufficient detail for an experienced programmer to follow. Yes
= OSGeo Committees and Community =
The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.
== Board ==
The OSGeo Board holds ultimate responsibility for all OSGeo activities. The Board requests:
# A project provide a Project Officer as a contract point: Yes
#* The Project Officer should be listed at: Project Officer
#* This person is established when the incubation committee recommends the project for graduation.
#* Your community can change the project officer as needed (just add an agenda item to the next board meeting so they can recognise the change of officer).
== Marketing ==
Access to OSGeo's Marketing_Committee and associated Marketing_Pipeline is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:
# Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's Marketing Artefacts. This lists the documentation requirements for OSGeo-Live. Marketing Artefacts include:
#* Application Overview Yes
#* Application Quick Start Yes
#* Logo Yes
#* Graphical Image Yes
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. Yes
* OSGeo-Live
* Debian
* Ubuntu
* KDE
* many more...
== Projects ==
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. 
Marble is part of a major release process within the KDE community. As a desktop application there are not many dependencies to other libraries. 
== SAC ==
The System Administration Committee is available to help infrastructure and facilities. Information for this committee is collected as part of the Project Status Template. The following should be set up:
* http://osgeo.org/marble has been set up.
A project may optionally request SAC help to make use of: None required, the project is in a safe haven at the KDE community-
* OSGeo issue tracker
* OSGeo mailing list
* OSGeo svn
* http://downloads.osgeo.org
Category: Incubation