Difference between revisions of "GeoMoose Incubation Checklist"

From OSGeo
Jump to navigation Jump to search
 
(16 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
* http://lists.osgeo.org/pipermail/geomoose-users/2012-May/004016.html
 
* http://lists.osgeo.org/pipermail/geomoose-users/2012-May/004016.html
  
In response to this review several improvements were made by the community:
+
In response to this review several improvements were made by the community (see RFC section below).
 
 
* [http://geomoose.org/trunk/rfc/rfc-1.html?highlight=rfc RFC 1: Project Steering Committee Guidelines]
 
* [http://geomoose.org/trunk/rfc/rfc-2.html?highlight=rfc RFC 2: GeoMOOSE Project Mission (What is GeoMOOSE)]
 
* [http://geomoose.org/trunk/rfc/rfc-3.html?highlight=rfc RFC 3: GeoMOOSE Release Process]
 
  
 
== Incubation Checklist ==
 
== Incubation Checklist ==
Line 13: Line 9:
 
=== Open ===
 
=== Open ===
  
License:
+
1. Open and public manner
  
* http://www.geomoose.org/info/license.html <-- MIT based
+
License:
 +
 
 +
* http://www.geomoose.org/info/license.html <-- MIT based License
  
 
Open Meetings:
 
Open Meetings:
Line 23: Line 21:
 
* http://geomoose.org/wiki/index.php/09_14_2012_Roadmap_Planning_Meeting
 
* http://geomoose.org/wiki/index.php/09_14_2012_Roadmap_Planning_Meeting
  
Email:
+
* 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:
 +
 
 +
* [http://geomoose.org/trunk/rfc/rfc-1.html?highlight=rfc RFC 1: Project Steering Committee Guidelines]
 +
* [http://geomoose.org/trunk/rfc/rfc-2.html?highlight=rfc RFC 2: GeoMOOSE Project Mission (What is GeoMOOSE)]
 +
* [http://geomoose.org/trunk/rfc/rfc-3.html?highlight=rfc 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-users-f4585800.html
 
* http://osgeo-org.1560.n6.nabble.com/GeoMOOSE-f5002154.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 ===
 
=== Copyright and License ===
Line 37: Line 52:
 
2. documentation license
 
2. documentation license
  
* no explicit documentation license
+
* no explicit documentation license [http://lists.osgeo.org/pipermail/geomoose-users/2012-May/004016.html discussion on using same license for everything]
  
 
3. code, documentation, and data reviewed
 
3. code, documentation, and data reviewed
Line 50: Line 65:
 
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
 +
 
 +
As a result the two GeoMoose pages referenced above will be edited as described here:
 +
 
 +
See GeoMoose Project Tickets [http://trac.osgeo.org/geomoose/ticket/179 #179] and [http://trac.osgeo.org/geomoose/ticket/180 #180]
  
 
=== Processes ===
 
=== Processes ===
  
* Covered by [http://www.geomoose.org/developer/index.html Developers Documentation]
+
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 ===
 
=== Documentation ===
Line 61: Line 99:
 
1. user documentation:
 
1. user documentation:
  
* [http://www.geomoose.org/getting_started.html|Getting Started]
+
* [http://www.geomoose.org/getting_started.html Getting Started]
* [http://www.geomoose.org/docs/index.html GeoMoose Documentation]
+
* [http://www.geomoose.org/docs/index.html GeoMoose Documentation]
  
 
2. developers documentation:
 
2. developers documentation:
  
* [http://www.geomoose.org/developer/index.html Developers Documentation]
+
* [http://www.geomoose.org/developer/index.html Developers Documentation]
 
* http://www.geomoose.org/trunk/api/  
 
* http://www.geomoose.org/trunk/api/  
  
Line 77: Line 115:
 
=== Board ===
 
=== Board ===
  
1. Project Officer: TBD
+
1. Project Officer:  
 +
 
 +
* Bob Basques as per: http://osgeo-org.1560.x6.nabble.com/OSGeo-project-officer-td5046209.html
  
 
=== Marketing ===
 
=== Marketing ===
Line 91: Line 131:
 
* http://www.geomoose.org/info/download.html
 
* http://www.geomoose.org/info/download.html
  
2. Projects
+
=== Projects ===
  
 
Integration of:
 
Integration of:

Latest revision as of 13:06, 12 April 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:

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

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

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

As a result the two GeoMoose pages referenced above will be edited as described here:

See GeoMoose Project Tickets #179 and #180

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:

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: