Difference between revisions of "Project Evaluation Criteria"
Jump to navigation
Jump to search
(Actually, this is the version 1.0 (I made mistakes in last copy)) |
(Drop requirements for use of OSGeo infrastructure, and reference Project Graduation Criteria) |
||
| Line 1: | Line 1: | ||
= Document Status = | = Document Status = | ||
| − | '''Version''': | + | '''Version''': 2.0alpha1 |
| − | '''Status''': | + | '''Status''': draft |
| − | '''Last Edited:''' | + | '''Last Edited:''' January 5, 2014 |
= Purpose = | = Purpose = | ||
| Line 13: | Line 13: | ||
= Criteria = | = Criteria = | ||
# The code is under an OSI approved license (data & doc projects need to specify their choice for a type of license). | # The code is under an OSI approved license (data & doc projects need to specify their choice for a type of license). | ||
| − | # The project is willing to keep code clear of encumbrances | + | # The project is willing to keep code clear of encumbrances. |
# The project is "geospatial", or directly in support of geospatial applications. | # The project is "geospatial", or directly in support of geospatial applications. | ||
| − | + | # The project is committed to work to address requirements of OSGeo's [http://www.osgeo.org/incubator/process/project_graduation_checklist.html Project Graduation Checklist]. | |
= Desirable = | = Desirable = | ||
| Line 23: | Line 23: | ||
# Project already has a substantial user community. | # Project already has a substantial user community. | ||
# Project already has a substantial and diverse developer community. | # Project already has a substantial and diverse developer community. | ||
| + | # Project has contributions and interest from more than just one company/organization. | ||
# Project members are aware of, and implements support for, relevant standards (ie. OGC, etc). | # Project members are aware of, and implements support for, relevant standards (ie. OGC, etc). | ||
# Project has linkages with existing foundation projects. | # Project has linkages with existing foundation projects. | ||
# Project fills a gap related to software that the foundation supports. | # Project fills a gap related to software that the foundation supports. | ||
| − | |||
| − | |||
| − | |||
[[Category:Incubation]] | [[Category:Incubation]] | ||
Revision as of 14:22, 4 January 2014
Document Status
Version: 2.0alpha1
Status: draft
Last Edited: January 5, 2014
Purpose
The purpose of this document is to outline the criteria to be used for prioritizing projects for acceptance into the incubation process. The project must fully meet, or be capable of meeting by graduation, the Required Criteria. Projects should meet some or all of the Desirable Criteria. The intention is that the more criteria a project meets, the more likely it will be accepted for incubation.
Criteria
- The code is under an OSI approved license (data & doc projects need to specify their choice for a type of license).
- The project is willing to keep code clear of encumbrances.
- The project is "geospatial", or directly in support of geospatial applications.
- The project is committed to work to address requirements of OSGeo's Project Graduation Checklist.
Desirable
The following are desirable traits of projects entering into the community:
- Open source software is already reasonably mature (working quality code).
- Project already has a substantial user community.
- Project already has a substantial and diverse developer community.
- Project has contributions and interest from more than just one company/organization.
- Project members are aware of, and implements support for, relevant standards (ie. OGC, etc).
- Project has linkages with existing foundation projects.
- Project fills a gap related to software that the foundation supports.