[mapguide-internals] Motion: Give developers commit rights to
workin a sandbox
rbray at robertbray.net
Fri Jun 26 12:58:10 EDT 2009
So I've read this whole thread with great interest. I believe we should get
a general sandbox approach setup as soon as possible. I liked Jason's idea
of project-oriented sandboxes rather than people-oriented ones, however I
also realize that the technology probably does not work quite that way.
Maybe we could require/request some documentation around the various
projects in the sandbox be available and kept current on the Wiki.
Anyway I am +1 on sandbox access for the named developers.
Also I believe the sandbox concept should be a priority for the PSC. We
should strive to be as open as open layers with respect to sandbox access.
This is a great way to get developers involved.
From: "Tom Fukushima" <tom.fukushima at autodesk.com>
Sent: Wednesday, June 24, 2009 4:57 PM
To: "MapGuide Internals Mail List" <mapguide-internals at lists.osgeo.org>
Subject: [mapguide-internals] Motion: Give developers commit rights to
workin a sandbox
> Hi PSC,
> I have three developers who will be working in a MGOS sandbox branch that
> I will be creating for them. I don't want to be submitting all of their
> patches for them and would prefer if they could commit directly to this
> branch. Unfortunately, I believe that we can only give submit rights to
> all or none of our subversion tree. So can we give subversion access to
> these developers on the condition that they work only in the sandbox?
> These developers are
> Hugues Wisniewski
> Jon Curtis
> Norm Olsen
> They are all senior Autodesk developers with many many years of
> development experience. I myself would be fine with giving them access to
> the full tree, but let's leave that for another discussion.
> I move to give Hugues, Jon and Norm, commit rights to a branch in the
> sandbox/adsk area.
> +1 Tom
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
More information about the mapguide-internals