Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:11206 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14039 invoked by uid 1010); 13 Jul 2004 21:13:57 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 13975 invoked from network); 13 Jul 2004 21:13:57 -0000 Received: from unknown (HELO miranda.org) (209.58.150.153) by pb1.pair.com with SMTP; 13 Jul 2004 21:13:57 -0000 Received: (qmail 25527 invoked by uid 546); 13 Jul 2004 21:13:56 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 13 Jul 2004 21:13:56 -0000 Date: Tue, 13 Jul 2004 17:13:56 -0400 (EDT) X-X-Sender: adam@miranda.org To: Daniel Crookston cc: Chris , internals@lists.php.net In-Reply-To: <20040713210434.X23650@hyperion-data.net> Message-ID: References: <5.1.0.14.2.20040712141042.03166120@127.0.0.1> <200407131032.34451.edink@emini.dk> <40F44B64.2040705@leftbrained.org> <20040713210434.X23650@hyperion-data.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] PHP 5.0.0 Test roll From: adam@trachtenberg.com (Adam Maccabee Trachtenberg) 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 -- adam@trachtenberg.com author of o'reilly's "upgrading to php 5" and "php cookbook" avoid the holiday rush, buy your copies today!