Re: CVS Account Request
| From: | Zeev Suraski | Date: | Wed, 15 Nov 2000 23:53:45 +0000 |
| Subject: | Re: CVS Account Request | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-38273@lists.php.net to get a copy of this message | ||
At 01:43 16/11/2000, Joey Smith wrote:
In the middle of all of this, I wanted to throw my 2 bits in regarding "extension specific commit". While most of the work that I have contributed has been in the Sybase CT extension (and not much at that), there have been occasional things I have found inside of various other extensions that stood out to me, but slipped past the module owner/maintainer for quite a while. In most cases, I tried to contact the owner before doing anything, but in some cases, these people have a spotty relationship to their modules. Not that I don't understand the issues involved...we're all pretty much volunteers here. I'm just saying that I, for one, would be against the concept of "extension specific commit", bcz it limits my already meager abilities.If you found a bug in one or two extensions, adding you to the ACL's for these extensions as well wouldn't have been a problem. I actually think that sometimes outsiders *think* they've found a bug, but because they don't actually understand what's going on in the code exactly, their fix may actually make things much worse. I'm not saying that's what happened in your case (it probably didn't), but it has happened before several times. After a few useful commits made to extensions other than the one you applied for, it may make sense to give you access to the entire tree, because you become an 'all arounder' to a degree. I think there are plenty of people who only maintain their extensions, and don't touch anything in other directories. Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/