GeoMoose Incubation Checklist
Incubation checklist reviewed on email list, links provided below.
In response to this review several improvements were made by the community (see RFC section below).
Incubation Checklist
Open
1. Open and public manner
License:
- http://www.geomoose.org/info/license.html <-- MIT based License
Open Meetings:
- http://www.geomoose.org/wiki/index.php/Category:Meetings
- http://geomoose.org/wiki/index.php/2012_07_26_Meeting <-- incubation discussed here
- http://geomoose.org/wiki/index.php/09_14_2012_Roadmap_Planning_Meeting
- As a consequence of moving through the Incubation process, the GeoMoose PCS has instituted a regular PSC meeting schedule of roughly once a month. These meetings are open and and usually occur online with an occasional Face to face meeting. The meeting Notes are published to the GeoMoose wiki.
Public decision making process:
- RFC 1: Project Steering Committee Guidelines
- RFC 2: GeoMOOSE Project Mission (What is GeoMOOSE)
- RFC 3: GeoMOOSE Release Process
- Also as a consequence of moving through the Incubation process, the GeoMoose project has implemented a formal PSC that meets to discuss the project and make decisions. RFCs related to this action have been passed and additional related RFC's are in a pending state. This is a desirable development from the GeoMoose PCS group and they have been ver motivated to moving this along as a process.
2. Active and healthy community
Community of developers and users:
- http://osgeo-org.1560.n6.nabble.com/GeoMOOSE-users-f4585800.html
- http://osgeo-org.1560.n6.nabble.com/GeoMOOSE-f5002154.html
Participation from multiple developers and organisations:
- https://svn.osgeo.org/geomoose/geomoose2/trunk/AUTHORS.rst
- http://www.geomoose.org/wiki/index.php/GeoMoose_Incubation_Status
Copyright and License
1. license
2. documentation license
- no explicit documentation license discussion on using same license for everything
3. code, documentation, and data reviewed
4. List of copyright holders
- http://www.geomoose.org/info/license.html
- https://svn.osgeo.org/geomoose/geomoose2/trunk/AUTHORS.rst
5. Contribution agreement
- no code contribution agreement used (authors asked to place code into the public domain)
- http://www.geomoose.org/developer/contribute.html (references http://www.geomoose.org/developer/standards.html)
We have asked the project to make this more clear resulting in the following discusssion: http://lists.osgeo.org/pipermail/geomoose-psc/2013-February/000089.html
The proposed text is:
- 7. Any contributed code should contain a code source comment block in each file header indicating the author (that is you and your employer if you are working on company time), date of contribution and any conflicting licensing restrictions that are not already covered by the GeoMoose License. All unusual situations need to be discussed and/or documented on the project mail list and/or in the project TRAC system.
Processes
1. code under configuration management
2. issue tracker
3. management processes
Suitable open governance policy:
public communication channel for decision making::
- http://www.geomoose.org/wiki/index.php/Category:Meetings
- see email lists above
Documentation
1. user documentation:
2. developers documentation:
3. Release Procedure
OSGeo Committees and Community
Board
1. Project Officer: TBD
Marketing
1. Marketting details
- http://live.osgeo.org/en/overview/geomoose_overview.html
- http://live.osgeo.org/en/quickstart/geomoose_quickstart.html
2. Stable release available
Projects
Integration of:
- MapServer
- OpenLayers
- Dojo Toolkit
Release procedure includes version check (Apache, Dojo, MapServer) and a release candidate window for testing. Project policy is to use stable release of OpenLayers.
SAC
1. Link provided to geomoose website, http://geomoose.osgeo.org not used
2. SAC facilities:
- issue tracker: http://trac.osgeo.org/geomoose/
- mailing list: http://lists.osgeo.org/mailman/listinfo/geomoose-users
- subversion: https://svn.osgeo.org/geomoose/geomoose2/trunk
- downloads: http://www.geomoose.org/downloads/