[fdo-internals] RE: Sandbox Commit Rights for Alex Sun

[Greg Boone]

Is there a mechanism for providing developer access to a sandbox and not the trunk?

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Wednesday, August 12, 2009 12:32 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RE: Sandbox Commit Rights for Alex Sun

Now that we have a way of controlling access to the sandbox, I'd like to see us adopt a policy similar to MapGuide.

Basically:
  - any PSC member can approve the creation of a new sandbox, just has to send email to list and update sandbox wiki
  - anyone can be given access to the sandbox
  - changes in the sandbox need to go through standard code review and/or RFC process before being merged into trunk

MapGuide sandbox wiki:
  http://trac.osgeo.org/mapguide/wiki/Sandboxes

 Jason

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Wednesday, August 12, 2009 9:01 AM
To: FDO Internals Mail List
Subject: [fdo-internals] Sandbox Commit Rights for Alex Sun

Hi All,

Alex Sun, a developer with Autodesk in Shanghai, has asked that he be provided commit rights to the FDO SVN for sandbox work on RFC 37: Detailed Exception.

http://trac.osgeo.org/fdo/wiki/FDORfc37

I plan to set up the following sandbox for this work

http://trac.osgeo.org/fdo/browser/sandbox/DetailedExceptions

If there is any objections to granting his commit rights for the sandbox, please let me know. Once his track record has been established, he can request full access to the trunk and all SVN folders.

Regards,
Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20090812/948669d7/attachment-0001.html