Jason van Zyl | 22 Dec 2005 18:52

[mojo-dev] [vote] sandbox access for james strachan

Hi,

James wants to contribute a retroweaver plugin so I figured sandbox 
access would be appropriate. James is an activemq and service mix guy.

+1

--

-- 

jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.

   -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)

Jason van Zyl | 22 Dec 2005 18:56

[mojo-dev] [vote] everyone to use https to access svn

Hi,

Currently there we have a problem on beaver where svn over https will 
only work if we change the ownership of the scm/ directory to apache. 
The problem lies in the fact that there is a limit as to how many groups 
a user can be in (32) and right now the apache user is in more then 32 
groups and apache needs access to the scm/ directory in order to write.

So the upside is that https will work for everyone if we change the 
ownership of the scm/ dir to apache, but the downside is that svn+ssh 
will no longer work.

Does anyone mind switching over to https and ditching svn+ssh access?

--

-- 

jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

the course of true love never did run smooth ...

  -- Shakespeare

Carlos Sanchez | 22 Dec 2005 18:21
Picon
Favicon
Gravatar

Re: [mojo-dev] [vote] everyone to use https to access svn

+1 to https

On 12/22/05, Jason van Zyl <jason <at> maven.org> wrote:
> Hi,
>
> Currently there we have a problem on beaver where svn over https will
> only work if we change the ownership of the scm/ directory to apache.
> The problem lies in the fact that there is a limit as to how many groups
> a user can be in (32) and right now the apache user is in more then 32
> groups and apache needs access to the scm/ directory in order to write.
>
> So the upside is that https will work for everyone if we change the
> ownership of the scm/ dir to apache, but the downside is that svn+ssh
> will no longer work.
>
> Does anyone mind switching over to https and ditching svn+ssh access?
>
> --
>
> jvz.
>
> Jason van Zyl
> jason at maven.org
> http://maven.apache.org
>
> the course of true love never did run smooth ...
>
>   -- Shakespeare
>

(Continue reading)

Jeff Genender | 22 Dec 2005 18:27

Re: [mojo-dev] [vote] sandbox access for james strachan

+1

Jason van Zyl wrote:
> Hi,
> 
> James wants to contribute a retroweaver plugin so I figured sandbox
> access would be appropriate. James is an activemq and service mix guy.
> 
> +1
> 

Alan D. Cabrera | 22 Dec 2005 18:31
Gravatar

Re: [mojo-dev] [vote] everyone to use https to access svn

On 12/22/2005 9:56 AM, Jason van Zyl wrote:

> Hi,
>
> Currently there we have a problem on beaver where svn over https will 
> only work if we change the ownership of the scm/ directory to apache. 
> The problem lies in the fact that there is a limit as to how many 
> groups a user can be in (32) and right now the apache user is in more 
> then 32 groups and apache needs access to the scm/ directory in order 
> to write.
>
> So the upside is that https will work for everyone if we change the 
> ownership of the scm/ dir to apache, but the downside is that svn+ssh 
> will no longer work.
>
> Does anyone mind switching over to https and ditching svn+ssh access?
>
+1 on switching over to https and ditching svn+ssh access

Regards,
Alan

Jeff Genender | 22 Dec 2005 18:37

Re: [mojo-dev] [vote] everyone to use https to access svn

+1...this would be great.

Alan D. Cabrera wrote:
> On 12/22/2005 9:56 AM, Jason van Zyl wrote:
> 
>> Hi,
>>
>> Currently there we have a problem on beaver where svn over https will
>> only work if we change the ownership of the scm/ directory to apache.
>> The problem lies in the fact that there is a limit as to how many
>> groups a user can be in (32) and right now the apache user is in more
>> then 32 groups and apache needs access to the scm/ directory in order
>> to write.
>>
>> So the upside is that https will work for everyone if we change the
>> ownership of the scm/ dir to apache, but the downside is that svn+ssh
>> will no longer work.
>>
>> Does anyone mind switching over to https and ditching svn+ssh access?
>>
> +1 on switching over to https and ditching svn+ssh access
> 
> 
> Regards,
> Alan
> 
> 

Kris Bravo | 21 Dec 2005 22:29
Picon

Re: [mojo-dev] [vote] everyone to use https to access svn


+1 https access.

There are times I'm behind a proxy that blocks ssh, so this is a good
thing for me.

Kris Bravo
Corridor Software, Inc.
http://www.corridor-software.us

> Hi,
>
> Currently there we have a problem on beaver where svn over https will
> only work if we change the ownership of the scm/ directory to apache.
> The problem lies in the fact that there is a limit as to how many groups
> a user can be in (32) and right now the apache user is in more then 32
> groups and apache needs access to the scm/ directory in order to write.
>
> So the upside is that https will work for everyone if we change the
> ownership of the scm/ dir to apache, but the downside is that svn+ssh
> will no longer work.
>
> Does anyone mind switching over to https and ditching svn+ssh access?
>
> --
>
> jvz.
>
> Jason van Zyl
> jason at maven.org
(Continue reading)

Kris Bravo | 21 Dec 2005 22:30
Picon

Re: [mojo-dev] [vote] sandbox access for james strachan

+1

Kris Bravo
Corridor Software, Inc.
http://www.corridor-software.us

> Hi,
>
> James wants to contribute a retroweaver plugin so I figured sandbox
> access would be appropriate. James is an activemq and service mix guy.
>
> +1
>
> --
>
> jvz.
>
> Jason van Zyl
> jason at maven.org
> http://maven.apache.org
>
> First, the taking in of scattered particulars under one Idea,
> so that everyone understands what is being talked about ... Second,
> the separation of the Idea into parts, by dividing it at the joints,
> as nature directs, not breaking any limb in half as a bad carver might.
>
>    -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
>

(Continue reading)

Brian E. Fox | 22 Dec 2005 18:38
Picon
Gravatar

RE: [mojo-dev] [vote] everyone to use https to access svn

+1 

-----Original Message-----
From: Jeff Genender [mailto:jgenender <at> codehaus.org] 
Sent: Thursday, December 22, 2005 12:38 PM
To: dev <at> mojo.codehaus.org
Subject: Re: [mojo-dev] [vote] everyone to use https to access svn

+1...this would be great.

Alan D. Cabrera wrote:
> On 12/22/2005 9:56 AM, Jason van Zyl wrote:
> 
>> Hi,
>>
>> Currently there we have a problem on beaver where svn over https will

>> only work if we change the ownership of the scm/ directory to apache.
>> The problem lies in the fact that there is a limit as to how many 
>> groups a user can be in (32) and right now the apache user is in more

>> then 32 groups and apache needs access to the scm/ directory in order

>> to write.
>>
>> So the upside is that https will work for everyone if we change the 
>> ownership of the scm/ dir to apache, but the downside is that svn+ssh

>> will no longer work.
>>
(Continue reading)

dan tran | 22 Dec 2005 18:53
Picon

Re: [mojo-dev] [vote] everyone to use https to access svn

+1


 
On 12/22/05, Brian E. Fox <brianf <at> reply.infinity.nu> wrote:
+1

-----Original Message-----
From: Jeff Genender [mailto: jgenender <at> codehaus.org]
Sent: Thursday, December 22, 2005 12:38 PM
To: dev <at> mojo.codehaus.org
Subject: Re: [mojo-dev] [vote] everyone to use https to access svn

+1...this would be great.

Alan D. Cabrera wrote:
> On 12/22/2005 9:56 AM, Jason van Zyl wrote:
>
>> Hi,
>>
>> Currently there we have a problem on beaver where svn over https will

>> only work if we change the ownership of the scm/ directory to apache.
>> The problem lies in the fact that there is a limit as to how many
>> groups a user can be in (32) and right now the apache user is in more

>> then 32 groups and apache needs access to the scm/ directory in order

>> to write.
>>
>> So the upside is that https will work for everyone if we change the
>> ownership of the scm/ dir to apache, but the downside is that svn+ssh

>> will no longer work.
>>
>> Does anyone mind switching over to https and ditching svn+ssh access?
>>
> +1 on switching over to https and ditching svn+ssh access
>
>
> Regards,
> Alan
>
>




Gmane