Difference between revisions of "Project Evaluation Criteria"
| Line 44: | Line 44: | ||
# The project proposal includes a scope of work that defines what is to be built. The scope should include requirements and at least minimal design elements so that reviewers understand what is to be built. | # The project proposal includes a scope of work that defines what is to be built. The scope should include requirements and at least minimal design elements so that reviewers understand what is to be built. | ||
# Mockups (if applicable) and/or prototypes of the software to be built (desirable, but not necessary). | # Mockups (if applicable) and/or prototypes of the software to be built (desirable, but not necessary). | ||
| − | # A list of other software members of the team have worked on. | + | # A list of other software that members of the team have worked on. |
= Related Documents = | = Related Documents = | ||
* documents | * documents | ||
Revision as of 09:15, 22 May 2006
Document Status
IncCom Document Number: X
Version: 1.0
Status: draft
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.
Terms and Definitions
- term
- definition
Criteria
Required
- 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 (committer agreements, etc). (?? is this still required ??)
- 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 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.
New Project Proposals To Be Considered By The Incubation Committee
Not all projects are mature. It is understood that it takes time for a project to be created and become viable, but that a community like OSGeo.org and its hosting software would benefit the project. However, the foundation and the community want to make sure that the project is well conceived, properly supported, and worthy of the foundation's resources, and volunteer's time. The following should also be desirable when presenting a new project:
- A detailed proposal of what is to be built and why it applies to the OSGeo foundation.
- The person making the proposal is fully capable of developing the software or has a team that is capable of producing the software.
- The project proposal includes a scope of work that defines what is to be built. The scope should include requirements and at least minimal design elements so that reviewers understand what is to be built.
- Mockups (if applicable) and/or prototypes of the software to be built (desirable, but not necessary).
- A list of other software that members of the team have worked on.
Related Documents
- documents