Re: CVS Account Request
| From: | Zeev Suraski | Date: | Wed, 15 Nov 2000 21:50:38 +0000 |
| Subject: | Re: CVS Account Request | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-38208@lists.php.net to get a copy of this message | ||
I tend to agree with Rasmus on that one.
I think that the ability to get write access to the tree today is all too easy, or for that matter, takes way too little time.
In my opinion, sending out patches for a few weeks is not going to be beyond our abilities. After people established their need for CVS write access, we can grant them write access. It would be even better if people who get in to support specific extension get write access to this extension only.
Zeev
At 00:47 16/11/2000, Rasmus Lerdorf wrote:
Another option is to have a two-person commit system for all code and all committers, where one person writes the code and then someone trusted, who volunteers for the job commits the code for that area of php (thus giving responsibility to two people, and hopefully, assuring that the code has been qa'ed). Sterling, unless you are willing and have time do do this peer-review yourself, there isn't much point in suggesting it. This review-then-commit approach was tried in the Apache project and it finally had to be abandoned because the backlog of contributions piled up to the point that contributors got frustrated and gave up when they did not receive a timely response. -Rasmus -- 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-- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/