Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44025 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 97417 invoked from network); 18 May 2009 16:54:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 May 2009 16:54:19 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 83.243.58.133 as permitted sender) X-PHP-List-Original-Sender: johannes@php.net X-Host-Fingerprint: 83.243.58.133 mailout1.netbeat.de Linux 2.6 Received: from [83.243.58.133] ([83.243.58.133:57076] helo=mailout1.netbeat.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F6/BA-44945-2B2911A4 for ; Mon, 18 May 2009 12:54:13 -0400 Received: (qmail 10052 invoked by uid 89); 18 May 2009 17:14:17 -0000 Received: from unknown (HELO ?192.168.1.102?) (johannes%schlueters.de@62.216.212.199) by mailout1.netbeat.de with ESMTPA; 18 May 2009 17:14:17 -0000 To: Sahid Ferdjaoui Cc: Christopher Jones , David Coallier , internals@lists.php.net In-Reply-To: References: <4A0C5CFC.6010705@oracle.com> Content-Type: text/plain Date: Mon, 18 May 2009 18:54:05 +0200 Message-ID: <1242665645.6751.17.camel@goldfinger> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] How to contribute for PHP Internals From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Fri, 2009-05-15 at 12:58 +0200, Sahid Ferdjaoui wrote: > Yes, why not :) > > By get involved section, > i seek a guideline for contribute for each different points. > > * Internal development > * References > * TSRM > * Zend Engine API > * ... Some documentation on this exists in the manual: http://php.net/internals2 Not sure how much but we might try to revive the internals-doc-writing efforts... > * Coding standard http://de2.php.net/reST/php-src/CODING_STANDARDS > * Get Started > * Features > * Bugs > * motivate ? go to seek a bug now ! > * ok, no panic, explain and purpose a patch > * ... Would help if the Bug Tracker was extended to mark (hopefully) low hanging fruits for starters.... [...] so lot's of information *is* available but very unstructured and distributed over many places. So a start might be to collect the links to one place with some guiding comments... > for example i like it : > http://live.gnome.org/JoinGnome That recently drove me nuts, I just wanted to locate the current VCS repository one of their projects was using for creating a simple patch, which I had ready against an older release but there was too much "irrelevant" information hiding the things was looking for. No I'm not looking for a Gtk tutorial, not for a mentor, not for love (well, maybe I do, but not related to gnome), ... But that's actually the tough part: Don't become too verbose while providing tons of information while again be motivational to beginners, too. johannes