Project Status Draft - Revision history

Arnulf: Superseded. Redirect to Project Graduation Checklist

2014-05-15T10:21:13Z

Superseded. Redirect to Project Graduation Checklist

Jive: /* Infrastructure */

2014-03-13T09:09:59Z

Infrastructure

Jive: /* Infrastructure */

2014-03-13T09:09:00Z

Infrastructure

Jive: /* Status Template */

2014-03-13T09:06:01Z

Status Template

Jive: /* Community */

2014-03-13T09:05:30Z

Community

Jive: /* Infrastructure */

2014-03-13T08:59:16Z

Infrastructure

Jive: /* Foundation */

2014-03-13T08:58:55Z

Foundation

Jive: /* Review */

2014-03-13T08:56:30Z

Review

Jive: /* Review */

2014-03-13T08:47:37Z

Review

Jive: /* Review */

2014-03-13T08:47:16Z

Review

← Older revision		Revision as of 10:21, 15 May 2014
Line 1:		Line 1:
−	~~= Document Status =~~	+	#redirect[[Project Graduation Checklist]]

−	~~'''Version''': 2.0alpha1~~	+	This page has been superseded. See http://www.osgeo.org/incubator/process/project_graduation_checklist.html for the officially approved version.
−
−	~~'''Status''': draft~~
−
−	~~'''Last Edited:''' March 13, 2014~~
−
−	~~''Previous documents'':~~
−
−	* [http://www.osgeo.org/incubator/process/statustemplate.html status template]
−	* [http://www.osgeo.org/incubator/process/evaluation.html evaluation]
−
−	~~= Purpose =~~
−
−	~~Welcome to the Open Source Geospatial Foundation.~~ This ~~status template is used by your project team (and project mentor) to start incubation and communicate with the incubation committee. As you progress through incubation please update this~~ page ~~as it is an initial indication you are ready for graduation.~~
−
−	~~To assist in answering these questions we have provided the ''evaluation criteria'' used by your mentor~~.
−
−	~~When ready your project mentor will ask you to fill in the final [~~http://www.osgeo.org/incubator/process/project_graduation_checklist.html ~~project graduation checklist]. Your project mentor will cordinate review with the incubation committee and make the final motion~~ for ~~graduation.~~
−
−	~~= Status Template =~~
−
−	~~; Has~~ the ~~project been~~ approved ~~for incubation by the OSGeo board?~~
−	~~: Yes / No - presumably yes.~~
−	~~: ''Desirable: Link to OSGeo board minuets where motion to accept has passed.''~~
−	~~: ''Desirable: Board motion clearly mentions project name and project mentor''~~
−
−	~~; Has an Incubation Mentor been assigned to the project?~~
−	~~: Indicate Incubation committee volunteer acting as project mentor.~~
−	~~: ''Desirable: Board motion clearly mentions project name and project mentor''~~
−
−	~~== Infrastructure ==~~
−
−	~~''We are asking some infrastructure questions up front in case you need any help getting set up. Raise a ticket [[SAC\|system admin committee]] for help.''~~
−
−	~~; Home Page~~
−	~~: The system admin committee needs this information to update http://www.osgeo.org Incubating Projects list.~~
−
−	~~: ''Criteria: vendor neutral home page''~~
−	~~: ''Desirable: Project has contributions and interest from more than just one company/organization.'~~
−	~~: ''Example: http://postgis.net is an example home page, while http://postgis.refractions.net is the original vendor specific home page.~~
−	~~: ''Tip: If you would like a http://project.osgeo.org domain just ask!~~
−
−	~~; Issue Tracker~~
−	~~: If your project is big enough for an issue tracker please provide a link.~~
−
−	~~: ''Desirable: Bugzilla, CodeHaus JIRA, GitHub Issues, SourceForge etc..''~~
−	~~: ''Tip: OSGeo can setup a bug tracker on request.''~~
−
−	~~; Mailing Lists~~
−	~~: What are your project mailing lists? Your project mentor will need this information to sign up to the development mailing list.~~
−
−	~~: ''Criteria: Public mailing list~~
−	~~: ''Desirable: Demonstrate communication with users.~~
−	~~: ''Tip: If you need a new mailing list at lists.osgeo.org please ask.''~~
−
−	~~; Version Control~~
−	~~: How can developers access the source code?~~
−
−	~~: ''Criteria: public codebase''~~
−	~~: ''Tip: OSGeo can provide subversion hosting if requested''~~
−
−	~~; Downloads~~
−	~~: Where can we download binary and source bundles?~~
−
−	~~: ''Desirable: History of releasing software''~~
−	~~: ''Tip: OSGeo can provide publication at http://downloads.osgeo.org/ is needed''~~
−
−	~~==Community==~~
−
−	~~; Is there a functioning user support mechanisms (ie. mailing list)?~~
−	~~: indicate the available user support mechanisms, and whether they seem to be functioning well (are getting used and get answers).~~
−
−	~~: ''Tip: This is your chance to mention a user guide, project wiki, mailing list, IRC channel or participation in support site such as http://gis.stackexchange.com''~~
−
−	~~; Are source and binary downloads for the package available?~~
−	~~: yes/no (and any caveats)~~
−
−	~~: ''Desirable: History of releasing software''~~
−
−	~~; Has a Project Steering Committee been formed, and given control of the project?~~
−	~~: yes/no, indicate members and whether it has effective control.~~
−
−	~~: ''Criteria: public decision making process (meeting minuets or request for chance procedure)''~~
−	~~: ''Desirable: Opportunity for public participation in project direction''~~
−	~~: ''Tip: Many projects use [http://mapserver.org/development/rfc/ MapServer RFC] procedure as a starting point ''~~
−
−	~~; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.~~
−	~~: Link to developers guide or similar~~
−
−	~~: ''Criteria: public decision making process''~~
−
−	~~; How many active developers are there? Are they from multiple organizations?~~
−	~~: Indicate number and some organizations involved.~~
−
−	~~==Foundation==~~
−
−	~~; Has an effort been made to brand the project web site with OSGeo Incubation logo?~~
−	~~: OSGeo logos, including project in incubation logo, are provided [http://www.osgeo.org/logos here].~~
−
−	~~: ''Criteria: OSGeo Incubation Logo on home page''~~
−	~~: ''Desirable: Image links to http://osgeo.org/ home page''~~
−
−	~~; Have project documents been updated to reflect participation in OSGeo Incubation?~~
−	~~: Just looking to acknowledge participation.~~
−
−	~~: ''Criteria: Reflect membership in OSGeo Foundation''~~
−	~~: ''Criteria: Incubation Status''~~
−
−	~~==Review==~~
−
−	~~; Are Committer Responsibilities Guidelines covering legal issues in place?~~
−	~~: Link to the guidelines and comitter acceptance~~
−
−	~~: ''Criteria: Indicate if committer guidelines have been adopted by project steering committee (or similar)~~
−	~~: ''Criteria: Record showing all committers have accepted guidelines~~
−	~~: ''Criteria: Guidelines provide clear permission for project to distribute contributions~~
−	~~: ''Desirable: Public record of committer acceptance preferred''~~
−
−	~~; Has a Code Provenance Review document been prepared for the project?~~
−	~~: Link to review document (often a wiki page or google document)~~
−
−	~~: ''Criteria: Ensure project owns (or has otherwise obtained permission) to source code used''~~
−	~~: ''Criteria: Ensure project owns (or has otherwise obtained permission) for any sample data used''~~
−	~~: ''Tip: Check [[Incubation_Committee#Graduated graduated projects]] for ideas, or review draft [[Code_Provenance_Review]]''~~
−	~~: ''Desirable: Headers provide clear indication of copyright and distribution license~~
−
−	~~; Have issues raised in the provenance review been adequately addressed?~~
−	~~: Link to outstanding issues~~
−
−	~~: ''Tip: Once again [[Incubation_Committee#Graduated graduated projects]] for ideas~~. ~~Projects have used issue trackers, or simply linked to archived email discussions''~~

@@ Line 40: / Line 40: @@
 :   ''Criteria: vendor neutral home page''
 :   ''Desirable: Project has contributions and interest from more than just one company/organization.'
-:   ''Example: [http://postgis.net] is an example home page, while [http://postgis.refractions.net] is the original vendor specific home page.
+:   ''Example: http://postgis.net is an example home page, while http://postgis.refractions.net is the original vendor specific home page.
-:   ''Tip: If you would like a http://project name.osgeo.org domain just ask!
+:   ''Tip: If you would like a http://project.osgeo.org domain just ask!
 ; Issue Tracker
@@ Line 66: / Line 66: @@
 :   ''Desirable: History of releasing software''
-:   ''Tip: OSGeo can provide http://downloads.osgeo.org/ is needed''
+:   ''Tip: OSGeo can provide publication at http://downloads.osgeo.org/ is needed''
 ==Community==

@@ Line 40: / Line 40: @@
 :   ''Criteria: vendor neutral home page''
 :   ''Desirable: Project has contributions and interest from more than just one company/organization.'
-:   ''Example: [[http://postgis.net]] is an example home page, while [[http://postgis.refractions.net]] is the original vendor specific home page.
+:   ''Example: [http://postgis.net] is an example home page, while [http://postgis.refractions.net] is the original vendor specific home page.
 :   ''Tip: If you would like a http://project name.osgeo.org domain just ask!

@@ Line 24: / Line 24: @@
 ; Has the project been approved for incubation by the OSGeo board?
 :   Yes / No - presumably yes.
-:   ''Criteria: Link to OSGeo board minuets where motion to accept has passed.''
+:   ''Desirable: Link to OSGeo board minuets where motion to accept has passed.''
 :   ''Desirable: Board motion clearly mentions project name and project mentor''

@@ Line 72: / Line 72: @@
 ; Is there a functioning user support mechanisms (ie. mailing list)?
 :  indicate the available user support mechanisms, and whether they seem to be functioning well (are getting used and get answers).
 ; Are source and binary downloads for the package available?
 :  yes/no (and any caveats)
 ; Has a Project Steering Committee been formed, and given control of the project?
 : yes/no, indicate members and whether it has effective control.
 ; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
-: yes/no - provide pointers to various related documents.
+: Link to developers guide or similar
 ; How many active developers are there? Are they from multiple organizations?

@@ Line 37: / Line 37: @@
 ; Home Page
 :   The system admin committee needs this information to update http://www.osgeo.org Incubating Projects list.
 :   ''Criteria: vendor neutral home page''
 :   ''Desirable: Project has contributions and interest from more than just one company/organization.'
@@ Line 44: / Line 45: @@
 ; Issue Tracker
 :   If your project is big enough for an issue tracker please provide a link.
 :   ''Desirable: Bugzilla, CodeHaus JIRA, GitHub Issues, SourceForge etc..''
 :   ''Tip: OSGeo can setup a bug tracker on request.''
@@ Line 49: / Line 51: @@
 ; Mailing Lists
 :   What are your project mailing lists? Your project mentor will need this information to sign up to the development mailing list.
 :  ''Criteria: Public mailing list
 :  ''Desirable: Demonstrate communication with users.
@@ Line 55: / Line 58: @@
 ; Version Control
 :   How can developers access the source code?
 :   ''Criteria: public codebase''
 :   ''Tip: OSGeo can provide subversion hosting if requested''
@@ Line 60: / Line 64: @@
 ; Downloads
 :   Where can we download binary and source bundles?
 :   ''Desirable: History of releasing software''
 :   ''Tip: OSGeo can provide http://downloads.osgeo.org/ is needed''

@@ Line 83: / Line 83: @@
 ; Has an effort been made to brand the project web site with OSGeo Incubation logo?
 : ''Criteria: OSGeo Incubation Logo on home page''
 : ''Desirable: Image links to http://osgeo.org/ home page''
 ; Have project documents been updated to reflect participation in OSGeo Incubation?
 : ''Criteria: Reflect membership in OSGeo Foundation''
 : ''Criteria: Incubation Status''

@@ Line 91: / Line 91: @@
 ==Review==
 ; Has a Code Provenance Review document been prepared for the project?
@@ Line 97: / Line 105: @@
 : ''Criteria: Ensure project owns (or has otherwise obtained permission) to source code used''
 : ''Criteria: Ensure project owns (or has otherwise obtained permission) for any sample data used''
-: ''Tip: For ideas on how to review check out what other projects have done, or check [[Code_Provenance_Review]]''
+: ''Tip: Check [[Incubation_Committee#Graduated graduated projects]] for ideas, or review draft [[Code_Provenance_Review]]''
 ; Have issues raised in the provenance review been adequately addressed?
 : Link to outstanding issues
-: ''Tip: Once again check other projects for ideas. Projects have used issue trackers, or simply linked to archived email discussions''
+: ''Tip: Once again [[Incubation_Committee#Graduated graduated projects]] for ideas. Projects have used issue trackers, or simply linked to archived email discussions''

@@ Line 102: / Line 102: @@
 : Link to outstanding issues
-* ''Tip: Once again check other projects for ideas. Projects have used issue trackers, or simply linked to archived email discussions''
+: ''Tip: Once again check other projects for ideas. Projects have used issue trackers, or simply linked to archived email discussions''
 ; Are Committer Responsibilities Guidelines covering legal issues in place?
 : Link to the guidelines and comitter acceptance
-* ''Criteria: Indicate if committer guidelines have been adopted by project steering committee (or similar)
+: ''Criteria: Indicate if committer guidelines have been adopted by project steering committee (or similar)
-* ''Criteria: Record showing all committers have accepted guidelines
+: ''Criteria: Record showing all committers have accepted guidelines
-* ''Desirable: Public record of committer acceptance preferred''
+: ''Desirable: Public record of committer acceptance preferred''

@@ Line 95: / Line 95: @@
 : Link to review document (often a wiki page or google document)
-* ''Criteria: Ensure project owns (or has otherwise obtained permission) to source code used''
+: ''Criteria: Ensure project owns (or has otherwise obtained permission) to source code used''
-* ''Criteria: Ensure project owns (or has otherwise obtained permission) for any sample data used''
+: ''Criteria: Ensure project owns (or has otherwise obtained permission) for any sample data used''
-* ''Tip: For ideas on how to review check out what other projects have done, or check [[Code_Provenance_Review]]''
+: ''Tip: For ideas on how to review check out what other projects have done, or check [[Code_Provenance_Review]]''
 ; Have issues raised in the provenance review been adequately addressed?