Great topic... a few thoughts:
- Internals documentation
This task needs volunteers. Ideally a mix of people who have either
no, some or enormous knowledge of internals but all with desire to
both learn and teach it. Gwynne started the task but ran out of steam
(life and the svn migration got in the way) but some good content
exists. But, this is its own topic. Volunteers please email me and
let's organize a hackfestish type event.
- Bug tracker as a starting point
The idea of intentionally creating nice bug reports for fairly simple
non-critical issues, and promoting these as tasks for new people
definitely sounds worth the extra effort. All ideas for how the bug
tracker could help with this are welcome.
- A "Get Involved" guide
Some nice thoughts in this thread, and similar ones for a _rough_ TOC
here:
- http://wiki.php.net/doc/scratchpad/wheretohelp
The basic idea is to create and promote a "Get Involved" section. To
digress, awhile back while thinking about this (and wondering how the
php.net project survives without it) I stumbled around and started a
different yet related project:
- http://teachingopensource.org/index.php/Teaching_Get_Involved
The plan is to learn how best to approach this topic and then apply it
to php.net. If people are interested in working on this or only
php.net specific parts then please let me know. So what that it's
taken us 10 years to write a nice "Get Involved" guide, but at least
we now have several resources to learn [steal!] ideas from while we
create our own :) Common problems like repeated, lost and outdated
content can no doubt be overcome.
Regards,
Philip
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
