Difference between revisions of "Project Evaluation Criteria"
Jump to navigation
Jump to search
(Copied from http://www.osgeo.org/incubator/process/evaluation.html, approved version 1.0 from July 2, 2006) |
|||
| Line 16: | Line 16: | ||
# The project is "geospatial", or directly in support of geospatial applications. | # The project is "geospatial", or directly in support of geospatial applications. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Desirable == | == Desirable == | ||
Revision as of 13:06, 4 January 2014
Document Status
Version: 1.0
Status: approved
Last Edited: July 2, 2006
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.
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 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.
- Project is prepared to develop in an open and collaborative fashion.
- Project has contributions and interest from more than just one company/organization.
- Project is willing to migrate some or all of its infrastructure (code repository, web site, wiki, mailing list, etc) to foundation support infrastructure, and to adopt a website style consistent with the foundation.