[Incubator] Vote: GeoMoose Graduation

[Basques, Bob (CI-StPaul)]

Cameron,

>>  
>>  (I think the project is getting close, but not quite ready to
>>  complete
>>  graduation)
>>  
>>  1. I notice that there are 7 committers to the project, from 5
>>  organisations. I consider this to be a low, but acceptable number
>>  for a maturing project if the organisations are independent of
>>  each other.
>>  However, I'd like to know who sponsors all these developers and
>>  organisations? Is all the work ultimately being sponsored by the
>>  one agency?

[bob.b said . . .] each agency/company is sponsoring the individuals as listed here: http://www.geomoose.org/wiki/index.php/GeoMoose_Incubation_Status

No one agency or company has control of the project.  Some work is sponsored while others are project handbacks from specific projects offered up via the PSC for adding improvements to GeoMoose.  Improvements to the project have come from each of the committers home organizations in the form of donated time, as well as from formal improvement projects from each organization.

>>  
>>  2. It seems there are still some of loose ends which are still to
>>  be addressed, and I think that projects should not ask for
>>  graduation approval until they have been addressed. In
>>  particular, Jody mentioned:
>>  * No clear statement yet on the licence of documentation?
>>  Reference to an email discussion about license, doesn't
>>  constitute completion. I'm looking for a license statement on
>>  website or developer guidelines or similar.

[bob.b said . . .] As a result of the Documentation Licensing discussion, there is a License statement at the bottom of Each GeoMoose web site documentation page that reads: "(c) Copyright 2009-2011, Dan "Ducky" Little under License (http://www.geomoose.org/info/license.html). Created using Sphinx 1.1.3."

As far as contributed documentation, it would fall under the contribution guidelines as indicated in the website as well as the two references RFCs (when completed). 

>>  * While not a show stopper, I'd expect that code contributors
>>  should be able to contribute code under the project's MIT
>>  license, rather than being required to contribute under public
>>  domain.

[bob.b said . . .] 

No specific requirement has been stated in the interests of leaving the options open for contributors.  But something had to be listed, and an example of a contribution was provided (as described in the RFC), which addresses this.

>>  * I see there are 2 outstanding tickets 179, 180 addressing
>>  license issues. I'd like to see these addressed before we
>>  consider the project ready to complete graduation.
>>  
>>  Documentation:
>>  http://www.geomoose.org/developer/index.html
>>  * I notice that core documentation is being stored in a RFC, eg:
>>  "Project Steering Committee Guidelines".
>>  * I'd expect that once the RFC has been approved, that the
>>  documentation is moved into the main documentation structure from
>>  which it can continue to be maintained. (I see RFCs as decisions
>>  that have been made, and then fixed in time, rather than current
>>  working documentation).
>>  
>>  * Link to "How to Release" points nowhere.
>>  
>>  * Project Officer: No one named yet. I'd expect a volunteer to be
>>  identified.
>>  
>>  
>>  
>>  On 18/03/2013 3:55 PM, Jody Garnett wrote:
>>  > I'd like to make a motion to recommend GeoMoose for graduation
>>  from
>>  > the incubation process.
>>  >
>>  >
>>  
>>  On 13/03/2013 4:45 PM, Jody Garnett wrote:
>>  > Here is the checklist now:
>>  > - http://wiki.osgeo.org/wiki/GeoMoose_Incubation_Checklist
>>  >
>>  > Discussion is open if you have any questions, everything looks
>>  in
>>  > order from my point of view.
>>  >
>>  > A couple of notes from my time as mentor:
>>  > - the project decisions have gotten way easier to track, with a
>>  > separate email list and RFC process.
>>  > - the documentation license question was interesting (as we had
>>  the
>>  > same discussion for GeoServer) - the result in this case is the
>>  > documentation being covered under the same MIT license as the
>>  codebase
>>  > - code contribution agreement is handled via contributors
>>  donating
>>  > work into the public domain (there are two outstanding trace
>>  issues to
>>  > patch the developers guide)
>>  > - provenance review did not turn up anything special, sample
>>  data was
>>  > credited or replaced with toy data
>>  > - project officer is TBD (and can be nominated when we send the
>>  > project up to the board for approval)
>>  >
>>  
>>  
>>  --
>>  Cameron Shorter
>>  Geospatial Solutions Manager
>>  Tel: +61 (0)2 8570 5050
>>  Mob: +61 (0)419 142 254
>>  
>>  Think Globally, Fix Locally
>>  Geospatial Solutions enhanced with Open Standards and Open Source
>>  http://www.lisasoft.com
>>  
>>  --
>>  Cameron Shorter
>>  Geospatial Solutions Manager
>>  Tel: +61 (0)2 8570 5050
>>  Mob: +61 (0)419 142 254
>>  
>>  Think Globally, Fix Locally
>>  Geospatial Solutions enhanced with Open Standards and Open Source
>>  http://www.lisasoft.com
>>  
>>  _______________________________________________
>>  Incubator mailing list
>>  Incubator at lists.osgeo.org
>>  http://lists.osgeo.org/mailman/listinfo/incubator