Difference between revisions of "GeoMoose Incubation Status"
(→Infrastructure Transition: add existing infrastructure links)
(→Document Status: increment version after infrastructure link updates)
|Line 3:||Line 3:|
'''IncCom Document Number''': X
'''IncCom Document Number''': X
Revision as of 14:48, 28 November 2011
IncCom Document Number: X
The project representative and mentor will use this template to inform the IncCom of the project status on a periodic basis. The state of the project, as reported using this template, will be the initial indication that a project is reaching graduation.
Terms and Definitions
- Has the project been approved for incubation by the OSGeo board?
- Not that I know of. Jody would you like to add this to the next Board agenda or should I?
- Has an Incubation Mentor been assigned to the project?
- Jody is our mentor
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?
- No. We haven't thought of or discussed this. We will probably use that to redirect to geomoose.org our current home (or vice-versa depending on discussions of which infrastructure we prefer.)
- Is the OSGeo bug tracker being used for the project?
- Pending ticket until then geomoose(dot)org(slash)trac
- Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
- Yes, check it out, GeoMoose list completed from ticket
- Is the OSGeo SVN being used for the project?
- Pending ticket until then, svn co https://geomoose.svn.sourceforge.net/svnroot/geomoose geomoose
- Are binary and source downloads available from http://download.osgeo.org ?
- No, we will probably put a link to GeoMoose download page
- Is there a functioning user support mechanisms (ie. mailing list)?
- The OSGeo hosted mailman list is the primary mechanism. It is working well. For some rough numbers, from March-November there were 828 emails so about 20ish emails a week. Most get answered promptly ending in a successful resolution. A very small number do not get answered at all.
- Are source and binary downloads for the package available?
- Yes (to the extent applicable).
- Has a Project Steering Committee been formed, and given control of the project?
- Yes. Dan, Jim, Bob, Brian*, Eli, and Brent are the PSC and have control. *Brian is the chair.
- Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
- Yes. We have an established decision process RFC1
- No, we need to improve and be more explicit in our contributor guidelines.
- How many active developers are there? Are they from multiple organizations?
- ~5. Various organizations (Houston Engineering, SharedGeo, GeoAnalytic, Freelance, Local Government Agencies, etc)
- Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
- Upon graduation from incubation GeoMoose will proudly display its affiliation with OSGeo reflected throughout the project (website, mailing list, logos, etc)
- Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
- Upon graduation the GeoMoose website will link to the OSGeo website from several places, display the OSGeo logo, and state that GeoMoose is a project of the Open Source Geospatial Foundation (OSGeo). We will also submit a SAC ticket for OSGeo website updates (listing in projects). Down the road the PSC will probably discuss options to allow GeoMoose sponsorship through OSGeo project sponsorship
Code Copyright Review
- Has a Code Provenance Review document been prepared for the project?
- yes/no - point to review document.
- Have issues raised in the provenance review been adequately addressed?
- indicate outstanding issues.
- Are Commiter Responsibilities Guidelines covering legal issues in place?
- yes/no - point to the guidelines and indicate if it is adopted by PSC, and accepted by all commiters.