Re: Two new projects in the CVS and 5th Toe



> > I've almost never wanted to commit something for the first time to
> > a module without asking the maintainer for an OK first.
> 
> The problem is that it takes a real amount of extra work to commit a 
> change to the permissions file than to say "yes, this patch looks good 
> please commit it"...

So how about this[1]: The first time someone tries to commit something
to a given module, the cvs server would reject them, spew the contents
of README.HACKING at them[2], and then *add them to the ACL*. Any
further attempts to commit would then succeed. Assuming you already got
an OK from the maintainers, you just immediately commit again and you're
done.

This wouldn't stop determined vandals and/or morons, but it should help
prevent well-meaning newbies from breaking other people's code.

-- Dan

[1] inspired by http://projects.puremagic.com/greylisting/
[2] I have no idea if this is actually possible in the CVS protocol



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]