Re: Looking docs on a site. QA

On Tue, 2004-11-09 at 22:46, Greg Beaver wrote: > Tip wrote: > > Hello Helgi, > > > > > >>>And so it is with CVS. I believe that developers can decide on their > >>>own who can make changes to the original code they've commited to the > >>>world. > > > > HЮ> Just wanted to add a little note, this will never happen actually, the > > HЮ> current CVS server doesn't have such a mechanism, and in it's current > > HЮ> state it could be plain dangerous to try achieving something like that > > HЮ> :) > > > > Why? Every problem has a solution. Can you plug a script into > > /CVSROOT/commitinfo to fetch information about current developers > > permissions and to allow/deny access based on that setting? > > There also can be interface for developers so they can add or remove > > people from CVS access to thier modules. > > This is a huge security risk. Not all developers are excellent judges > of character, it's better that approval be a bit slower but more regulated. > > If CVS was completely separate for each pear module, it would be a > different story. Many developers have full access the the PEAR CVS > tree, and probably should not be granting complete control to unknown folks. That's what I was talking about, sometimes to much freedom will turn things into chaos ;) Regarding the full access, it would actually be okey to start fine graining that access level. - Helgi