Project Graduation Checklist - Revision history

Arnulf: /* Review Notes */ link updated

2018-07-25T11:15:28Z

Review Notes: link updated

Arnulf: This page is outdated! Link to current Incubation Checklist on the OSGeo web site updated and note added.

2018-07-25T11:14:34Z

This page is outdated! Link to current Incubation Checklist on the OSGeo web site updated and note added.

Wiki-Camerons at 10:00, 12 January 2018

2018-01-12T10:00:03Z

Jmckenna: /* Marketing */ update MS4W link

2016-09-22T19:42:45Z

Marketing: update MS4W link

Wiki-Camerons: /* Release Procedure */

2016-09-06T10:42:17Z

Release Procedure

Wiki-Camerons: Moved "Code of Conduct"

2016-09-06T10:28:54Z

Moved "Code of Conduct"

Wiki-Camerons: Removed: [open.2d] Users are supported and encouraged, via an email list or similar.

2016-09-06T10:20:17Z

Removed: [open.2d] Users are supported and encouraged, via an email list or similar.

Wiki-Camerons: /* Processes */

2015-08-04T21:09:02Z

Processes

Wiki-Camerons: /* Processes */

2015-04-30T23:51:19Z

Processes

Wiki-Camerons: /* Processes */

2015-01-25T20:48:28Z

Processes

@@ Line 4: / Line 4: @@
 = <span style="color:red">Review Notes</span> =
-* <span style="color:red">This wiki provides a draft for a 3.0 version of the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html Project Graduation Checklist].</span>
+* <span style="color:red">This wiki provides a draft for a 3.0 version of the [https://www.osgeo.org/resources/project-graduation-checklist/ Project Graduation Checklist].</span>
 * <span style="color:red">It incorporates some content from the OSGeo [[General_Principles_of_Incubation]], which is proposed to be retired.</span>
 * <span style="color:red">It incorporates some concepts from the [[Live_GIS_Disc_Apply| selection criteria for adding a project to OSGeoLive]].</span>

← Older revision		Revision as of 11:14, 25 July 2018
Line 1:		Line 1:
		+	'''Please note that this Wiki page is out of date. Find the current Checklist on the official OSGeo web site at: https://www.osgeo.org/resources/project-graduation-checklist/'''
		+
		+	------
		+
	= <span style="color:red">Review Notes</span> =		= <span style="color:red">Review Notes</span> =
	* <span style="color:red">This wiki provides a draft for a 3.0 version of the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html Project Graduation Checklist].</span>		* <span style="color:red">This wiki provides a draft for a 3.0 version of the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html Project Graduation Checklist].</span>

@@ Line 1: / Line 1: @@
 = <span style="color:red">Review Notes</span> =
 * <span style="color:red">This wiki provides a draft for a 3.0 version of the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html Project Graduation Checklist].</span>
-* <span style="color:red">It also incorporates some content from the OSGeo [[General_Principles_of_Incubation]], which is proposed to be retired.</span>
+* <span style="color:red">It incorporates some content from the OSGeo [[General_Principles_of_Incubation]], which is proposed to be retired.</span>
 * <span style="color:red"> New text is in red font. Removed text in strike font. All points in the checklist now have an indentifier.</span>
 * <span style="color:red"> When publishing the final section, these Review Notes will be removed.</span>

@@ Line 107: / Line 107: @@
 #* <span id="marketing.1c">[marketing.1c]</span> Logo
 #* <span id="marketing.1d">[marketing.1d]</span> Graphical Image
-# <span id="marketing.2">[marketing.2]</span> Ideally, stable version(s) of executable applications are bundled with appropriate distributions.<br/><i>In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.maptools.org/ms4w/ ms4w], etc.)</i>
+# <span id="marketing.2">[marketing.2]</span> Ideally, stable version(s) of executable applications are bundled with appropriate distributions.<br/><i>In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.ms4w.com ms4w], etc.)</i>
 # <span id="marketing.3" style="color: red">[marketing.3] The project incorporates OSGeo branding, such as including an OSGeo logo on its website.</span>
 # <span id="marketing.4" style="color: red">[marketing.4] The project has been registered with Open HUB, and Open HUB has been updated to reference the correct code repository(s) for the project. [https://www.openhub.net/ Open HUB] provides metrics to help assess the health of a project. </span>

@@ Line 76: / Line 76: @@
 # <span id="release.1">[release.1]</span> The project follows a defined release process:
-#* <span id="release.1a" style="color:red">[release.1a] Which supports both stable and development releases.</span>
+#* <span id="release.1a" style="color:red"><strike>[release.1a] Which supports both stable and development releases.</strike></span>
 #* <span id="release.1b">[release.1b]</span> Which includes execution of the testing process before releasing a stable release.
 # <span id="release.2">[release.2]</span> The project follows a documented testing process.

@@ Line 41: / Line 41: @@
 #* <span id="open.2c">[open.2c] Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.</span>
 #* <span id="open.2d" style="color:red"><strike>[open.2d] Users are supported and encouraged, via an email list or similar.</strike></span>
 == Copyright and License ==
@@ Line 58: / Line 59: @@
 #* <span id="processes.3a">[processes.3a]</span> The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. <br/><i>This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.</i>
 #* <span id="processes.3b">[processes.3b]</span> The project uses public communication channels for decision making to maintain transparency.<br/><i> E.g. archived email list(s), archived IRC channel(s), public issue tracker.</i>
 == Documentation ==

@@ Line 56: / Line 56: @@
 # <span id="processes.2">[processes.2]</span> The project uses an issue tracker and keeps the status of the issue tracker up to date.
 # <span id="processes.3">[processes.3]</span> The project has documented <span style="color:red">and follows</span> its management processes. <br/><i>This is typically done within a Developers Guide or Project Management Plan.</i>
-#* <span id="processes.3a">[processes.2a]</span> The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. <br/><i>This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.</i>
+#* <span id="processes.3a">[processes.3a]</span> The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. <br/><i>This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.</i>
-#* <span id="processes.3b">[processes.2b]</span> The project uses public communication channels for decision making to maintain transparency.<br/><i> E.g. archived email list(s), archived IRC channel(s), public issue tracker.</i>
+#* <span id="processes.3b">[processes.3b]</span> The project uses public communication channels for decision making to maintain transparency.<br/><i> E.g. archived email list(s), archived IRC channel(s), public issue tracker.</i>
-# <span style="color:red"><span id="processes.4" style="color:red">[processes.3]</span> The project has a Code of Conduct. <br/><i>This may be a reference to the OSGeo Code of Conduct. (TBD OSGeo Code of Conduct is yet to be written).</i></span>
+# <span style="color:red"><span id="processes.4" style="color:red">[processes.4]</span> The project has a Code of Conduct. <br/><i>This may be a reference to the OSGeo Code of Conduct. (TBD OSGeo Code of Conduct is yet to be written).</i></span>
 == Documentation ==