For whatever reason this seems to be the week of people
wanting to help
out with PhpDocumentor. Thanks 
The best way to get started is too join the developer
mailing list
(http://lists.bluga.net/mailman/listinfo/phpdocumentor
-devel) and to
start fixing some bugs.
The basic process is find a bug you want to work on, from
the roadmap:
http://pear.php.net/bug
s/roadmap.php?roadmapdetail=1.4.1&package=PhpDocumentor#
a1.4.1
Send a message to the list letting people know your working
on it and
ask any questions you might have.
Fix the bug and attach a patch and ask Chuck or me to review
it on the
mailing list.
After you've done that a couple times I'll set you up with
accounts
everywhere and eventually give you commit access.
In general the phpDocumentor code base is a bit of a mess,
Chuck is
currently working on a project to clean it up, but that will
take awhile.
So don't let the code intimidate you, just for a pointer on
where to
look for fixing something.
Let me know if you have any questions.
-josh
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Phpdocu-developer mailing list
Phpdocu-developer lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phpdo
cu-developer
|
