Difference between revisions of "Project Graduation Checklist"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
# The developer community works in a reasonably healthy way, open to input, new members and reaching consensus on decisions. | # The developer community works in a reasonably healthy way, open to input, new members and reaching consensus on decisions. | ||
| − | == | + | == Desirable Items == |
| − | # The project has | + | # The project has an automated build process. |
| − | # | + | # The project has an automated test system. |
= Related Documents = | = Related Documents = | ||
* [[Project Graduation Process]] | * [[Project Graduation Process]] | ||
Revision as of 04:19, 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
- The code has been adequately vetted to assure it is all properly licensed, to the satisfaction of the Mentor.
- The project has a suitable governance policy and a project management committee established that ensures decisions can be made, documented and adhered to?
- The developer community works in a reasonably healthy way, open to input, new members and reaching consensus on decisions.
Desirable Items
- The project has an automated build process.
- The project has an automated test system.