Difference between revisions of "Project Evaluation Criteria"
Jump to navigation
Jump to search
| (11 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
= Document Status = | = Document Status = | ||
| − | ''' | + | '''Version''': 2.0alpha1 |
| − | ''' | + | '''Status''': draft |
| − | ''' | + | '''Last Edited:''' January 5, 2014 |
= Purpose = | = Purpose = | ||
| − | The purpose of this document is to outline the criteria to be used for prioritizing projects for acceptance into the incubation process. | + | 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 = | = 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 [http://www.osgeo.org/incubator/process/project_graduation_checklist.html Project Graduation Checklist]. | ||
| − | = | + | = Desirable = |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
The following are desirable traits of projects entering into the community: | The following are desirable traits of projects entering into the community: | ||
| − | + | # Open source software is already reasonably mature (working quality code). | |
| − | # Open source software is already reasonably mature (working quality code). | ||
# 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. | ||
| Line 34: | Line 29: | ||
# Project is prepared to develop in an open and collaborative fashion. | # Project is prepared to develop in an open and collaborative fashion. | ||
# Project has contributions and interest from more than just one company/organization. | # Project has contributions and interest from more than just one company/organization. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | # | + | = Questions = |
| − | # | + | # Please provide the name and email address of the principal Project Owner. |
| − | # | + | # Please provide the names of co-project owners (if any). |
| − | # | + | # Please provide the names and entity affiliation of all official committers. |
| − | # | + | # Please describe your Project. |
| + | # Why is OSGeo Incubation good for your project? | ||
| + | # What type of application does this project represent(client, server, standalone, library, etc.): | ||
| + | # Please describe any relationships to other open source projects. | ||
| + | # Please describe any relationships with commercial companies or products. | ||
| + | # Please explain how your project will use an open governance policy, ensuring decisions are made, documented and adhered to in a public manner. | ||
| + | # Which open source license(s) will the source code be released under? | ||
| + | # What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? | ||
| + | # How many people actively contribute (code, documentation, other?) to the project at this time? | ||
| + | # How many people have commit access to the source code repository? | ||
| + | # Approximately how many users are currently using this project? | ||
| + | # What type of users does your project attract (government, commercial, hobby, academic research, etc. )? | ||
| + | # Do you wish to host any portion of this project using the OSGeo infrastructure? If so, what? | ||
| + | # Does the project support open standards? Which ones and to what extent? | ||
| + | # Is the code free of patents, trademarks, and do you control the copyright? | ||
| + | # Does the project include an automated build and test? | ||
| + | # What language(s) are used in this project? (C/Java/perl/etc) | ||
| + | # What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? | ||
| + | # What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released? | ||
| − | |||
| − | + | [[Category:Incubation]] | |
Latest revision as of 19:37, 10 March 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.
- Project is prepared to develop in an open and collaborative fashion.
- Project has contributions and interest from more than just one company/organization.
Questions
- Please provide the name and email address of the principal Project Owner.
- Please provide the names of co-project owners (if any).
- Please provide the names and entity affiliation of all official committers.
- Please describe your Project.
- Why is OSGeo Incubation good for your project?
- What type of application does this project represent(client, server, standalone, library, etc.):
- Please describe any relationships to other open source projects.
- Please describe any relationships with commercial companies or products.
- Please explain how your project will use an open governance policy, ensuring decisions are made, documented and adhered to in a public manner.
- Which open source license(s) will the source code be released under?
- What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)?
- How many people actively contribute (code, documentation, other?) to the project at this time?
- How many people have commit access to the source code repository?
- Approximately how many users are currently using this project?
- What type of users does your project attract (government, commercial, hobby, academic research, etc. )?
- Do you wish to host any portion of this project using the OSGeo infrastructure? If so, what?
- Does the project support open standards? Which ones and to what extent?
- Is the code free of patents, trademarks, and do you control the copyright?
- Does the project include an automated build and test?
- What language(s) are used in this project? (C/Java/perl/etc)
- What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers?
- What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released?