[mapguide-internals] MapGuide RFC 57 - Refining the linuxbuildprocess and generating install packages

[Jason Birch]

I feel that we could give sandbox committers full access and expect them
to "do the right thing".  My personal take is that if we do this we
should require that our sandbox committers sign a contribution agreement
though.

Other projects like gdal and openlayers create the sandbox at the same
level as trunk, branches, etc, and as far as I know don't set up Trac
components for the sandbox.  We could either overload the "Build"
component, or create a new component for CMake I guess.

Jason

-----Original Message-----
From: Zac Spitzer
Sent: Wednesday, November 26, 2008 13:10
Subject: Re: [mapguide-internals] MapGuide RFC 57 - Refining the
linuxbuildprocess and generating install packages

With regards to undertaking this work in a sandbox, how is that going
to work with commit rights?

Will SVN ACL's be used to provide commit access to the people working
on the sandbox
without giving the commit access to the whole tree?

As it was mentioned that 2.1 was going to appear as a beta (back in
oct?) is the trunk in a
reasonable state for branching off into a sandbox?

What's the best approach with trac? a special milestone?