[mapguide-internals] Motion: Give developers commit rights to
work in a sandbox
tom.fukushima at autodesk.com
Thu Jun 25 12:30:26 EDT 2009
Thanks, please note that I am not asking that they be given full commit rights; please interpret the statement "I myself would be fine with giving them access to the full tree, but let's leave that for another discussion" as me giving my vote of confidence for them; nothing more.
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Andy Morsell
Sent: Thursday, June 25, 2009 10:23 AM
To: 'MapGuide Internals Mail List'
Subject: RE: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox
Agreed with Jason that they still need to go through the formal processes
and agreed with Paul that setting them up in a sandbox sooner than later is
a good thing. The more developers the better.
From: Tom Fukushima [mailto:tom.fukushima at autodesk.com]
Sent: Wednesday, June 24, 2009 3:58 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: Give developers commit rights to work
in a sandbox
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
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
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
More information about the mapguide-internals