Revision as of 01:46, 13 March 2014

Document Status

Version: 2.0alpha1

Status: draft

Last Edited: March 13, 2014

Previous documents:

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 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.; Criteria: 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 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: [[1]] is an example home page, while [[2]] is the original vendor specific home page.; Tip: If you would like a http://project name.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 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).

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.

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?: 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

Review

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: 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?: Link to outstanding issues

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: Record showing all committers have accepted guidelines
Desirable: Public record of committer acceptance preferred

@@ Line 93: / Line 93: @@
 ; Has a Code Provenance Review document been prepared for the project?
-: Please provide a link to review document (often a wiki page or google document)
+: Link to review document (often a wiki page or google document)
 * ''Criteria: Ensure project owns (or has otherwise obtained permission) to source code used''
@@ Line 100: / Line 100: @@
 ; Have issues raised in the provenance review been adequately addressed?
-: Provide a link to outstanding issues
+: Link to outstanding issues
 * ''Tip: Once again check other projects for ideas. Projects have used issue trackers, or simply linked to archived email discussions''

Difference between revisions of "Project Status Draft"