Difference between revisions of "GeoMoose Incubation Checklist"

From OSGeo
Jump to navigation Jump to search
Line 61: Line 61:
 
5. Contribution agreement
 
5. Contribution agreement
  
−
* no code contribution agreement used (authors retain copyright?)
+
* no code contribution agreement used (authors asked to place code into the public domain)
−
* http://www.geomoose.org/developer/contribute.html
+
* 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 ===
 
=== Processes ===

Revision as of 04:13, 18 February 2013

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:

Open Meetings:

Public decision making process:

2. Active and healthy community

Community of developers and users:

Participation from multiple developers and organisations:

Copyright and License

1. license

2. documentation license

3. code, documentation, and data reviewed

4. List of copyright holders

5. Contribution agreement

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::

Documentation

1. user documentation:

2. developers documentation:

3. Release Procedure

OSGeo Committees and Community

Board

1. Project Officer: TBD

Marketing

1. Marketting details

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:

Retrieved from "http://wiki.osgeo.org/w/index.php?title=GeoMoose_Incubation_Checklist&oldid=69003"