Re: CVS Account Request
| From: | Zeev Suraski | Date: | Wed, 15 Nov 2000 21:42:20 +0000 |
| Subject: | Re: CVS Account Request | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-38204@lists.php.net to get a copy of this message | ||
At 00:28 16/11/2000, Rasmus Lerdorf wrote:
Now, one can make a big deal out of it, and take it 'personally', that I don't think the Web guys should have write access to the source code. This shouldn't be the case though. It's just better for things to be organized than not. Since Zak, for instance, has no benefit in having write access to the php4 tree, there's no good reason he should have write access there. I wouldn't deny him, or anybody else access if it's useful for them, but right now, people are getting access to the source repository for no good reason other than a historically messed-up setup. Well, the reason it makes sense for the doc folks to have commit access to the source tree is so that they can keep the embedded prototype comments in synch with the documentation.I thought about it too, that's why I talked about the Web guys in my example.
And I don't really see this multitude of bugs introduced by people who shouldn't be committing things. These problems have been introduced by people to whom I doubt we would have denied cvs access to under a stricter system.Granted, there were less, but there were some. I think that the current way CVS works is a bit too trusting, especially for new people. I don't see a real problem if people send in patches for a few weeks before they're granted write access to the source. With the popularity of PHP, there comes some responsibility. I didn't find it too much fun at all to have to represent the dev team on bugtraq. The bugtraq security bugs were in the core, in some of the concepts of the language. I don't want to increase the number of appearances on bugtraq beyond the bare minimum. Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/