Re: CVS Account Request

It looks like my message was deleayed...., but I see it just arrived. Also, I would like to point out (as far as exploits being imbeded into source) that CVS commits are still developmental, and php still has to go through the full Release/Review process. I do agree that having a security policy is good, and some protection is always usefull. If someone is really wanting to contribute, they will be fine waiting for an account. Its also a good experience when your starting off to run patches by a developer whos more experienced with the code your modifing. This really is a good process, if for no other reason than allowing the newcomer to learn the style and form of the project. -Jason ----- Original Message ----- From: "Zeev Suraski" <zeev@zend.com> To: "Rasmus Lerdorf" <rasmus@php.net> Cc: "Sterling Hughes" <Sterling.Hughes@pentap.net>; <php-dev@lists.php.net> Sent: Wednesday, November 15, 2000 2:35 PM Subject: Re: [PHP-DEV] CVS Account Request > At 01:24 16/11/2000, Rasmus Lerdorf wrote: > >But how do we do that? By reducing the number of commits? That doesn't > >sound like the right answer to me. > > No, by making it a bit more difficult for an infiltrator to get in, and if > he does, reduce the amount of damage he can do. As Jason said, people who > actually want to work on PHP can live easily with the need to send patches > for a couple of weeks, and accept CVS write access either. I think that > they would actually think it's a good practice, and the way an organized > project should be working in anyway (again, see what Jason said). > I also think that someone who receives CVS access to develop a module for > FooSQL, won't find it insulting or weird if he only got access to the > ext/foosql directory on the repository. > > >That's not entirely true. Yes, doc people and lately pear people have had > >semi-automatic cvs accounts created. I have had dozens of exchanges with > >people wanting to contribute to the codebase before setting up the cvs > >account. But we could formalize this and write it down somewhere. > > > Well, a part of that could be that none of us ever saw these exchanges, or > even knew of their existence. It seemed that sometimes, from the time > requests showed up on group@ and till the time you added people to the CVS > writers, it took less than a day... > At any rate, if that's how things work anyway, it may be a good idea to > formalize it as you said, or perhaps more these discussions over to php-dev > as well. It can end up being useful. > > Zeev > > Zeev Suraski <zeev@zend.com> > CTO, Zend Technologies Ltd. http://www.zend.com/ > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >