+1<br><br><div class="gmail_quote">On Mon, Mar 30, 2009 at 12:00, Tim Schaub <span dir="ltr"><<a href="mailto:tschaub@opengeo.org">tschaub@opengeo.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hey-<br>
<br>
So, I'm picking up the GeoExt governance proposal again.<br>
<br>
Please see the links below for a history of the issue [1], [2].<br>
<br>
The executive summary follows: GeoExt is a new project that brings<br>
OpenLayers functionality to Ext JS widgets and data utilities. The<br>
GeoExt PSC would like to assign copyright for the code to OSGeo. OSGeo<br>
suggested that out of courtesy, the GeoExt PSC make a proposal to an<br>
OSGeo member project asking the member project to accept a role in the<br>
governance of the new project.<br>
<br>
The responsibilities of this role (for the OpenLayers PSC and for the<br>
GeoExt PSC) are described here:<br>
<br>
<a href="http://www.geoext.org/trac/geoext/wiki/governance" target="_blank">http://www.geoext.org/trac/geoext/wiki/governance</a><br>
<br>
What does this mean for the OpenLayers PSC?<br>
-------------------------------------------<br>
The OpenLayers PSC will ask the GeoExt PSC to provide evidence that code<br>
contributions are free from encumbrances. Further, the OpenLayers PSC<br>
will provide guidance to the GeoExt PSC if it appears that GeoExt is in<br>
violation of any other criteria of an OSGeo member project.<br>
<br>
What does this means for the GeoExt PSC?<br>
----------------------------------------<br>
The GeoExt PSC will gather signed license agreements from code<br>
contributors. It will provide a report (periodically or generated on<br>
demand) all contributors and status of their CLA. In addition, the<br>
GeoExt PSC will continue to govern the project in a way that conforms<br>
with the guidelines for OSGeo member projects.<br>
<br>
What does this *not* mean?<br>
--------------------------<br>
The OpenLayers PSC will *not* be responsible for examining the commit<br>
logs, tracking down code contributors, asking individuals to sign the<br>
CLA, or any duties that have to do with technical aspects of managing<br>
the GeoExt project. The OpenLayers PSC will also *not* vote on issues<br>
before the GeoExt PSC.<br>
<br>
Why is this happening?<br>
----------------------<br>
See the links below for a little history. Basically, anyone can assign<br>
copyright to OSGeo. Frank Warmerdam suggested that the OSGeo would<br>
probably be happier about having copyright assigned if a current member<br>
project accepted some role in the governance of the new project (the one<br>
assigning copyright). OSGeo doesn't have any real responsibility for<br>
the non-member projects that assign it copyright. By extension,<br>
OpenLayers does not assume any real liability under this agreement (its<br>
status as a member project is not jeopardized if the terms of the<br>
agreement are not met). This is largely a courtesy to the OSGeo.<br>
<br>
<br>
So, as a member of the OpenLayers PSC, I'd like to propose that we<br>
accept this role in the governance of the GeoExt PSC. I'm happy to<br>
answer any more specific questions about what this means.<br>
<br>
Thanks for the vote and/or questions.<br>
<br>
Tim<br>
<br>
[1] <a href="http://n2.nabble.com/copyright-question-td2088465.html" target="_blank">http://n2.nabble.com/copyright-question-td2088465.html</a><br>
[2] <a href="http://n2.nabble.com/proposal-for-GeoExt-governance-td2477185.html" target="_blank">http://n2.nabble.com/proposal-for-GeoExt-governance-td2477185.html</a><br>
<font color="#888888"><br>
<br>
--<br>
Tim Schaub<br>
OpenGeo - <a href="http://opengeo.org" target="_blank">http://opengeo.org</a><br>
Expert service straight from the developers.<br>
_______________________________________________<br>
Dev mailing list<br>
<a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a><br>
<a href="http://openlayers.org/mailman/listinfo/dev" target="_blank">http://openlayers.org/mailman/listinfo/dev</a><br>
</font></blockquote></div><br>