ACL sharing between ivy and ant

[Gilles Scokart <gs...@gmail.com>]

I know I might comes a little bit late with my question.

I have no problem to have all ant committers becoming ivy commiter.
Certainly not.  It is a quick way to increase the size of the ivy community.

But I suddently have a doubt on what will happen if someone demonstrates his
trustability to the ivy community but is not present in the ant community?

How will be the vote for a new committer being made in that context?


-- 
Gilles SCOKART

Re: ACL sharing between ivy and ant

[Stefan Bodewig <bo...@apache.org>]

On Wed, 03 Oct 2007, Steve Loughran <st...@apache.org> wrote:
> Gilles Scokart wrote:
>
>> But I suddently have a doubt on what will happen if someone
>> demonstrates his trustability to the ivy community but is not
>> present in the ant community?  How will be the vote for a new
>> committer being made in that context?
> 
> I guess you make them a committer in ivy; they get access to both.

Same here.

So far we've had a single community at Ant and we'll learn together
how to deal with the single ACL when Ivy joins Ant.  It certainly is a
two-way road.

> -All commits on ant get looked by other people; its pretty hard to
> get away with something drastic except in a commit so big the mailer
> doesn't send it to the group (>100K of change).

I think this limit went away when we switched from CVS to svn.  The
new mailer code splits commit mails and will send them no matter how
big the change is.

Stefan

Re: ACL sharing between ivy and ant

[Steve Loughran <st...@apache.org>]

Gilles Scokart wrote:
> I know I might comes a little bit late with my question.
> 
> I have no problem to have all ant committers becoming ivy commiter.
> Certainly not.  It is a quick way to increase the size of the ivy community.
> 
> But I suddently have a doubt on what will happen if someone demonstrates his
> trustability to the ivy community but is not present in the ant community?
> 
> How will be the vote for a new committer being made in that context?
> 
> 


I guess you make them a committer in ivy; they get access to both.


-there's almost no security risk in ant changes; its hard for anyone to 
deliberately stick a back door in, the way you could with Xerces or Axis.

-biggest risk is just making backwards-incompatible changes to classes 
and tasks.

-All commits on ant get looked by other people; its pretty hard to get 
away with something drastic except in a commit so big the mailer doesn't 
send it to the group (>100K of change). We'd ask some hard questions if 
a change that big went in, as it is incredibly rare.

steve


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org

Re: ACL sharing between ivy and ant

[Steve Loughran <st...@apache.org>]

Gilles Scokart wrote:
> I know I might comes a little bit late with my question.
> 
> I have no problem to have all ant committers becoming ivy commiter.
> Certainly not.  It is a quick way to increase the size of the ivy community.
> 
> But I suddently have a doubt on what will happen if someone demonstrates his
> trustability to the ivy community but is not present in the ant community?
> 
> How will be the vote for a new committer being made in that context?
> 
> 


I guess you make them a committer in ivy; they get access to both.


-there's almost no security risk in ant changes; its hard for anyone to 
deliberately stick a back door in, the way you could with Xerces or Axis.

-biggest risk is just making backwards-incompatible changes to classes 
and tasks.

-All commits on ant get looked by other people; its pretty hard to get 
away with something drastic except in a commit so big the mailer doesn't 
send it to the group (>100K of change). We'd ask some hard questions if 
a change that big went in, as it is incredibly rare.

steve