GRASS Incubation Progress
Revision as of 09:36, 26 April 2007 by Arnulf (talk | contribs) (→Mentor Notes: added links to earlier source code vetting)
Document Purpose
The mentor will use this to inform the Incubation Committee of the project status and it will be the initial indication that a project is reaching graduation.
Basics
- Has the project been approved for incubation by the OSGeo board?
- Yes, and GRASS-PSC formed
- Has an Incubation Mentor been assigned to the project?
- Norman Vine and Arnulf Christl are assigned mentors.
Infrastructure Transition
Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.
- Has the projectname.osgeo.org domain been populated with the projects web presence?
http://grass.osgeo.orghttp://www.osgeo.org/grass has been populated.
- Is the OSGeo bug tracker being used for the project?
- Currently the existing bug tracker is used. A migration may be possible in future.
- Is the OSGeo mailing list manager being used for the project?
- The announce list will be used, the other mailing lists will remain under http://grass.itc.it to maintain the long archives of emails (starting 1991).
- Is the OSGeo SVN or CVS system being used for the project?
- Currently the existing CVS is used. A migration may be possible in future.
- Are binary and source downloads available from the OSGeo download area?
- Yes. http://download.osgeo.org/grass/
Community Functioning
- Is there a functioning user support mechanisms (ie. mailing list)?
- Existing user support mechanisms are numerous mailing lists, IRC and Wiki. Companies are available for commercial support. There are also several national user groups. There is also a GRASS user map(server). The GRASS newsletter is currently adopted by OSGeo with the working title OSgeo Jounal.
- Are source and binary downloads for the package available?
- Yes. GRASS is a multi-platform GIS, all major operating systems are supported - see download page
- Has a Project Steering Committee been formed, and given control of the project?
- Yes. GRASS-PSC was formed in 12/2006
- Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
- Yes. See RFC1: Project Steering Committee Guidelines
- See also RFC2: Legal aspects of code contributions
- How many active developers are there? Are they from multiple organizations?
- Currently 38 (worldwide) developers have CVS write access. In 2006, around 16 developers of this group where active. FBK-irst (formerly ITC-irst) Trento, Italy is supporting the project since 2001, many universities, companies and individuals are contributing. For details, see the grass-commit mailing list archives. More than 10000 CVS commits have been done since 1st January 2000 (opening of CVS). See also CVS statistics which is part of the new GRASS Quality Assessment System and Ohloh statistics and CIA.
Foundation Membership
- Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
- Yes, see also Newsletter.
- Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
- Yes. The OSGeo logo is on the front page and search turns up 707 references to "OSGeo".
Code Copyright Review
- Has a Code Provenance Review document been prepared for the project?
- Yes, current status 97% see also GRASS Provenance Review.
- Have issues raised in the provenance review been adequately addressed?
- Yes.
Mentor Notes
Putting together notes for a documentatoin of the vetting process.
- Example of header addition: http://grass.itc.it/pipermail/grass-commit/2007-April/028266.html
- more of them here: http://grass.itc.it/pipermail/grass-commit.mbox/grass-commit.mbox
Earlier vetting has been done in: