Re: How to contribute for PHP Internals
| From: | Sahid Ferdjaoui | Date: | Fri, 15 May 2009 10:58:01 +0000 |
| Subject: | Re: How to contribute for PHP Internals | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-43982@lists.php.net to get a copy of this message | ||
Yes, why not :)
By get involved section,
i seek a guideline for contribute for each different points.
* Internal development
* References
* TSRM
* Zend Engine API
* ...
* Coding standard
* Get Started
* Features
* Bugs
* motivate ? go to seek a bug now !
* ok, no panic, explain and purpose a patch
* ...
* Pecl development
* How to (ok ...Sara Golemon's book)
* What php need ?
* QA
* Documentation
Because php is a very big project and it is dificulte to say:
"No problem Rasmus...,
you can take a nap, i will fix this bug." ;)
for example i like it :
http://live.gnome.org/JoinGnome
--
~/sahid
http://sahid.funraill.org
On Thu, May 14, 2009 at 8:03 PM, Christopher Jones
<christopher.jones@oracle.com> wrote:
>
>
> David Coallier wrote:
>>
>> 2009/5/14 Sahid Ferdjaoui <sahid.ferdjaoui@gmail.com>:
>>>
>>> Hello Internals,
>>>
>>> I want to contribute for PHP Internal,
>>> but i don't know how to do it.
>>>
>>> I am ready to give approximately 6 to 12 hours per week for PHP.
>>>
>>> i have checked a wiki,
>>> but i don't see a "get involved" section and i do not know how to start
>>> :)
>>>
>>
>> The best way to get started is to check +3
>> §³j¤ÜÛ+ îúœ$http://php.net/anoncvs make a
>> checkout of HEAD (php6) and then go to http://bugs.php.net
>> start
>> making patches and attach them to bug reports.
>>
>> From there you will gain developers trust (People will be tired of
>> committing all your patches) and at some point you'll be granted with
>> an account :)
>>
>> Good luck and welcome :)
>>
>
> Yes, welcome!
>
> Perhaps you could create a "get involved" wiki section based on what you
> find out about getting involved?
>
> Chris
>
> --
> Email: christopher.jones@oracle.com
> Twitter: Â http://twitter.com/ghrd
>