GeoMoose Incubation Checklist

Incubation checklist reviewed on email list, links provided below.

• http://lists.osgeo.org/pipermail/geomoose-users/2012-May/004016.html

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

Public decision making process:

• RFC 1: Project Steering Committee Guidelines
• RFC 2: GeoMOOSE Project Mission (What is GeoMOOSE)
• RFC 3: GeoMOOSE Release 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

• http://www.geomoose.org/info/license.html
• https://svn.osgeo.org/geomoose/geomoose2/trunk/LICENSE

2. documentation license

• no explicit documentation license discussion on using same license for everything

3. code, documentation, and data reviewed

• http://wiki.osgeo.org/wiki/GeoMoose_Provenance_Review

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

• https://svn.osgeo.org/geomoose/geomoose2/trunk

2. issue tracker

• http://trac.osgeo.org/geomoose/

3. management processes

Suitable open governance policy:

• http://www.geomoose.org/rfc/rfc-1.html

public communication channel for decision making::

• http://www.geomoose.org/wiki/index.php/Category:Meetings
• see email lists above

Documentation

1. user documentation:

• Started
• GeoMoose Documentation

2. developers documentation:

• Developers Documentation
• http://www.geomoose.org/trunk/api/

3. Release Procedure

• How to Release

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

• http://live.osgeo.org/en/overview/geomoose_overview.html
• http://www.geomoose.org/info/download.html

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/