[mapguide-internals] Motion: Give developers commit rights to work in a sandbox

[Jason Birch]

I suppose I don't have any real problem with this, so my vote is 0.

It would be nice to see an introduction from each of these people.  I believe that Hugues has already introduced himself, and I met Norm at FOSS4G 2007 and believe that they both work on CS-Map.  What areas are Jon interested in?  Can we expect to see community involvement from these folks?  Do they have individual CLAs on file?

For commit rights to the full tree, I would want to see due process (patches, public review, etc) followed.  Although I'm sure that they are all good developers, I don't like the idea of bypassing community involvement just because they work for Autodesk.

Jason

-----Original Message-----
From: Tom Fukushima
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
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