@@ -6,7 +6,7 @@ websites is a never-ending one. With every release or release candidate comes a
66wave of work, which takes a lot of organization and co-ordination.
77
88You don't need any special access to download, build, debug and begin submitting
9- PHP or PECL code, tests or documentation. Once you've followed this guide and
9+ PHP or extension code, tests or documentation. Once you've followed this guide and
1010had several contributions accepted, commit privileges are often quickly granted.
1111
1212## Index
@@ -20,7 +20,7 @@ had several contributions accepted, commit privileges are often quickly granted.
2020* [ Getting help] ( #getting-help )
2121* [ PHP source code directory structure] ( #php-source-code-directory-structure )
2222* [ PHP internals] ( #php-internals )
23- * [ PECL extensions ] ( #pecl- extensions )
23+ * [ Extensions ] ( #extensions )
2424* [ Checklist for submitting contribution] ( #checklist-for-submitting-contribution )
2525* [ What happens after submitting contribution?] ( #what-happens-after-submitting-contribution )
2626* [ What happens when your contribution is applied?] ( #what-happens-when-your-contribution-is-applied )
@@ -149,11 +149,6 @@ about what you're working on, you can contact us via the
149149[ documentation mailing list] ( mailto:phpdoc@lists.php.net ) for documentation
150150issues.
151151
152- Although not a formal channel, you can also find a number of core developers on
153- the #php.pecl channel on [ EFnet] ( http://www.efnet.org/ ) . Similarly, many
154- documentation writers can be found on #php.doc. Windows development IRC channel
155- is available at #winphp-dev on FreeNode.
156-
157152## PHP source code directory structure
158153
159154PHP source code also includes several files generated during development and
@@ -237,7 +232,6 @@ locations.
237232 ├─ streams/ # Streams layer subsystem
238233 ├─ php_version.h # Generated by release managers using `configure`
239234 └─ ...
240- ├─ pear/ # PEAR installation
241235 └─ sapi/ # PHP SAPI modules
242236 └─ cli/
243237 ├─ mime_type_map.h # Generated by `sapi/cli/generate_mime_type_map.php`
@@ -258,27 +252,14 @@ For information on PHP internal C functions see
258252Various external resources can be found on the web. A standard printed reference
259253is the book "Extending and Embedding PHP" by Sara Golemon.
260254
261- ## PECL extensions
255+ ## Extensions
262256
263- If you are fixing broken functionality in a [ PECL] ( https://pecl.php.net )
264- extension then create a bug or identify an existing bug at
265- [ bugs.php.net] ( https://bugs.php.net ) . A bug can be used to track the change
257+ If you are fixing broken functionality in a PHP extension then create a bug or
258+ identify an existing bug at GitHub. A bug can be used to track the change
266259progress and prevent your changes getting lost in the PHP mail archives. Some
267- PECL extensions have their own bug tracker locations and different contributing
260+ extensions have their own bug tracker locations and different contributing
268261procedures.
269262
270- If your change is large then create a
271- [ Request for Comments (RFC)] ( https://wiki.php.net/rfc ) , discuss it with the
272- extension maintainer, and discuss it on the development mailing list
273- pecl-dev@lists.php.net depending on the extension. PECL mailing list
274- subscription is explained on the
275- [ PECL support page] ( https://pecl.php.net/support.php ) .
276-
277- Update any open bugs and add a link to the source of your change. Send the patch
278- or pointer to the bug to pecl-dev@lists.php.net . Also CC the extension
279- maintainer. Explain what has been changed by your patch. Test scripts should be
280- included.
281-
282263## Checklist for submitting contribution
283264
284265- Read [ Coding standards] ( /CODING_STANDARDS.md ) before you start working.
0 commit comments