[mapserver-dev] Sandbox Priv.s

Steve Lime Steve.Lime at dnr.state.mn.us
Fri Mar 20 11:21:34 EDT 2009

So, where are we at with this? If I've read the thread correctly:

  - folks are cool with the concept
  - OSGeo userid are sufficient credentials, they must ask on the -dev list for access
  - we tweak the committer guidelines with a "sandbox" clause and direct the requestor to that doc
  - committers grant access to the sandbox
  - committers have a responsibility to verify that anything that makes the leap to trunk meets appropriate guidelines

If this is right then the next steps are:

  - tweaking the committer guidelines (volunteer?)
  - getting the mapserver_sandbox group populated and things configured (volunteer?)


>>> On 3/13/2009 at 12:08 PM, in message <49BA9322.5090904 at umn.edu>, Perry
Nacionales <naci0002 at umn.edu> wrote:
> Howard Butler wrote:
>> On Mar 13, 2009, at 9:20 AM, Daniel Morissette wrote:
>>> Any member of the MapServer community can request mapserver_sandbox 
>>> group access to the trunk sandbox, provided that the person 
>>> requesting the sandbox explain on the -dev list what they plan to use 
>>> it for and that no objections are expressed by PSC members within 2 
>>> business days.
>> I disagree with the idea of 2 business days.  I think delaying someone 
>> sandbox access can have a dampening effect on enthusiasm, momentum, 
>> and willingness to share, which the sandbox access is hopefully there 
>> to help capture.  Granting sandbox access to *all* OSGeo userid's 
>> would be fine with me.
>> It seems you want a bit of a check on unfettered access though.  Maybe 
>> the rule for getting sandbox access could be that you convince a 
>> committer there's a good reason for you to develop one.  IIRC, the 
>> committers all list their "areas" in the docs somewhere (if we don't 
>> do this, we should).  A potential sandboxer should look at that list 
>> and shoot an email to someone who's doing related things (someone 
>> monkeying with renderers, or someone fixing the SDE bugs that I ignore 
>> :) ).  Ask them "hey, I want sandbox access to do X, Y, and Z".  
>> Committer agrees and grants them access by pointing and clicking a few 
>> things.
>>> Any regular mapserver committer moving code from a sandbox to trunk 
>>> assumes responsibility for ensuring it is appropriate from a 
>>> copyright point of view and that all other requirements of the 
>>> committer guidelines are met.
>> Absolutely.
> Agree with Howard.  If someone with OSGeo ID asks for permission to play 
> in a sandbox, to help fix/improve something then we shouldn't hinder 
> that too much.  Too many rules/restrictions will hinder participation 
> and too little could leave it open for abuse.  In the end though, any 
> code committed from sandbox to trunk needs to be verified clear of 
> copyright issues.
> I'm +1 if Howard's suggestions are implemented.
> -Perry
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org 
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev

More information about the mapserver-dev mailing list