You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Stefan Bodewig <bo...@apache.org> on 2005/07/13 15:36:28 UTC
Controlling access to metadata
Hi,
it turned out that rw=* as access rule is a bad idea. Not only caused
it the mailer script to drop author information, it allwed everybody
commit access to the metadata. Not all Apache committers, literally
everybody (with a svn client).
Henri has now created a group in the authorization file that contains
all people from the apcvs group on minotaur. This one is bound to get
out of date when new accounts get created.
I'd suggest we restrict the list to all people who've committed to
Gump's metadata so far and extend it on request.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Controlling access to metadata
Posted by Scott Sanders <sc...@dotnot.org>.
On Jul 13, 2005, at 6:36 AM, Stefan Bodewig wrote:
> I'd suggest we restrict the list to all people who've committed to
> Gump's metadata so far and extend it on request.
+1, simple request to this mailing list should suffice.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Controlling access to metadata
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 13 Jul 2005, Adam R. B. Jack <aj...@apache.org> wrote:
> That said, who has rights to modify it? Can the Gump PMC members who
> are ASF members do it w/o needing to bug infrastructure@? I'd hope
> so.
Not quite. All PMC chairmen and the nice people from infrastructure
can, i.e. of the Gump PMC me, Leo and Scott can.
> Also, is there any way we can have some notice grab first time
> committer's attention? Some ASF_COMMITTERS_READ_ME.txt in the root,
> or something.
Sure feel free to become as creative as you like 8-)
> Or, is there a way to get some notice given upon commit failures?
I don't think so, unfortunately.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Controlling access to metadata
Posted by "Adam R. B. Jack" <aj...@apache.org>.
> Henri has now created a group in the authorization file that contains
> all people from the apcvs group on minotaur. This one is bound to get
> out of date when new accounts get created.
Yeah, stale is bad.
> I'd suggest we restrict the list to all people who've committed to
> Gump's metadata so far and extend it on request.
Agreed. It isn't a huge barrier for folks to ask the first time. That said,
who has rights to modify it? Can the Gump PMC members who are ASF members do
it w/o needing to bug infrastructure@? I'd hope so.
Also, is there any way we can have some notice grab first time committer's
attention? Some ASF_COMMITTERS_READ_ME.txt in the root, or something. Or, is
there a way to get some notice given upon commit failures?
regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org