From: "Leo Simons" <[EMAIL PROTECTED]>
> On Wed, 2002-05-29 at 14:04, Andrew C. Oliver wrote:
> > I don't think
> > there is anything to forbid a community from temporarily granting CVS
> > access.
>
> ;)
>
> Well, I think our guidelines forbid us. You cannot give someone CVS
> access without giving them all the committer rights and responsibilities
> as well. That's the point of the discussion, innit?
Yes, it is.
I regard CVS as the heart of our system.
Would you make a well known surgeon operate your heart without knowing him
first, and being sure he can assist you afterwards?
If you do, usually it's for emergencies... like wanting some 20MB patch to
be in CVS and not having time to do it.
Personally, I would prefer not have the patch at all, if it means giving
access to the CVS to someone you don't trust.
And if you trust him, there is no time limit.
Nothing prevents him from asking his account to be deleted anyway.
If you invite someone in the boat with you, it's because you think that
he'll be part of the group, and share roles and responsibilities; I don't
think we need technical "repairmen" here.
I may be wrong, but for me it's a matter of trust, personal trust.
I have been contributing stuff to Cocoon since version 1.7, but never
proposed as a comitter.
Why?
Because I wasn't ready for OS collaboration, and they didn't trust me.
This made me stronger, and I learned a lot.
Now you made me come in Avalon just on my word and good proposition, and
this is something I will never forget. It has a very strong meaning for me.
I would like that others have these possibilities, that have made me learn a
lot.
I'm afraid that having "technitians" would break up this system.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
