<br><br><div class="gmail_quote">On Wed, Mar 18, 2009 at 11:33, 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>
<div class="im"><br>
Erik Uzureau wrote:<br>
> So from this mail and reading the two links... it sounds like the impact<br>
> for OL PSC<br>
> would be that we must make sure that:<br>
><br>
> 1) GeoExt has a OSGeo-friendly license (and doesn't change it)<br>
> 2) All contributors to GeoExt project have signed CLA<br>
> 3) GeoExt remains Geo-related.<br>
><br>
> Seems like (1) and (3) are essentially a one-time deal. (2), however,<br>
> would imply someone from OL PSC monitoring all GeoExt commits<br>
> and double-checking to see that CLAs are on file for the committer<br>
> or in the event that the committer is merely acting as a reviewer,<br>
> then for the originator of the patch.<br>
><br>
<br>
</div>Thanks for the response Erik. I think you've described the practical<br>
implications well.<br>
<div class="im"><br>
> None of this seems particularly difficult or time consuming.<br>
><br>
> My immediate question, though, is "can a member of the OL PSC<br>
> act in any of these roles if they are also a member of the GeoExt<br>
> PSC (or general community)?"<br>
<br>
</div>Sure. This is what I was imagining.<br>
<br></blockquote><div><br>Really? I'd maybe put that one to the good people at OSGEO before<br>declaring a victory. I don't wanna be a sourpuss, but to me this has<br>hints of some sort of wierd rotary-clubesque golden parachuting. <br>
<br>I mean, correct me if I'm wrong here, but even barring the above <br>conflict-of-interest issue, there just doesn't seem to be any sense<br>of *real* responsibility happenning at any stage of this game, does <br>
there? <br><br>Erik<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Governance in this case is largely about asking for evidence that<br>
guidelines are being met.<br>
<div class="im"><br>
><br>
> If the answer is "yes", and either Tim or Eric (who I know are both<br>
> involved in GeoExt) would like to take on the responsibilities, then<br>
> I don't see any reason for the OL PSC *not* to approve this.<br>
><br>
> If the answer is "no", then a suitable chaperone among the uninvolved<br>
> on the OL PSC will have to step up.<br>
><br>
> Are there any side effects to this that are not being listed here? I mean,<br>
> whether the answer to my above question is "yes" or "no", it doesn't seem<br>
> like OL PSC really has anything to *lose* either way.... maybe I'm<br>
> missing something?<br>
><br>
<br>
</div>I don't think there are implications that you are missing. If there is<br>
no more discussion, I'll ask for a vote tomorrow.<br>
<br>
Tim<br>
<div class="im"><br>
> Erik<br>
><br>
><br>
><br>
> On Fri, Mar 13, 2009 at 23:54, Tim Schaub <<a href="mailto:tschaub@opengeo.org">tschaub@opengeo.org</a><br>
</div><div><div></div><div class="h5">> <mailto:<a href="mailto:tschaub@opengeo.org">tschaub@opengeo.org</a>>> wrote:<br>
><br>
> Hey-<br>
><br>
> GeoExt is a project that aims to provide an Ext based toolkit for<br>
> developing applications with OpenLayers. The library will extend Ext<br>
> widgets and data management classes with mapping functionality from<br>
> OpenLayers.<br>
><br>
> The GeoExt project steering committee and existing users and developers<br>
> are interested in assigning copyright for the GeoExt code base to the<br>
> OSGeo foundation. For OSGeo to accept copyright, it would be ideal if<br>
> an existing OSGeo project could participate in the governance of the<br>
> GeoExt project.<br>
><br>
> Our hope (as the GeoExt PSC) is that the OpenLayers PSC would accept<br>
> this responsibility. Exactly what "participate in the governance" means<br>
> is a little hard to nail down. I've put together a proposal with a bit<br>
> more specific language:<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>
> I'd like to open discussion on this proposal and get a vote from the<br>
> OpenLayers PSC some time next week.<br>
><br>
> What this means for the OpenLayers PSC:<br>
><br>
> The OpenLayers PSC requires that the GeoExt PSC provides evidence that<br>
> GeoExt is following the criteria for becoming an OSGeo member project<br>
> (as far as I can tell, this is best described here<br>
> <a href="http://wiki.osgeo.org/wiki/OSGeo_Labs#Criteria" target="_blank">http://wiki.osgeo.org/wiki/OSGeo_Labs#Criteria</a>).<br>
><br>
> In practice, this will mean that the OpenLayers PSC will request that<br>
> the GeoExt PSC provide information on contributors and signed<br>
> contributor license agreements, and that the GeoExt PSC maintains the<br>
> "geospatial" nature of the project.<br>
><br>
> Questions and feedback welcome.<br>
> Tim<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>
</div></div>> <a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a> <mailto:<a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a>><br>
<div class="im">> <a href="http://openlayers.org/mailman/listinfo/dev" target="_blank">http://openlayers.org/mailman/listinfo/dev</a><br>
><br>
><br>
<br>
<br>
</div>--<br>
<div><div></div><div class="h5">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>
</div></div></blockquote></div><br>