OSGeo.org › OSGeo Software and Data Projects › MapGuide Open Source › MapGuide Internals

Motion: Give developers commit rights to work in a sandbox

28 messages

1 2

Tom Fukushima

Motion: Give developers commit rights to work in a sandbox

Reply Threaded

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

Thanks
Tom
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Jason Birch

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

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

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Tom Fukushima

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

They don't have CLAs on file but I have already told them about it and they will be in place before I create the sandbox.

I don't have answers for the other two questions.

Cheers
Tom

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Wednesday, June 24, 2009 5:15 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox

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

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Paul Spencer-2

Re: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

In reply to this post by Tom Fukushima

I'm happy to see more developers involved in the MapGuide source, I
think it is reasonable to start with sandbox access (even if it is
only virtual at this time) for anyone who expresses interest in
becoming involved. +1 Paul

PS I believe that Chris Schmidt was working on making it possible to
set up more fine grained commit rights, perhaps a quick question to
SAC might resolve this.

On 24-Jun-09, at 6:57 PM, Tom Fukushima wrote:

> 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
>
> Thanks
> Tom
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals

__________________________________________

Paul Spencer
Chief Technology Officer
DM Solutions Group Inc
http://research.dmsolutions.ca/

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Frank Warmerdam

Re: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

Folks,

Per the "Authz Rules" section of http://wiki.osgeo.org/wiki/Subversion
we are now capable of managing a distinct commit group for subareas of
a repository - typically for /sandbox type areas with a more permissive
participation process.

Just file a SAC ticket with the particulars of what you need when you are
ready and Howard or I should be able to implement it.

Best regards,

Paul Spencer wrote:

> PS I believe that Chris Schmidt was working on making it possible to set
> up more fine grained commit rights, perhaps a quick question to SAC
> might resolve this.
>
> On 24-Jun-09, at 6:57 PM, Tom Fukushima wrote:
>
>> 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?

--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, [hidden email]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Andy Morsell

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

In reply to this post by Tom Fukushima

+1 Andy

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.

Andy

-----Original Message-----
From: Tom Fukushima [mailto:[hidden email]]
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

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

Thanks
Tom

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Tom Fukushima

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

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.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] 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

+1 Andy

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.

Andy

-----Original Message-----
From: Tom Fukushima [mailto:[hidden email]]
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

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

Thanks
Tom

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Kenneth Skovhede, GEOGRAF A/S

Re: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

In reply to this post by Tom Fukushima

If I understand Frank correctly, it is "easy" to create a sandbox in svn.
With this sandbox anyone (in theory) should be allowed a sandbox area,
for free play and testing.

If this is so, I don't see the need for this vote.
I think UV would like a sandbox as well.

The open source handbook:
http://producingoss.com/

clearly states that the founding company should not try to bypass the
rules, as that will make the project appear "closed" in the sense that
only "insiders" get commit access, which is the opposite of the goal
with OS software.

I'm not suggesting that there is foul play here, and I am confident that
the proposed developers are highly skilled, but seen from the outside,
this looks a bit like favorizing the Autodesk people.

I would suggest that we instead clear up any confusion on the sandbox
issues,
and make sandboxes avalible for those who apply for one.
If there are too many requests for sandboxes, we will have to reconsider
what criteria there should be for applicants.

Regards, Kenneth Skovhede, GEOGRAF A/S

Tom Fukushima skrev:

> 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
>
> Thanks
> Tom
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Paul Spencer-2

Re: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

Sandbox access for OpenLayers has been a free-for-the-asking thing and
it has worked extremely well in terms of getting folks involved in the
project. Only a small percentage of folks getting sandboxes have
become core committers, but it has allowed non-committers to work with
committers on things like testing and documentation where the final
diff from a sandbox branch is then pulled as a patch, reviewed by the
committers and finally committed.

Assuming that we can set up a sandbox area in svn, I agree with
Kenneth that anyone who wants access should get access. There do need
to be some guidelines for the sandbox - folks should create sub
folders with their user name and make copies within that directory
unless they are collaborating with several users for instance.

Paul

On 25-Jun-09, at 1:48 PM, Kenneth Skovhede, GEOGRAF A/S wrote:

> If I understand Frank correctly, it is "easy" to create a sandbox in
> svn.
> With this sandbox anyone (in theory) should be allowed a sandbox area,
> for free play and testing.
>
> If this is so, I don't see the need for this vote.
> I think UV would like a sandbox as well.
>
> The open source handbook:
> http://producingoss.com/
>
> clearly states that the founding company should not try to bypass the
> rules, as that will make the project appear "closed" in the sense that
> only "insiders" get commit access, which is the opposite of the goal
> with OS software.
>
> I'm not suggesting that there is foul play here, and I am confident
> that
> the proposed developers are highly skilled, but seen from the outside,
> this looks a bit like favorizing the Autodesk people.
>
> I would suggest that we instead clear up any confusion on the
> sandbox issues,
> and make sandboxes avalible for those who apply for one.
> If there are too many requests for sandboxes, we will have to
> reconsider
> what criteria there should be for applicants.
>
> Regards, Kenneth Skovhede, GEOGRAF A/S
>
>
>
> Tom Fukushima skrev:
>> 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
>>
>> Thanks
>> Tom
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Tom Fukushima

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

In reply to this post by Kenneth Skovhede, GEOGRAF A/S

Kenneth,

Wow, I'm sorry if I'm being dense, but I really don't know where this favoritism feeling is coming from.

Let me back up a bit... MGOS doesn't have a process for the sandbox, and so I thought I was doing the right thing by making sure to ask the PSC for the rights to the sandbox for some developers. So yes, we need to vote or do something. What did I do wrong to get so much concern about this request? Please tell me, I would like to know? Should I just tell the developers that they should forget this approach?

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Kenneth Skovhede, GEOGRAF A/S
Sent: Thursday, June 25, 2009 11:49 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox

If I understand Frank correctly, it is "easy" to create a sandbox in svn.
With this sandbox anyone (in theory) should be allowed a sandbox area,
for free play and testing.

If this is so, I don't see the need for this vote.
I think UV would like a sandbox as well.

The open source handbook:
http://producingoss.com/

clearly states that the founding company should not try to bypass the
rules, as that will make the project appear "closed" in the sense that
only "insiders" get commit access, which is the opposite of the goal
with OS software.

I'm not suggesting that there is foul play here, and I am confident that
the proposed developers are highly skilled, but seen from the outside,
this looks a bit like favorizing the Autodesk people.

I would suggest that we instead clear up any confusion on the sandbox
issues,
and make sandboxes avalible for those who apply for one.
If there are too many requests for sandboxes, we will have to reconsider
what criteria there should be for applicants.

Regards, Kenneth Skovhede, GEOGRAF A/S

Tom Fukushima skrev:

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Haris Kurtagic

RE: Motion: Give developers commit rights towork in a sandbox

Reply Threaded

In reply to this post by Tom Fukushima

+1
I agree with Paul and Andy, more sandboxes and developers the better

Haris

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Tom
Fukushima
Sent: Thursday, June 25, 2009 6:30 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Motion: Give developers commit rights
towork in a sandbox

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.

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] 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

+1 Andy

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.

Andy

-----Original Message-----
From: Tom Fukushima [mailto:[hidden email]]
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

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

Thanks
Tom

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Jason Birch

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

In reply to this post by Tom Fukushima

I'm not Kenneth, but... :)

You've cleared this up since, but your initial email where you talked about giving full commit rights felt a bit out of place given the difficulty getting commit rights for UV (which BTW I still feel was appropriate given that he was also essentially unknown to the community). It may not have been your intention, but this did sound to me like "They work for Autodesk, and I trust them, so they should have access". I think the general sandbox approach is fine, just that the initial message may have been misinterpreted.

I also agree with Paul that sandboxes should be available to anyone who needs one, but I wonder if there should be a specific reason (such as, overhauling the projection library, or integrating a REST extension, or writing a Flex-based client, or maintaining a custom branch for some product). This has the benefit of making sandbox creation more about the function than about the person. This is more about controlling the size of the repository than about trust / usefulness. Once created, we could have an open-door policy about commit rights, but with the understanding that any code integrated into trunk would first require both a CLA and community review. I guess I'm not really opposed to person-based sandboxes, but I can't think of a use case that project-based sandboxes wouldn't cover.

Jason

-----Original Message-----
From: Tom Fukushima
Sent: Thursday, June 25, 2009 1:36 PM
Subject: RE: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox

Kenneth,

Wow, I'm sorry if I'm being dense, but I really don't know where this favoritism feeling is coming from.

Let me back up a bit... MGOS doesn't have a process for the sandbox, and so I thought I was doing the right thing by making sure to ask the PSC for the rights to the sandbox for some developers. So yes, we need to vote or do something. What did I do wrong to get so much concern about this request? Please tell me, I would like to know? Should I just tell the developers that they should forget this approach?

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Tom Fukushima

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

Jason,

In case you are saying that I'm thinking that giving Hugues, Jon and Norm full access "felt a bit out of place given the difficulty getting commit rights for UV". This is totally 100% not what I'm thinking. As I think we all know now, I'm only saying that they need access to the sandbox --- that's it.

There are more developers here (for example, Christine) who would like commit access to the MGOS vault, but we are putting them through the standard process of providing patches first. There is no favoritism. Let's stop any thoughts that there might be immediately.

There is no need to reply to this email, it is for clarification purposes only.

PSC,

One other point of clarification. According to the committers list, Jon is already a committer in the MapGuide vault, he worked on the original 1.0 versions of MapGuide. Sorry, that I added him to the original list. If you see him making submissions to other branches, that's because he can (I'm assuming that we are going with the PFOSS book rule of not removing committers even if they have been dormant for a while).

Tom

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Thursday, June 25, 2009 3:46 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox

I'm not Kenneth, but... :)

You've cleared this up since, but your initial email where you talked about giving full commit rights felt a bit out of place given the difficulty getting commit rights for UV (which BTW I still feel was appropriate given that he was also essentially unknown to the community). It may not have been your intention, but this did sound to me like "They work for Autodesk, and I trust them, so they should have access". I think the general sandbox approach is fine, just that the initial message may have been misinterpreted.

I also agree with Paul that sandboxes should be available to anyone who needs one, but I wonder if there should be a specific reason (such as, overhauling the projection library, or integrating a REST extension, or writing a Flex-based client, or maintaining a custom branch for some product). This has the benefit of making sandbox creation more about the function than about the person. This is more about controlling the size of the repository than about trust / usefulness. Once created, we could have an open-door policy about commit rights, but with the understanding that any code integrated into trunk would first require both a CLA and community review. I guess I'm not really opposed to person-based sandboxes, but I can't think of a use case that project-based sandboxes wouldn't cover.

Jason

-----Original Message-----
From: Tom Fukushima
Sent: Thursday, June 25, 2009 1:36 PM
Subject: RE: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox

Kenneth,

Wow, I'm sorry if I'm being dense, but I really don't know where this favoritism feeling is coming from.

Let me back up a bit... MGOS doesn't have a process for the sandbox, and so I thought I was doing the right thing by making sure to ask the PSC for the rights to the sandbox for some developers. So yes, we need to vote or do something. What did I do wrong to get so much concern about this request? Please tell me, I would like to know? Should I just tell the developers that they should forget this approach?

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Kenneth Skovhede, GEOGRAF A/S

Re: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

In reply to this post by Tom Fukushima

Tom,

I don't think you are being dense. We just see this from different angles.

Your request is to allow some qualified developers acceptable working
conditions.
I totally support that. The more the merrier.

But, your request looks very similar to a request made by UV a little while
back. His request was denied, because there was no means of getting a
sandbox.

If I have overlooked a difference in the two requests, I will be happy to
be informed of the differences.

There may be valid reasons for allowing one request, and not another, but in
your mail, it initially appeared to me as if the difference was your
confidence
in the developers. I don't see that as a valid reason (although I trust
your
judgement).

After re-reading the mail, I can see that your confidence was mentioned
to assure us
that they would not start commiting to areas they were not supposed to.

As for favorism, I don't see anyone else having the privileges that you
are requesting
for the proposed contributors. And I can't see how anyone else could
apply for something
like it. As always, I'm gladly corrected.

There may also be a misunderstanding about what an "SVN Sandbox" is
supposed to be or do.
I have my idea of a sandbox from OpenLayers:
http://faq.openlayers.org/svn/how-can-i-get-commit-access-to-the-svn-repository/

In the OL sense, a sandbox is a free-for-all playground, where anyone
can get access.
I am under the impressions that this is possible in MapGuide too, so
there is no
need to vote on this issue, we should just set it up, free for all.

If I misunderstood that part, I would also be happy to be informed.

Having a sandbox would potentially open up for many more developers, and
make
stuff like reviews of specific cases better.

I vote -0.
I want the developers on board, but I
don't like the method.

Regards, Kenneth Skovhede, GEOGRAF A/S

Tom Fukushima skrev:

> Kenneth,
>
> Wow, I'm sorry if I'm being dense, but I really don't know where this favoritism feeling is coming from.
>
> Let me back up a bit... MGOS doesn't have a process for the sandbox, and so I thought I was doing the right thing by making sure to ask the PSC for the rights to the sandbox for some developers. So yes, we need to vote or do something. What did I do wrong to get so much concern about this request? Please tell me, I would like to know? Should I just tell the developers that they should forget this approach?
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Kenneth Skovhede, GEOGRAF A/S
> Sent: Thursday, June 25, 2009 11:49 AM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox
>
> If I understand Frank correctly, it is "easy" to create a sandbox in svn.
> With this sandbox anyone (in theory) should be allowed a sandbox area,
> for free play and testing.
>
> If this is so, I don't see the need for this vote.
> I think UV would like a sandbox as well.
>
> The open source handbook:
> http://producingoss.com/
>
> clearly states that the founding company should not try to bypass the
> rules, as that will make the project appear "closed" in the sense that
> only "insiders" get commit access, which is the opposite of the goal
> with OS software.
>
> I'm not suggesting that there is foul play here, and I am confident that
> the proposed developers are highly skilled, but seen from the outside,
> this looks a bit like favorizing the Autodesk people.
>
> I would suggest that we instead clear up any confusion on the sandbox
> issues,
> and make sandboxes avalible for those who apply for one.
> If there are too many requests for sandboxes, we will have to reconsider
> what criteria there should be for applicants.
>
> Regards, Kenneth Skovhede, GEOGRAF A/S
>
>
>
> Tom Fukushima skrev:
>
>> 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
>>
>> Thanks
>> Tom
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
>>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

zspitzer

Re: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

I concur with Kenneth.

being more liberal with sandboxes, makes the currently opaque process of
getting commit access a lot more visible.

Code review by committed fixes with comments, much easier?

Subversion sandboxes are so cheap resource wise, creating one
is just a pointer in the db.

more sandboxes!

z

On Fri, Jun 26, 2009 at 4:46 PM, Kenneth Skovhede, GEOGRAF
A/S<[hidden email]> wrote:

> Tom,
>
> I don't think you are being dense. We just see this from different angles.
>
> Your request is to allow some qualified developers acceptable working
> conditions.
> I totally support that. The more the merrier.
>
> But, your request looks very similar to a request made by UV a little while
> back. His request was denied, because there was no means of getting a
> sandbox.
>
> If I have overlooked a difference in the two requests, I will be happy to
> be informed of the differences.
>
> There may be valid reasons for allowing one request, and not another, but in
> your mail, it initially appeared to me as if the difference was your
> confidence
> in the developers. I don't see that as a valid reason (although I trust your
> judgement).
>
> After re-reading the mail, I can see that your confidence was mentioned to
> assure us
> that they would not start commiting to areas they were not supposed to.
>
> As for favorism, I don't see anyone else having the privileges that you are
> requesting
> for the proposed contributors. And I can't see how anyone else could apply
> for something
> like it. As always, I'm gladly corrected.
>
> There may also be a misunderstanding about what an "SVN Sandbox" is supposed
> to be or do.
> I have my idea of a sandbox from OpenLayers:
> http://faq.openlayers.org/svn/how-can-i-get-commit-access-to-the-svn-repository/
>
> In the OL sense, a sandbox is a free-for-all playground, where anyone can
> get access.
> I am under the impressions that this is possible in MapGuide too, so there
> is no
> need to vote on this issue, we should just set it up, free for all.
>
> If I misunderstood that part, I would also be happy to be informed.
>
> Having a sandbox would potentially open up for many more developers, and
> make
> stuff like reviews of specific cases better.
>
> I vote -0.
> I want the developers on board, but I
> don't like the method.
>
> Regards, Kenneth Skovhede, GEOGRAF A/S
>
>
>
> Tom Fukushima skrev:
>>
>> Kenneth,
>>
>> Wow, I'm sorry if I'm being dense, but I really don't know where this
>> favoritism feeling is coming from.
>>
>> Let me back up a bit... MGOS doesn't have a process for the sandbox, and
>> so I thought I was doing the right thing by making sure to ask the PSC for
>> the rights to the sandbox for some developers. So yes, we need to vote or
>> do something. What did I do wrong to get so much concern about this request?
>> Please tell me, I would like to know? Should I just tell the developers that
>> they should forget this approach?
>>
>>
>> -----Original Message-----
>> From: [hidden email]
>> [mailto:[hidden email]] On Behalf Of Kenneth
>> Skovhede, GEOGRAF A/S
>> Sent: Thursday, June 25, 2009 11:49 AM
>> To: MapGuide Internals Mail List
>> Subject: Re: [mapguide-internals] Motion: Give developers commit rights to
>> work in a sandbox
>>
>> If I understand Frank correctly, it is "easy" to create a sandbox in svn.
>> With this sandbox anyone (in theory) should be allowed a sandbox area,
>> for free play and testing.
>>
>> If this is so, I don't see the need for this vote.
>> I think UV would like a sandbox as well.
>>
>> The open source handbook:
>> http://producingoss.com/
>>
>> clearly states that the founding company should not try to bypass the
>> rules, as that will make the project appear "closed" in the sense that
>> only "insiders" get commit access, which is the opposite of the goal
>> with OS software.
>>
>> I'm not suggesting that there is foul play here, and I am confident that
>> the proposed developers are highly skilled, but seen from the outside,
>> this looks a bit like favorizing the Autodesk people.
>>
>> I would suggest that we instead clear up any confusion on the sandbox
>> issues,
>> and make sandboxes avalible for those who apply for one.
>> If there are too many requests for sandboxes, we will have to reconsider
>> what criteria there should be for applicants.
>>
>> Regards, Kenneth Skovhede, GEOGRAF A/S
>>
>>
>>
>> Tom Fukushima skrev:
>>
>>>
>>> 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
>>>
>>> Thanks
>>> Tom
>>> _______________________________________________
>>> mapguide-internals mailing list
>>> [hidden email]
>>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>>
>>
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>

Bruce Dechant

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

In reply to this post by Tom Fukushima

+1 for sandbox access

Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Tom Fukushima
Sent: Wednesday, June 24, 2009 4:58 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: Give developers commit rights to work in 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

Thanks
Tom
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

Trevor Wekel-3

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

In reply to this post by zspitzer

And next thing we need to look at is an online code review tool to make the whole review process easier to manage. Using patch files is ok but they are a hassle for any significant code change. I did a quick internet search and there are a number of open source code review tools available. Some are more stable and active than others:

http://www.review-board.org/

http://codestriker.sourceforge.net/

http://groogle.sourceforge.net/

http://code.google.com/p/jupiter-eclipse-plugin/

Does any on the list have experience with any of these tools? Anyone know of any good alternatives?

I, and all the other Autodesk developers, have experience with SmartBear's Code Collaborator. I originally discounted it from the list but I found a little note on their Pricing page saying that it is "FREE for Open Source Projects!". Since OSGeo is all open source, it might make sense to see if SAC would be interested in it.

http://smartbear.com/codecollab.php

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Zac Spitzer
Sent: Friday, June 26, 2009 2:29 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox

I concur with Kenneth.

being more liberal with sandboxes, makes the currently opaque process of
getting commit access a lot more visible.

Code review by committed fixes with comments, much easier?

Subversion sandboxes are so cheap resource wise, creating one
is just a pointer in the db.

more sandboxes!

z

On Fri, Jun 26, 2009 at 4:46 PM, Kenneth Skovhede, GEOGRAF
A/S<[hidden email]> wrote:

--
Zac Spitzer -
http://zacster.blogspot.com
+61 405 847 168
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

zspitzer

Re: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

http://www.atlassian.com/studio/ ? it's free for opensource projects

On Fri, Jun 26, 2009 at 7:35 PM, Trevor Wekel<[hidden email]> wrote:

> And next thing we need to look at is an online code review tool to make the whole review process easier to manage. Using patch files is ok but they are a hassle for any significant code change. I did a quick internet search and there are a number of open source code review tools available. Some are more stable and active than others:
>
> http://www.review-board.org/
>
> http://codestriker.sourceforge.net/
>
> http://groogle.sourceforge.net/
>
> http://code.google.com/p/jupiter-eclipse-plugin/
>
> Does any on the list have experience with any of these tools? Anyone know of any good alternatives?
>
> I, and all the other Autodesk developers, have experience with SmartBear's Code Collaborator. I originally discounted it from the list but I found a little note on their Pricing page saying that it is "FREE for Open Source Projects!". Since OSGeo is all open source, it might make sense to see if SAC would be interested in it.
>
> http://smartbear.com/codecollab.php
>
>
>
> Thanks,
> Trevor
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Zac Spitzer
> Sent: Friday, June 26, 2009 2:29 AM
> To: MapGuide Internals Mail List
> Subject: Re: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox
>
> I concur with Kenneth.
>
> being more liberal with sandboxes, makes the currently opaque process of
> getting commit access a lot more visible.
>
> Code review by committed fixes with comments, much easier?
>
> Subversion sandboxes are so cheap resource wise, creating one
> is just a pointer in the db.
>
> more sandboxes!
>
> z
>
>
> On Fri, Jun 26, 2009 at 4:46 PM, Kenneth Skovhede, GEOGRAF
> A/S<[hidden email]> wrote:
>> Tom,
>>
>> I don't think you are being dense. We just see this from different angles.
>>
>> Your request is to allow some qualified developers acceptable working
>> conditions.
>> I totally support that. The more the merrier.
>>
>> But, your request looks very similar to a request made by UV a little while
>> back. His request was denied, because there was no means of getting a
>> sandbox.
>>
>> If I have overlooked a difference in the two requests, I will be happy to
>> be informed of the differences.
>>
>> There may be valid reasons for allowing one request, and not another, but in
>> your mail, it initially appeared to me as if the difference was your
>> confidence
>> in the developers. I don't see that as a valid reason (although I trust your
>> judgement).
>>
>> After re-reading the mail, I can see that your confidence was mentioned to
>> assure us
>> that they would not start commiting to areas they were not supposed to.
>>
>> As for favorism, I don't see anyone else having the privileges that you are
>> requesting
>> for the proposed contributors. And I can't see how anyone else could apply
>> for something
>> like it. As always, I'm gladly corrected.
>>
>> There may also be a misunderstanding about what an "SVN Sandbox" is supposed
>> to be or do.
>> I have my idea of a sandbox from OpenLayers:
>> http://faq.openlayers.org/svn/how-can-i-get-commit-access-to-the-svn-repository/
>>
>> In the OL sense, a sandbox is a free-for-all playground, where anyone can
>> get access.
>> I am under the impressions that this is possible in MapGuide too, so there
>> is no
>> need to vote on this issue, we should just set it up, free for all.
>>
>> If I misunderstood that part, I would also be happy to be informed.
>>
>> Having a sandbox would potentially open up for many more developers, and
>> make
>> stuff like reviews of specific cases better.
>>
>> I vote -0.
>> I want the developers on board, but I
>> don't like the method.
>>
>> Regards, Kenneth Skovhede, GEOGRAF A/S
>>
>>
>>
>> Tom Fukushima skrev:
>>>
>>> Kenneth,
>>>
>>> Wow, I'm sorry if I'm being dense, but I really don't know where this
>>> favoritism feeling is coming from.
>>>
>>> Let me back up a bit... MGOS doesn't have a process for the sandbox, and
>>> so I thought I was doing the right thing by making sure to ask the PSC for
>>> the rights to the sandbox for some developers. So yes, we need to vote or
>>> do something. What did I do wrong to get so much concern about this request?
>>> Please tell me, I would like to know? Should I just tell the developers that
>>> they should forget this approach?
>>>
>>>
>>> -----Original Message-----
>>> From: [hidden email]
>>> [mailto:[hidden email]] On Behalf Of Kenneth
>>> Skovhede, GEOGRAF A/S
>>> Sent: Thursday, June 25, 2009 11:49 AM
>>> To: MapGuide Internals Mail List
>>> Subject: Re: [mapguide-internals] Motion: Give developers commit rights to
>>> work in a sandbox
>>>
>>> If I understand Frank correctly, it is "easy" to create a sandbox in svn.
>>> With this sandbox anyone (in theory) should be allowed a sandbox area,
>>> for free play and testing.
>>>
>>> If this is so, I don't see the need for this vote.
>>> I think UV would like a sandbox as well.
>>>
>>> The open source handbook:
>>> http://producingoss.com/
>>>
>>> clearly states that the founding company should not try to bypass the
>>> rules, as that will make the project appear "closed" in the sense that
>>> only "insiders" get commit access, which is the opposite of the goal
>>> with OS software.
>>>
>>> I'm not suggesting that there is foul play here, and I am confident that
>>> the proposed developers are highly skilled, but seen from the outside,
>>> this looks a bit like favorizing the Autodesk people.
>>>
>>> I would suggest that we instead clear up any confusion on the sandbox
>>> issues,
>>> and make sandboxes avalible for those who apply for one.
>>> If there are too many requests for sandboxes, we will have to reconsider
>>> what criteria there should be for applicants.
>>>
>>> Regards, Kenneth Skovhede, GEOGRAF A/S
>>>
>>>
>>>
>>> Tom Fukushima skrev:
>>>
>>>>
>>>> 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
>>>>
>>>> Thanks
>>>> Tom
>>>> _______________________________________________
>>>> mapguide-internals mailing list
>>>> [hidden email]
>>>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>>>
>>>
>>> _______________________________________________
>>> mapguide-internals mailing list
>>> [hidden email]
>>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>> _______________________________________________
>>> mapguide-internals mailing list
>>> [hidden email]
>>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>>
>>
>> _______________________________________________
>> mapguide-internals mailing list
>> [hidden email]
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
>
>
>
> --
> Zac Spitzer -
> http://zacster.blogspot.com
> +61 405 847 168
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>

Trevor Wekel-3

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

Hi Zac,

Nice find. It is another option to explore. But I think we would only need the Crucible portion of Studio. We already have an issue tracker, wiki, repository viewer, and subversion repository. One thing I would be concerned about is integration with our existing infrastructure. Crucible seems to be integrated with Studio.

Thanks,
Trevor

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Zac Spitzer
Sent: Friday, June 26, 2009 4:01 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox

http://www.atlassian.com/studio/ ? it's free for opensource projects

On Fri, Jun 26, 2009 at 7:35 PM, Trevor Wekel<[hidden email]> wrote:

Tom Fukushima

RE: Motion: Give developers commit rights to work in a sandbox

Reply Threaded

In reply to this post by Kenneth Skovhede, GEOGRAF A/S

Kenneth,

Let me reiterate. We don't have a process for the sandbox, until we define the process for setting up sandboxes especially since we have not set up subversion so that sandbox users cannot submit to the mainstream; and how it can be used, etc, I (nor you) cannot go and make arbitrary decisions about it. If I did, I think that would be unfair.

I don't think that the definition of a sandbox is in question. It is a place to "play".

I am not aware of a request from UV for a sandbox; I don't know why we would reject such a request actually.

Honestly, your vote of -0 makes me feel less positive about this project.

Tom

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Kenneth Skovhede, GEOGRAF A/S
Sent: Friday, June 26, 2009 12:47 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] Motion: Give developers commit rights to work in a sandbox

Tom,

I don't think you are being dense. We just see this from different angles.

Your request is to allow some qualified developers acceptable working
conditions.
I totally support that. The more the merrier.

But, your request looks very similar to a request made by UV a little while
back. His request was denied, because there was no means of getting a
sandbox.

If I have overlooked a difference in the two requests, I will be happy to
be informed of the differences.

There may be valid reasons for allowing one request, and not another, but in
your mail, it initially appeared to me as if the difference was your
confidence
in the developers. I don't see that as a valid reason (although I trust
your
judgement).

After re-reading the mail, I can see that your confidence was mentioned
to assure us
that they would not start commiting to areas they were not supposed to.

As for favorism, I don't see anyone else having the privileges that you
are requesting
for the proposed contributors. And I can't see how anyone else could
apply for something
like it. As always, I'm gladly corrected.

There may also be a misunderstanding about what an "SVN Sandbox" is
supposed to be or do.
I have my idea of a sandbox from OpenLayers:
http://faq.openlayers.org/svn/how-can-i-get-commit-access-to-the-svn-repository/

In the OL sense, a sandbox is a free-for-all playground, where anyone
can get access.
I am under the impressions that this is possible in MapGuide too, so
there is no
need to vote on this issue, we should just set it up, free for all.

If I misunderstood that part, I would also be happy to be informed.

Having a sandbox would potentially open up for many more developers, and
make
stuff like reviews of specific cases better.

I vote -0.
I want the developers on board, but I
don't like the method.

Regards, Kenneth Skovhede, GEOGRAF A/S

Tom Fukushima skrev:

1 2