On Tue, 13 Jul 2004, Daniel Crookston wrote: > So, am I being lazy, have I missed some docs on the web regarding how to > be useful, or how to become familiar enough with the PHP code to start > lending a hand with the debugging? Or are we expected to learn it > ourselves, on our own, in order to be accepted into "the club" as it were? > (Not that there's anything wrong with that, it's just that a lot of groups > require self-validation like that.)
The general method of helping out (at first) is to review open bug reports and post patches to this list. Someone will then review and merge into the code base. A pattern of good patches leads to greater CVS karma, so you can apply them yourself. If you're not up for that right now, you could go through open reports and help classify them, provide reproducing test cases (and/or backtraces), mark them as bogus, etc. There's no good online "here's how PHP's C internals work," but George's "Advanced PHP Programming" book is a good place to start reading. -adam -- [EMAIL PROTECTED] author of o'reilly's "upgrading to php 5" and "php cookbook" avoid the holiday rush, buy your copies today! -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
