Re: How to contribute for PHP Internals

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