1
0
mirror of https://github.com/php/web-php.git synced 2026-03-23 23:02:13 +01:00
Files
archived-web-php/get-involved.php
Peter Cowburn 582c9e134d move sidebar links to main content for Get Involved page
Replaces the old sidebar with a ToC.

Original suggestion from Côme Chilliet:
    When I tried to get involved in PHP the first time, I got to
    https://php.net/get-involved.php, read the "Development of the
    PHP source" section and was like «Hum, ok, but where is the source?
    Why aren’t there any links here?». The stuff in the right column
    should really be in the middle and replaced with a Table of contents
    for consistency IMO.

Aside: the contents of this page could do with some love.
2019-02-05 20:03:17 +00:00

91 lines
3.3 KiB
PHP

<?php
$_SERVER['BASE_PAGE'] = 'get-involved.php';
include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc';
site_header("Get Involved", array("current" => "community"));
?>
<h2 class="content-title" id="contributing-to-php">Contributing to PHP</h2>
<div class="content-box">
<p>
Anybody who programs in PHP can be a contributing member of the community
that develops and deploys it; the task of deploying PHP, documentation and
associated websites is a never ending one. With every release, or release
candidate comes a wave of work, which takes a lot of organization and
co-ordination.
</p>
<p>
With the introduction of release managers comes a smoother release process,
but help is still needed: testing release candidates, finding and squashing
bugs in tests, documentation, and sources.
</p>
</div>
<h3 class="content-title" id="ways-to-contribute">Four Best Ways to Contribute</h3>
<ol class="content-box listed">
<li>Running test suites in <a href="http://qa.php.net/">RC</a>
and <a href="http://php.net/releases">release</a> distributions of PHP</li>
<li>Help finding and diagnosing failed tests, see
the <a href="http://qa.php.net/write-test.php">phpt documentation</a></li>
<li>Filing and resolving bug reports
at <a href="http://bugs.php.net">bugs.php.net</a></li>
<li>Help maintain and or translate documentation files
at <a href="http://edit.php.net">edit.php.net</a>. Check out our
<a href="http://doc.php.net/tutorial/">guide for contributors</a>.</li>
</ol>
<h3 class="content-header" id="php-src">Development of the PHP source</h3>
<div class="content-box">
<p>
Someone hoping to become involved in the maintenance and development of
the source should be experienced in all of the areas mentioned above, as
this creates a strong team; everyone knows how every other part of the
project works.
</p>
<p>
You will also need experience in C programming as PHP is written entirely in C.
</p>
</div>
<h3 class="content-title" id="references">Useful links for developers</h3>
<ul class="content-box listed">
<li><a href="https://wiki.php.net/rfc/howto">The RFC process</a> - the process
by which developers can suggest and discuss new ideas with the community</li>
<li><a href="/build-setup.php">Developer Setup Help</a> - some helpful information
regarding setting up a development environment for PHP</li>
<li><a href="/mailing-lists.php">Mailing List</a> - list of general and internal mailing lists
used by PHP</li>
</ul>
<?php
/*
XXX: lxr is offline and should be re-added once its are back online in a more permanent state (Kalle, 17/10/2017)
<li><a href="http://lxr.php.net">lxr</a> - an online interface to the
PHP source, providing search facilities useful for programmers and researchers</li>
*/
$SIDEBAR_DATA ='
<div class="panel">
<div class="headline">Table of Contents</div>
<div class="body">
<ul>
<li><a href="#contributing-to-php">Contributing to PHP</a></li>
<li><a href="#ways-to-contribute">Four Best Ways to Contribute</a></li>
<li><a href="#php-src">Development of the PHP source</a></li>
<li><a href="#references">Useful links for developers</a></li>
</ul>
</div>
</div>
';
site_footer(array('sidebar'=>$SIDEBAR_DATA));
/* vim: set et ts=4 sw=4 ft=php: : */