Marble Graduation Checklist - Revision history

Arnulf at 13:25, 20 November 2013

2013-11-20T13:25:53Z

Arnulf at 10:27, 22 October 2013

2013-10-22T10:27:18Z

Arnulf at 10:24, 22 October 2013

2013-10-22T10:24:13Z

Arnulf at 10:22, 22 October 2013

2013-10-22T10:22:08Z

Wiki-Torsten Rahn: /* Documentation */

2013-09-12T12:37:48Z

Documentation

Arnulf: /* Release Procedure */

2013-09-12T11:01:47Z

Release Procedure

Arnulf: /* Processes */

2013-09-12T11:00:01Z

Processes

Arnulf: /* Incubation Checklist */

2013-09-12T10:48:17Z

Incubation Checklist

Arnulf: Created page with "= Incubation Checklist = Further details are available on the Marble Project Status page. == Open == The project has demonstrated that it has an open, active and healthy..."

2013-09-12T10:47:08Z

Created page with "= Incubation Checklist = Further details are available on the Marble Project Status page. == Open == The project has demonstrated that it has an open, active and healthy..."

New page

= Incubation Checklist =
Further details are available on the [[Marble Project 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 [http://en.wikipedia.org/wiki/Bus_factor 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 [http://www.osgeo.org/incubator/process/codereview.html 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''
#* 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'''
#* 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: 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'''
# 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: [[Contacts#Software_Projects|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 [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for [http://live.osgeo.org 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'''
* [http://live.osgeo.org OSGeo-Live]
* [http://debian.org/ Debian]
* [https://ubuntu.com Ubuntu]
* [http://edu.kde.org/marble/ 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 [[SAC|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]]

← Older revision		Revision as of 13:25, 20 November 2013
Line 1:		Line 1:
−	'''''Marble has succesfully [http://wiki.osgeo.org/wiki/Press_Release_Marble_Virtual_Globe_Graduates_Incubation graduated form Incubation] and is now an official OSGeo project. '''''	+	'''''Marble has succesfully [http://wiki.osgeo.org/wiki/Press_Release_Marble_Virtual_Globe_Graduates_Incubation graduated form Incubation] on 17 October 2013 and is now an official OSGeo project. '''''

	= Incubation Checklist =		= Incubation Checklist =

← Older revision		Revision as of 10:27, 22 October 2013
Line 97:		Line 97:

	[[Category: Incubation]]		[[Category: Incubation]]
−	~~[[Category:OSGeo Project]]~~

← Older revision		Revision as of 10:24, 22 October 2013
Line 97:		Line 97:

	[[Category: Incubation]]		[[Category: Incubation]]
		+	[[Category:OSGeo Project]]

← Older revision		Revision as of 10:22, 22 October 2013
Line 1:		Line 1:
		+	'''''Marble has succesfully [http://wiki.osgeo.org/wiki/Press_Release_Marble_Virtual_Globe_Graduates_Incubation graduated form Incubation] and is now an official OSGeo project. '''''
		+
	= Incubation Checklist =		= Incubation Checklist =
	More details are linked from the corresponding section on the [[Marble Incubation Status]] page.		More details are linked from the corresponding section on the [[Marble Incubation Status]] page.

@@ Line 35: / Line 35: @@
 #* 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'''
+#* 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'''

@@ Line 43: / Line 43: @@
 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: http://techbase.kde.org/Policies
+# 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'''
+# The project follows a documented testing process.  '''Yes: [http://www.englishbreakfastnetwork.org/krazy/reports/kde-4.x/kdeedu/marble/index.html QA page with code checker]'''
 # Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes'''

@@ Line 26: / Line 26: @@
 # 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''
+# 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'''

@@ Line 1: / Line 1: @@
 = Incubation Checklist =
-Further details are available on the [[Marble Project Status]] page.
+More details are linked from the corresponding section on the [[Marble Incubation Status]] page.
 == Open ==