Difference between revisions of "Project Graduation Checklist"

From OSGeo
Jump to navigation Jump to search
Line 26: Line 26:
 
== Desirable Items ==
 
== Desirable Items ==
  
 +
# The project has code under configuration control. Eg, subversion.
 +
# The project uses an issue tracker.
 +
# The project uses public communication channels. Eg archieved email lists.
 +
# The project has user documentation.
 +
# The project has developer documentation.
 
# The project has an automated build process.
 
# The project has an automated build process.
 
# The project has an automated test system.
 
# The project has an automated test system.
 +
# The project has documented its management processes which include:
 +
## Roles and responsibilities
 +
## Release process
  
 
= Related Documents =
 
= Related Documents =
  
 
* [[Project Graduation Process]]
 
* [[Project Graduation Process]]

Revision as of 04:33, 19 August 2006

Document Status

IncCom Document Number: X

Version: 1.0

Status: draft

Purpose

The purpose of this checklist is to determine whether or not an Incubator Project is ready for graduation. All mandatory items in the checklist must be completed before a project can be considered for graduation. Completion of the items in this checklist does not necessarily guarantee graduation. Once a project is ready for graduation, it must follow the Project Graduation Process

Terms and Definitions

Mentor
a member of the Incubation Committee chosen to assist a Project through the Incubation Process

Checklist

Mandatory Items

  1. The code has been adequately vetted to assure it is all properly licensed, to the satisfaction of the Mentor.
  2. All code contributors have agreed to abide by the project's license policy.
  3. The project has a suitable governance policy and a project management committee established that ensures decisions can be made, documented and adhered to?
  4. The developer community works in a reasonably healthy way, open to input, new members and reaching consensus on decisions.

Desirable Items

  1. The project has code under configuration control. Eg, subversion.
  2. The project uses an issue tracker.
  3. The project uses public communication channels. Eg archieved email lists.
  4. The project has user documentation.
  5. The project has developer documentation.
  6. The project has an automated build process.
  7. The project has an automated test system.
  8. The project has documented its management processes which include:
    1. Roles and responsibilities
    2. Release process

Related Documents