gwynne Mon, 13 Jul 2009 08:14:46 +0000
ViewVC URL: http://svn.php.net/viewvc?view=revision&revision=283997
Changed paths:
D web/php/trunk/anoncvs.php
A web/php/trunk/anonsvn.php
D web/php/trunk/cvs-php.php
U web/php/trunk/error.php
U web/php/trunk/include/languages.inc
U web/php/trunk/license/contrib-guidelines-code.php
U web/php/trunk/mirroring.php
U web/php/trunk/search.php
U web/php/trunk/sitemap.php
U web/php/trunk/sites.php
U web/php/trunk/source.php
A web/php/trunk/svn-php.php
U web/php/trunk/urlhowto.php
Log:
- Redirects from CVS pages to SVN pages
- CVS -> SVN in all affected pages
Most of this work was done by Shawn Stratton.
Deleted: web/php/trunk/anoncvs.php
===================================================================
--- web/php/trunk/anoncvs.php 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/anoncvs.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -1,183 +0,0 @@
-<?php
-// $Id$
-$_SERVER['BASE_PAGE'] = 'anoncvs.php';
-include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc';
-$SIDEBAR_DATA = '
-<h3>What is CVS?</h3>
-<p>
- You can find more information about CVS, and
- download clients for most major platforms, at
- <a href="http://ximbiot.com/cvs/wiki/";>the CVS Wiki</a>.
-</p>
-
-<h3>CVS mirroring</h3>
-<p>
- You can also mirror the PHP CVS repository using CVSup, see
- <a href="/cvsup.php">our CVSup page</a> for more details.
-</p>
-
-<h3>Contribute</h3>
-<p>
- If you would like to join PHP development or would like to
- contribute to the PHP documentation, contact the relevant
- group. You will need <a href="/cvs-php.php">your own CVS account</a>
- to contribute.
-</p>
-
-<h3>Source and binary snapshots</h3>
-<p>
- You may also be interested in a PHP snapshot, see
- <a href="http://snaps.php.net/";>snaps.php.net</a>.
- Compiled snapshots for Windows users are also included.
-</p>
-';
-site_header("Anonymous CVS Access");
-?>
-
-<h1>Anonymous CVS Access</h1>
-
-<p>
- If you wish to get the latest PHP source tree, you can obtain it
- through anonymous CVS. You should be warned that the CVS version
- is a development version, and as such, is often unstable, and may
- not even compile properly. The advantage of using CVS, though,
- is that you can get the latest fixes and updates, without having
- to wait for the official releases.
-</p>
-
-<p>
- PHP uses an advanced configuration system that requires you to have
- the following tools. Re2c is only necessary for developers and can be found
- <a href="http://re2c.org";>here</a>.
- All other utilities can be obtained from
- <a href="ftp://ftp.gnu.org/pub/gnu/";>the GNU FTP site</a>.
-</p>
-
-<ul>
- <li><i>autoconf</i>: 2.13</li>
- <li><i>automake</i>: 1.4+</li>
- <li><i>libtool</i>: 1.4.x+ (except 1.4.2)</li>
- <li><i>bison</i>: 1.28, 1.35, 1.75, 2.0 or higher</li>
- <li><i>flex</i>: 2.5.4 (<strong>not higher</strong>)</li>
- <li><i>re2c</i>: 0.9.11+ (0.12.0+ for HEAD)</li>
-</ul>
-
-<p>
- If you're experiencing problems, see also the section on
- <a href="#buildconf_fail">buildconf failures</a>.
-</p>
-
-<h2>Steps for using PHP from CVS</h2>
-<ol>
- <li>
- It is recommended that you configure CVS by putting this
- in your <code>~/.cvsrc</code> file:
-<pre>
-cvs -z3
-update -d -P
-checkout -P
-diff -u
-</pre>
- </li>
-
- <li>
- Log in to the PHP CVS server. We'll use the anonymous user
<strong>cvsread</strong>
- as the username, and use <strong>phpfi</strong> as the password:<br />
- <code>cvs -d :pserver:cvsr...@cvs.php.net:/repository login</code>
- </li>
-
- <li>
- Obtain the latest PHP source from CVS. There is a single <i>php-src</i>
- directory that contains all PHP branches. To get PHP from CVS,
- use the <i>"cvs checkout -r BRANCH"</i> notation. To checkout the
- latest, consider the following CVS commands:<br /><br />
- <strong>PHP 4.4</strong>:
- <code>cvs -d :pserver:cvsr...@cvs.php.net:/repository checkout -r PHP_4_4
php-src</code>
- <br />
- <strong>PHP 5.2</strong>:
- <code>cvs -d :pserver:cvsr...@cvs.php.net:/repository checkout -r PHP_5_2
php5</code>
- <br />
- <strong>PHP 5.3</strong>:
- <code>cvs -d :pserver:cvsr...@cvs.php.net:/repository checkout -r PHP_5_3
php5</code>
- <br />
- <strong>PHP 6</strong>:
- <code>cvs -d :pserver:cvsr...@cvs.php.net:/repository checkout php6</code>
- <br /><br />
- Some tips and notes:
- <br />
- <div class="tip">
- <p>You may retrieve a specific release of PHP from CVS by using the
- <i>-r</i> flag in your cvs command. Some examples:<br />
- <code>cvs -d :pserver:cvsr...@cvs.php.net:/repository checkout -r php_4_2_1
php-src</code><br />
- <code>cvs -d :pserver:cvsr...@cvs.php.net:/repository checkout -r php_4_3_2
php-src</code></p>
- </div>
- <ul>
- <li>
- The branch names can also be used for cvs diff and merge operations.
- </li>
- <li>
- You can also specify the directory name, for example, to put PHP 6 HEAD
into a directory
- named php6dev:<br />
- <code>cvs -d :pserver:cvsr...@cvs.php.net:/repository checkout -d php6dev
php6</code>
- </li>
- </ul>
- </li>
-
- <li>
- Make sure you have autoconf 2.13 or newer, automake 1.4 or newer and libtool
- 1.4.
- <div class="tip" style="margin: 10px 0 10px 20px;">
- <p>Note that certain combinations of autoconf, automake and libtool may not
- work when used together. See <a href="#buildconf_fail">below</a> for
- details.<br />
- Also, certain versions of autoconf may generate warnings of
<code>AC_PROG_CPP
- called before AC_PROG_CC</code>. These messages can usually be ignored.</p>
- </div>
- </li>
-
- <li>
- Run <code>./buildconf</code>. After a while, the configure script should be
generated.
- </li>
-
- <li>
- From this point onwards, installation is similar to the installation of one
of
- the official packages with one main difference – you must have bison
1.28 or later
- and flex 2.5.4 to compile, because the pre-generated scanner and parser
- files are not included in CVS.
- </li>
-</ol>
-
-<p>
- There are also other things, like the XML source code
- for the documentation, available via anonymous CVS. See
- <a href="http://cvs.php.net/";>the web-based view of the CVS
- server</a> to see what is available. For example, to checkout the
- latest english version of the PHP manual:<br />
- <code>cvs -d :pserver:cvsr...@cvs.php.net:/repository checkout phpdoc</code>
-</p>
-
-<a name="buildconf_fail"></a>
-<h2>autoconf, automake and libtool information</h2>
-
-<p>
- There seem to be problems with libtool 1.4.2. It is suggested
- that you use libtool 1.4, along with autoconf 2.13 and
- automake 1.4. You should also ensure that autoconf, automake
- and libtool are installed in the same directory. libtool 1.5
- will not work.
-</p>
-
-<p>The following combinations are known to work:</p>
-<ul>
- <li>autoconf 2.13, automake 1.4 and libtool 1.4.3</li>
- <li>autoconf 2.13, automake 1.5 and libtool 1.4.3</li>
-</ul>
-
-<a name="flex_fail"></a>
-<h2>Zend/zend_language_scanner.c: No such file or directory</h2>
-
-<p>
- PHP only supports flex 2.5.4, <strong>not</strong> later versions as they
broke backwards compatibility
-</p>
-
-<?php site_footer(); ?>
Added: web/php/trunk/anonsvn.php
===================================================================
--- web/php/trunk/anonsvn.php (rev 0)
+++ web/php/trunk/anonsvn.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -0,0 +1,153 @@
+<?php
+// $Id$
+$_SERVER['BASE_PAGE'] = 'anonsvn.php';
+include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc';
+$SIDEBAR_DATA = '
+<h3>What is SVN?</h3>
+<p>
+ You can find more information about SVN, and
+ download clients for most major platforms, at
+ <a href="http://subversion.tigris.org";>the official SVN site</a>.
+</p>
+
+
+<h3>Contribute</h3>
+<p>
+ If you would like to join PHP development or would like to
+ contribute to the PHP documentation, contact the relevant
+ group. You will need <a href="/svn-php.php">your own SVN account</a>
+ to contribute.
+</p>
+
+<h3>Source and binary snapshots</h3>
+<p>
+ You may also be interested in a PHP snapshot, see
+ <a href="http://snaps.php.net/";>snaps.php.net</a>.
+ Compiled snapshots for Windows users are also included.
+</p>
+';
+site_header("SVN Access");
+?>
+
+<h1>SVN Access</h1>
+
+<p>
+ If you wish to get the latest PHP source tree, you can obtain it
+ through SVN. You should be warned that the SVN version
+ is a development version, and as such, is often unstable, and may
+ not even compile properly. The advantage of using SVN, though,
+ is that you can get the latest fixes and updates, without having
+ to wait for the official releases.
+</p>
+
+<p>
+ PHP uses an advanced configuration system that requires you to have
+ the following tools. re2c is only necessary for developers and can be found
+ <a href="http://re2c.org";>here</a>.
+ All other utilities can be obtained from
+ <a href="ftp://ftp.gnu.org/pub/gnu/";>the GNU FTP site</a>.
+</p>
+
+<ul>
+ <li><i>autoconf</i>: 2.13</li>
+ <li><i>automake</i>: 1.4+</li>
+ <li><i>libtool</i>: 1.4.x+ (except 1.4.2)</li>
+ <li><i>bison</i>: 1.28, 1.35, 1.75, 2.0 or higher</li>
+ <li><i>flex (PHP 5.2 and earlier)</i>: 2.5.4 (<strong>not
higher</strong>)</li>
+ <li><i>re2c</i>: 0.13.4+</li>
+</ul>
+
+<p>
+ If you're experiencing problems, see also the section on
+ <a href="#buildconf_fail">buildconf failures</a>.
+</p>
+
+<h2>Steps for using PHP from SVN</h2>
+<ol>
+
+ <li>
+ Obtain the latest PHP source from SVN. There is a single <i>php-src</i>
+ directory that contains all PHP branches and tags. To get PHP from SVN,
+ use the <i>"svn checkout
http://svn.php.net/repository/php/php-src/branches/BRANCH";</i> notation. To
checkout the
+ latest, consider the following SVN commands:<br /><br />
+ <strong>PHP 5.2</strong>:
+ <code>svn checkout
http://svn.php.net/repository/php/php-src/branches/PHP_5_2 php-src-5.2</code>
+ <br />
+ <strong>PHP 5.3</strong>:
+ <code>svn checkout
http://svn.php.net/repository/php/php-src/branches/PHP_5_3 php-src-5.3</code>
+ <br />
+ <strong>PHP 6</strong>:
+ <code>svn checkout http://svn.php.net/repository/php/php-src/trunk
php-src</code>
+ <br /><br />
+ The branch names can also be used for SVN diff and merge operations.
+ </li>
+
+ <li>
+ Make sure you have autoconf 2.13 or newer, automake 1.4 or newer and libtool
+ 1.4.
+ <div class="tip" style="margin: 10px 0 10px 20px;">
+ <p>Note that certain combinations of autoconf, automake and libtool may not
+ work when used together. See <a href="#buildconf_fail">below</a> for
+ details.<br />
+ Also, certain versions of autoconf may generate warnings of
<code>AC_PROG_CPP
+ called before AC_PROG_CC</code>. These messages can usually be ignored.</p>
+ </div>
+ </li>
+
+ <li>
+ Run <code>./buildconf</code> to generate the configure script. This may take
several moments.
+ </li>
+
+ <li>
+ From this point onwards, installation is similar to the installation of one
of
+ the official packages with one main difference – you may need bison
1.28 or later
+ and flex 2.5.4 (PHP 5.2 and earlier) or re2c 0.13.4+ or later (PHP 5.3 and
later) to
+ compile, because the pre-generated scanner and parser files may not
+ be included in SVN.
+ </li>
+</ol>
+
+<p>
+ There are many other things, such as the XML source code
+ for the documentation, available via SVN. See
+ <a href="http://svn.php.net/";>the web-based view of the SVN
+ server</a> to see what is available. For example, to checkout the
+ latest english version of the PHP manual:<br />
+ <code>svn checkout http://svn.php.net/repository/phpdoc/en/trunk
./phpdoc-en</code>
+</p>
+
+<a name="buildconf_fail"></a>
+<h2>autoconf, automake and libtool information</h2>
+
+<p>
+ There seem to be problems with libtool 1.4.2. It is suggested
+ that you use libtool 1.4, along with autoconf 2.13 and
+ automake 1.4. You should also ensure that autoconf, automake
+ and libtool are installed in the same directory. libtool 1.5
+ will not work.
+</p>
+
+<p>The following combinations are known to work:</p>
+<ul>
+ <li>autoconf 2.13, automake 1.4 and libtool 1.4.3</li>
+ <li>autoconf 2.13, automake 1.5 and libtool 1.4.3</li>
+ <li>autoconf 2.63, automake 1.11 and libtool 2.2.6 (with many warnings)</li>
+</ul>
+
+<p>
+ If you have multiple versions of autoconf installed on your computer, as is
+ common for many UNIXes, you can set the PHP_AUTOCONF and PHP_AUTOHEADER
+ variables when running buildconf to indicate which versions it should use
+ e.g.:<br />
+ <code>PHP_AUTOCONF=autoconf213 PHP_AUTOHEADER=autoheader213 ./buildconf</code>
+</p>
+
+<a name="flex_fail"></a>
+<h2>Zend/zend_language_scanner.c: No such file or directory</h2>
+
+<p>
+ PHP only supports flex 2.5.4, <strong>not</strong> later versions as they
broke backwards compatibility.
+ Please note that PHP 5.3 and later do not require flex at all.
+</p>
+
+<?php site_footer(); ?>
Property changes on: web/php/trunk/anonsvn.php
___________________________________________________________________
Added: svn:keywords
+ Id Rev
Added: svn:eol-style
+ native
Deleted: web/php/trunk/cvs-php.php
===================================================================
--- web/php/trunk/cvs-php.php 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/cvs-php.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -1,408 +0,0 @@
-<?php
-// $Id$
-$_SERVER['BASE_PAGE'] = 'cvs-php.php';
-include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc';
-include_once $_SERVER['DOCUMENT_ROOT'] . '/include/email-validation.inc';
-include_once $_SERVER['DOCUMENT_ROOT'] . '/include/posttohost.inc';
-
-$SIDEBAR_DATA = '
-<h3>More about CVS</h3>
-<p>
- You can find more information about CVS, and
- download clients for most major platforms, at
- <a href="http://ximbiot.com/cvs/wiki/index.php";>the CVS Wiki</a>.
-</p>
-
-<h3>Anonymous CVS access</h3>
-<p>
- If you would like to grab PHP sources or other PHP.net
- hosted project data from PHP.net, you can also use
- <a href="/anoncvs.php">anonymous CVS</a>.
-</p>
-';
-site_header("Using CVS for PHP Development");
-
-$groups = array(
- "php" => "PHP Group",
- "pear" => "PEAR Group",
- "pecl" => "PECL Group",
- "doc" => "Doc Group",
-);
-
-?>
-
-<h1>Using CVS for PHP Development</h1>
-
-<?php
-
-// We have a form submitted, and the user have read all the comments
-if (count($_POST) && (!is_array($_POST['purpose']) ||
!count($_POST['purpose']))) {
- // Clean up incoming POST vars
- if (get_magic_quotes_gpc()) {
- foreach ($_POST as $k => $v) {
- $cleaned[$k] = stripslashes($v);
- }
- }
- else {
- $cleaned = $_POST;
- }
-
- // No error found yet
- $error = "";
-
- // Check for errors
- if (empty($_POST['id'])) {
- $error .= "You must supply a desired CVS id. ";
- } elseif(!preg_match('!^[a-z]\w+$!', $_POST['id'])) {
- $error .= "Your user id must be >1 char long, start with ".
- "a letter and contain nothing but a-z or 0-9 and _";
- }
- if (empty($_POST['fullname'])) {
- $error .= "You must supply your real name. ";
- }
- if (empty($_POST['realpurpose'])) {
- $error .= "You must supply a reason for requesting the CVS account. ";
- }
- if (empty($_POST['password'])) {
- $error .= "You must supply a desired password. ";
- }
- if (empty($_POST['email']) || !is_emailable_address($cleaned['email'])) {
- $error .= "You must supply a proper email address. ";
- }
- if (empty($_POST['yesno']) || $_POST['yesno'] != 'yes') {
- $error .= "You did not fill the form out correctly. ";
- }
- if (empty($_POST['group']) || !isset($groups[$_POST['group']])) {
- $error .= "You did not fill out where to send the request. ";
- }
- if (!isset($_POST['guidelines']) || !$_POST['guidelines']) {
- $error .= "You did not agree to follow the contribution guidelines. ";
- }
-
- // Post the request if there is no error
- if (!$error) {
- $error = posttohost(
- "http://master.php.net/entry/cvs-account.php";,
- array(
- "username" => $cleaned['id'],
- "name" => $cleaned['fullname'],
- "email" => $cleaned['email'],
- "passwd" => $cleaned['password'],
- "note" => $cleaned['realpurpose'],
- "yesno" => $cleaned['yesno'],
- "group" => $cleaned['group'],
- )
- );
- // Error while posting
- if ($error) {
- $error = "An error occured when trying to create the account:
$error.";
- }
- }
-
- // Some error was found, while checking or submitting the data
- if ($error) {
- echo "<p class=\"formerror\">$error</p>";
- }
- else {
-?>
-<p>
- Thank you. Your request has been sent. You should hear something within the
- next week or so. If you haven't heard anything by around <i><?php echo
date('r', time()+604800) ?></i>
- then please send an email to the appropriate <a
href="/mailing-lists.php">mailing list</a>:
-</p>
-<ul>
- <li>Internals: <a
href="mailto:intern...@lists.php.net";>intern...@lists.php.net</a></li>
- <li>Documentation: <a
href="mailto:php...@lists.php.net";>php...@lists.php.net</a></li>
- <li>PECL: <a
href="mailto:pecl-...@lists.php.net";>pecl-...@lists.php.net</a></li>
- <li>PEAR: <a
href="mailto:pear-...@lists.php.net";>pear-...@lists.php.net</a></li>
- <li>Other: <a href="mailto:gr...@php.net";>gr...@php.net</a></li>
-</ul>
-<p>
- This is to let us know that we've
- forgotten you, but you haven't forgotten us! It happens. There's several of
- us, and sometimes we think that someone else has taken care of your request,
- and they think that we took care of it. Sorry. You can also speed up the
- process by having an existing CVS account holder who works in the area you are
- interested in mail us to vouch for you.
-</p>
-
-<p>
- If you are not familiar with CVS, you should have a look at the various
- documentation resources available in <a
- href="http://ximbiot.com/cvs/wiki/index.php";>the CVS Wiki</a>. This is
- also where to get the most recent version of the CVS client.
-</p>
-
-<p>
- All CVS commit messages to the PHP sources get sent to the php-cvs mailing
list.
- You should subscribe yourself to this mailing list. Instructions for
subscribing
- are on the <a href="/mailing-lists.php">Mailing Lists</a> page.
-</p>
-
-<p>
- CVS itself is quite easy to use. You will not be able to check out your
- own copy of the CVS tree, until you receive confirmation of your account
- having been created. After that, you can follow the steps listed on the
- <a href="/anoncvs.php">anonymous CVS</a> page for checking out your tree.
- Substitute your own user name for 'cvsread' and use the password you
- submitted.
-</p>
-
-<p>
- Next, once you have your CVS tree you need to know the following commands.
- They should all be executed from within the checked out tree. eg.
- <tt>cd php-src</tt>.
-</p>
-
-<dl>
- <dt><strong><tt>cvs update -dP</tt></strong></dt>
- <dd>
- This fetches all updates made by others and brings your tree up to date.
- Before starting to edit anything in the tree you should do this. Generally
- you would do this whenever you see a CVS commit message on the php-cvs
- mailing list.</dd>
- <dt><strong><tt>cvs commit</tt></strong></dt>
- <dd>
- This commits any changes you have made anywhere in the tree. A text
- editor will pop up and you will need to describe the changes you made.
- Please provide a good description here as it may help people in the
- future when looking at your code changes.
- </dd>
-</dl>
-<?php
- site_footer();
- exit;
- } // endif: no error found
-} // endif: no data or checkread not checked
-
-else {
- if (count($_POST)) {
- print <<<EOT
-<p class="formerror">
- We could not have said it more clearly. Read everything on
- this page and look at the form you are submitting carefully.
-</p>
-EOT;
- }
-?>
-
-<p>
- All PHP development is done through a distributed revision control system
- called CVS. This helps us track changes and it makes it possible for people
- located in all corners of the world to collaborate on a project without
- having to worry about stepping on each others' toes.
-</p>
-
-<p>
- Please note that you do <strong>not</strong> need a CVS account to <a
- href="/anoncvs.php"><strong>access</strong> the CVS tree</a>, to use PHP,
- or to write PHP scripts. You only need a CVS account if you will be a
- regular contributor to the development of PHP itself.
-</p>
-
-<p>
- And once again since people just don't seem to understand this point:
-</p>
-
-<table border="0" cellpadding="3" class="standard">
- <tr>
- <th>Does Not Require CVS Account</th>
- <th>Requires CVS Account</th>
- </tr>
- <tr>
- <td class="sub">Learning PHP</td>
- <td>Developing the PHP runtime</td>
- </tr>
- <tr>
- <td class="sub">Coding in PHP</td>
- <td>Maintaining an official, bundled PHP extension</td>
- </tr>
- <tr>
- <td class="sub">Reading the PHP source</td>
- <td><a href="/dochowto">Maintaining the documentation</a></td>
- </tr>
- <tr>
- <td class="sub">Using PHP extensions</td>
- <td><a href="/dochowto">Translating the documentation</a></td>
- </tr>
- <tr>
- <td class="sub">Creating experimental PHP extensions</td>
- <td>Maintaining www.php.net</td>
- </tr>
- <tr>
- <td class="sub">Submitting a patch to PHP</td>
- <td> </td>
- </tr>
- <tr>
- <td class="sub">Adding notes to the documentation</td>
- <td> </td>
- </tr>
- <tr>
- <td class="sub">Writing web pages with PHP</td>
- <td> </td>
- </tr>
- <tr>
- <td class="sub">Setting up a php.net mirror site</td>
- <td> </td>
- </tr>
-</table>
-
-<p>
- If you are contributing a patch, a small fix, or another minor change you do
- not need to ask for a CVS account before submitting it. Just send your patch
to
- <a href="mailto:intern...@lists.php.net";>the internals mailing list</a>. You
- should <a href="mailto:internals-subscr...@lists.php.net";>subscribe to that
- list</a> to participate in any discussion your patch generates! Your patch may
- not get noticed the first time. Make sure that when you send your patch, you
- explain what it does. Make sure you use a clear subject when sending your
- patch (you might even want to prefix it with <tt>"[PATCH]"</tt>). If nobody
- seems to take notice after a few days, you might want to try resubmitting it.
- Your original message might have gotten missed because of another heated
- discussion.
-</p>
-
-<p>
- Submitting patches and participating in the discussion on the 'internals' list
- <strong>before</strong> requesting full CVS access is strongly suggested, so
- the PHP development team can get to know you and what you'll be contributing.
- It is suggested that all PHP developers (<strong>people developing PHP
- itself</strong>, not people developing in PHP) subscribe to this list.
- Similarly, if you plan on contributing documentation, you should
- <a href="mailto:phpdoc-subscr...@lists.php.net";>subscribe to the
- documentation mailing list</a>, and read the <a href="/dochowto">PHP
- Documentation HOWTO</a>.
-</p>
-
-<p>
- If you wish to contribute to the documentation please contact the translation
- team for the language you wish to help with. If you have trouble finding the
- team, ask on the phpdoc mailing list. Once you have made contact you may
- apply for a CVS account here by including the name of one or more people from
- the existing translation team that referred you and of course the language
- you wish to translate to.
-</p>
-
-<p>
- If you have a new PEAR package you wish to contribute, propose it
- through the PEPR system on the PEAR website. If you have a new PECL
- extension you wish to contribute, bring it up on the appropriate PECL
- mailing list first.
- <br />
- Once your PEAR package has been approved, or you get the sense that
- people generally agree that your PECL contribution is worthwhile, you
- may apply for a CVS account here. Specify the name of your PEAR package
- or PECL contribution (single word CVS module name) and also reference an
- existing account holder who can vouch for your contribution, or provide
- a link to your PEAR proposal.
-</p>
-
-<p>
- Okay, if you are still reading, then you may actually need a CVS account.
- This is <strong>not</strong> an automatic process. Fill in the form below to
- request an account. In the box next to "Purpose", describe what it is that
- you intend to do with CVS access. If it isn't clear from what you've
- described already, tell us what parts of the CVS repository you need access
- to (for example, "phpdoc" is the documentation tree, "php-src/ext/readline"
- is the PHP readline extension). If someone told you to fill out the form
- here, make sure to mention them here!
-</p>
-
-<p>
- The CVS account, once granted and activated (which could take a while, so be
- patient!), gives you access to a number of things. First, and most
- importantly, it gives you access to modify those parts of the PHP CVS tree for
- which you have requested and been granted access. It also allows you to
comment
- on and close bugs in our <a href="http://bugs.php.net/";>bug database</a>, and
- allows you to modify the documentation notes in the <a
href="/manual/">annotated
- manual</a>. Your CVS account also translates into a f...@php.net forwarding
email
- address where <strong>foo</strong> is your CVS user id. Feel free to use it!
-</p>
-
-<h2>Request a CVS account</h2>
-
-<p class="warn">
- Please note that you do <em>NOT</em> need a CVS account to study PHP. You do
- <em>NOT</em> need a CVS account to learn PHP, to use PHP or to in any way do
- anything at all with PHP. If you are sitting there wondering if you need a
- CVS account, then you don't! If an existing CVS account holder suggested you
- request an account, please mention their CVS id in the request.
-</p>
-<p class="warn">
- Also note that information provided here will be sent to a public
- mailing list.
-</p>
-
-<?php
-} // endif: no data submitted
-
-?>
-<form action="/cvs-php.php" method="post">
-<table border="0" class="standard" style="width: 80%;">
-<tr>
- <th class="subr">Full Name:</th>
- <td><input type="text" size="50" name="fullname"
- class="max" value="<?php if (isset($_POST['fullname'])) echo
clean($_POST['fullname']);?>" /></td>
-</tr>
-<tr>
- <th class="subr">Email:</th>
- <td><input type="text" size="50" name="email"
- class="max" value="<?php if (isset($_POST['email'])) echo
clean($_POST['email']);?>" /></td>
-</tr>
-<tr>
- <th class="subr">For what purpose do you require a CVS account:<br />
- (check all that apply)</th>
- <td>
-<?php
-$purposes = array("Learning PHP", "Coding in PHP", "Reading the PHP source",
- "Using PHP extensions", "Creating experimental PHP extensions",
- "Submitting a patch to PHP", "Adding notes to the documentation",
- "Writing web pages with PHP", "Setting up a php.net mirror site");
-
-foreach ($purposes as $i => $p) { ?>
- <input type="checkbox" name="purpose[<?php echo $i?>]" value="1"
- checked="checked" /><?php echo $p; ?><br />
-<?php } ?>
- </td>
-</tr>
-<tr>
- <th class="subr">If your intended purpose is not in the list, <br />please
state it here:</th>
- <td><textarea cols="50" rows="5" name="realpurpose" class="max"><?php if
(isset($_POST['realpurpose'])) echo
clean($_POST['realpurpose']);?></textarea></td>
-</tr>
-<tr>
-<th class="subr">Do you agree to follow the <a
href="license/contrib-guidelines-code.php">contribution guidelines</a>?</th>
-<td><input type="checkbox" name="guidelines" value="1" />Check the box if you
agree.</td>
-</tr>
-<tr>
- <th class="subr">User ID:<br /> <small>(single word, lower case)</small></th>
- <td><input type="text" size="10" name="id"
- class="max" value="<?php if (isset($_POST['id'])) echo
clean($_POST['id']);?>" /></td>
-</tr>
-<tr>
- <th class="subr">Requested Password:</th>
- <td><input type="password" size="10" name="password"
- class="max" value="<?php if (isset($_POST['password'])) echo
clean($_POST['password']);?>" /></td>
-</tr>
-<tr>
- <th class="subr">Did you fill this form out correctly (yes/no)?</th>
- <td><input type="text" size="10" name="yesno" class="max" value="no" /></td>
-</tr>
-<tr>
- <th>Type of initial karma (who to send this request to):</th>
- <td>
- <select name="group">
-<?php
-foreach($groups as $group => $name) {
- $selected = (isset($_POST["group"]) && $_POST["group"] == $group) ? '
selected="selected"' : '';
- echo "<option value='$group'$selected>$name</option>\n";
-}
-?>
- </select>
- </td>
-</tr>
-<tr>
- <th colspan="2"><input type="submit" value="Send Request" /></th>
-</tr>
-</table>
-</form>
-
-<?php site_footer();
Modified: web/php/trunk/error.php
===================================================================
--- web/php/trunk/error.php 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/error.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -386,6 +386,10 @@
# external shortcut aliases ;)
"dochowto" => "phpdochowto",
"projects.php" => "projects", // BC
+
+ # CVS -> SVN
+ "anoncvs.php" => "anonsvn",
+ "cvs-php.php" => "svn-php",
);
$external_redirects = array(
Modified: web/php/trunk/include/languages.inc
===================================================================
--- web/php/trunk/include/languages.inc 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/include/languages.inc 2009-07-13 08:14:46 UTC (rev 283997)
@@ -4,7 +4,7 @@
/*
This is a list of all manual languages hosted
- within PHP CVS modules (phpdoc-{lang})
+ within PHP SVN modules (phpdoc-{lang})
Some codes, like "kr", "tw" and "hk" are not in
conformance with the official language code standard!
Modified: web/php/trunk/license/contrib-guidelines-code.php
===================================================================
--- web/php/trunk/license/contrib-guidelines-code.php 2009-07-13 06:42:59 UTC
(rev 283996)
+++ web/php/trunk/license/contrib-guidelines-code.php 2009-07-13 08:14:46 UTC
(rev 283997)
@@ -7,7 +7,7 @@
<h2>PHP Contributor Guidelines for Code Developers</h2>
<p>
- Before you complete the form to request a CVS id, you must understand and
accept the principles under which PHP
+ Before you complete the form to request a SVN account, you must understand
and accept the principles under which PHP
itself is developed. These are summarised in the next paragraph.
</p>
<p>
Modified: web/php/trunk/mirroring.php
===================================================================
--- web/php/trunk/mirroring.php 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/mirroring.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -8,15 +8,17 @@
Properly working mirror sites are listed on <a href="/mirrors.php">our
mirrors page</a>.
</p>
-
-<h3>CVS repository mirroring</h3>
+';
+/*
+<h3>SVN repository mirroring</h3>
<p>
If you are interested in using a local copy of our
- CVS repository for yourself, we provide
- <a href="/cvsup.php">CVSUp instructions</a>
+ SVN repository for yourself, we provide
+ <a href="/svnsync.php">svnsync instructions</a>
separately.
</p>
';
+*/
site_header("Mirroring The PHP Website");
Modified: web/php/trunk/search.php
===================================================================
--- web/php/trunk/search.php 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/search.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -125,8 +125,8 @@
In case you find any bugs, <a href="http://bugs.php.net/";>we are
interested</a>
in a detailed writeup, including JS error messages, operating system and
browser
information. The source code of this feature is released under the PHP
License and
- is available <a
href="http://cvs.php.net/cvs.php/phpdoc/scripts/quickref";>from the
- PHP CVS server</a> without any support.
+ is available <a
href="http://svn.php.net/phpdoc/doc-base/trunk/scripts/quickref";>from the
+ PHP SVN server</a> without any support.
</p>
<?php
if (FALSE) {
Modified: web/php/trunk/sitemap.php
===================================================================
--- web/php/trunk/sitemap.php 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/sitemap.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -76,12 +76,12 @@
<li><a href="/sites.php">PHP.net Sites List</a></li>
</ul>
-<h2>CVS instructions</h2>
+<h2>SVN instructions</h2>
<ul>
- <li><a href="/anoncvs.php">Getting PHP from CVS</a></li>
- <li><a href="/cvs-php.php">Using CVS for PHP Development</a></li>
- <li><a href="/cvsup.php">Maintaining a Local CVS Repository</a></li>
+ <li><a href="/svn.php">Getting PHP from SVN</a></li>
+ <li><a href="/svn-php.php">Using SVN for PHP Development</a></li>
+<!-- <li><a href="/svnsync.php">Maintaining a Local SVN Repository</a></li> -->
</ul>
<h2>Mirror sites</h2>
Modified: web/php/trunk/sites.php
===================================================================
--- web/php/trunk/sites.php 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/sites.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -163,16 +163,24 @@
process.
</p>
-<h2><a href="http://cvs.php.net/viewvc.cgi/";>cvs.php.net</a>: CVS
Repository</h2>
+<h2><a href="http://svn.php.net/";>svn.php.net</a>: SVN Repository</h2>
<p>
- The PHP project is organized with a CVS server, and this website is the web
+ The PHP project is organized with a SVN server, and this website is the web
interface to it. There you can browse the history (and latest versions) of the
source code for all of the PHP projects. For example, the <a
- href="http://cvs.php.net/viewvc.cgi/php-src/";>php-src</a> module is the
+ href="http://svn.php.net/php/php-src/";>php-src</a> module is the
repository for the source code to the latest version of PHP itself.
</p>
+<h2><a href="http://cvs.php.net/";>cvs.php.net</a>: Archived CVS Repository</h2>
+
+<p>
+ The PHP project used to be organized under the CVS revision control system,
but
+ migrated to Subversion (see above) in July of 2009. The old CVS repository is
+ archived here for posterity.
+</p>
+
<h2><a href="http://lxr.php.net/";>lxr.php.net</a>: Cross Reference</h2>
<p>
@@ -204,7 +212,7 @@
<p>
This site is dedicated to automatic PHP code coverage testing. On a regular
- basis current CVS snapshots are being build and tested on this machine. After
+ basis current SVN snapshots are being build and tested on this machine. After
all tests are done the results are visualized along with a code coverage
analysis.
</p>
Modified: web/php/trunk/source.php
===================================================================
--- web/php/trunk/source.php 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/source.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -28,8 +28,8 @@
<p>
Of course, if you want to see the <a href="/source.php?url=/source.php">source
of this page</a>, we have it available.
- You can also browse the CVS repository for this website on
- <a href="http://cvs.php.net/viewvc.cgi/phpweb/";>cvs.php.net</a>.
+ You can also browse the SVN repository for this website on
+ <a href="http://svn.php.net/web/php/";>svn.php.net</a>.
</p>
';
site_header("Show Source");
Added: web/php/trunk/svn-php.php
===================================================================
--- web/php/trunk/svn-php.php (rev 0)
+++ web/php/trunk/svn-php.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -0,0 +1,414 @@
+<?php
+// $Id$
+$_SERVER['BASE_PAGE'] = 'svn-php.php';
+include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc';
+include_once $_SERVER['DOCUMENT_ROOT'] . '/include/email-validation.inc';
+include_once $_SERVER['DOCUMENT_ROOT'] . '/include/posttohost.inc';
+
+$SIDEBAR_DATA = '
+<h3>More about SVN</h3>
+<p>
+ You can find more information about SVN, and
+ download clients for most major platforms, at
+ <a href="http://subversion.tigris.org/";>the official SVN site</a>.
+</p>
+
+<h3>Anonymous SVN access</h3>
+<p>
+ If you would like to grab PHP sources or other PHP.net
+ hosted project data from PHP.net, you can also use
+ <a href="/svn.php">anonymous SVN</a>.
+</p>
+';
+site_header("Using SVN for PHP Development");
+
+$groups = array(
+ "php" => "PHP Group",
+ "pear" => "PEAR Group",
+ "pecl" => "PECL Group",
+ "doc" => "Doc Group",
+);
+
+?>
+
+<h1>Using SVN for PHP Development</h1>
+
+<?php
+
+// We have a form submitted, and the user have read all the comments
+if (count($_POST) && (!isset($_POST['purpose']) ||
!is_array($_POST['purpose']) || !count($_POST['purpose']))) {
+ // Clean up incoming POST vars
+ if (function_exists('get_magic_quotes_gpc') && @get_magic_quotes_gpc()) {
+ foreach ($_POST as $k => $v) {
+ $cleaned[$k] = stripslashes($v);
+ }
+ }
+ else {
+ $cleaned = $_POST;
+ }
+
+ // No error found yet
+ $error = "";
+
+ // Check for errors
+ if (empty($_POST['id'])) {
+ $error .= "You must supply a desired SVN user id. <br />";
+ } elseif(!preg_match('!^[a-z]\w+$!', $_POST['id'])) {
+ $error .= "Your user id must be >1 char long, start with ".
+ "a letter and contain nothing but a-z, 0-9, and _ <br />";
+ }
+ if (empty($_POST['fullname'])) {
+ $error .= "You must supply your real name. <br />";
+ }
+ if (empty($_POST['realpurpose'])) {
+ $error .= "You must supply a reason for requesting the SVN account.
<br />";
+ }
+ if (empty($_POST['password'])) {
+ $error .= "You must supply a desired password. <br />";
+ }
+ if (empty($_POST['email']) || !is_emailable_address($cleaned['email'])) {
+ $error .= "You must supply a proper email address. <br />";
+ }
+ if (empty($_POST['yesno']) || $_POST['yesno'] != 'yes') {
+ $error .= "You did not fill the form out correctly. <br />";
+ }
+ if (empty($_POST['group']) || !isset($groups[$_POST['group']])) {
+ $error .= "You did not fill out where to send the request. <br />";
+ }
+ if (!isset($_POST['guidelines']) || !$_POST['guidelines']) {
+ $error .= "You did not agree to follow the contribution guidelines.
<br />";
+ }
+
+ // Post the request if there is no error
+ if (!$error) {
+ $error = posttohost(
+ "http://master.php.net/entry/svn-account.php";,
+ array(
+ "username" => $cleaned['id'],
+ "name" => $cleaned['fullname'],
+ "email" => $cleaned['email'],
+ "passwd" => $cleaned['password'],
+ "note" => $cleaned['realpurpose'],
+ "yesno" => $cleaned['yesno'],
+ "group" => $cleaned['group'],
+ )
+ );
+ // Error while posting
+ if ($error) {
+ $error = "An error occured when trying to create the account:
$error.";
+ }
+ }
+
+ // Some error was found, while checking or submitting the data
+ if ($error) {
+ echo "<p class=\"formerror\">$error</p>";
+ }
+ else {
+?>
+<p>
+ Thank you. Your request has been sent. You should hear something within the
+ next week or so. If you haven't heard anything by around <?php echo date('l,
F jS', time()+604800); ?>
+ then please send an email to the appropriate <a
href="/mailing-lists.php">mailing list</a>:
+</p>
+<ul>
+ <li>Internals: <a
href="mailto:intern...@lists.php.net";>intern...@lists.php.net</a></li>
+ <li>Documentation: <a
href="mailto:php...@lists.php.net";>php...@lists.php.net</a></li>
+ <li>PECL: <a
href="mailto:pecl-...@lists.php.net";>pecl-...@lists.php.net</a></li>
+ <li>PEAR: <a
href="mailto:pear-...@lists.php.net";>pear-...@lists.php.net</a></li>
+ <li>Other: <a href="mailto:gr...@php.net";>gr...@php.net</a></li>
+</ul>
+<p>
+ This is to let us know that we've
+ forgotten you, but you haven't forgotten us! It happens. There's several of
+ us, and sometimes we think that someone else has taken care of your request,
+ and they think that we took care of it. Sorry. You can also speed up the
+ process by having an existing SVN account holder who works in the area you are
+ interested in mail us to vouch for you.
+</p>
+
+<p>
+ If you are not familiar with SVN, you should have a look at the various
+ documentation resources available in <a
+ href="http://subversion.tigris.org/";>the official SVN site</a>. This is
+ also where to get the most recent version of the SVN client.
+</p>
+
+<p>
+ All SVN commit messages to the PHP sources get sent to the php-svn mailing
lists.
+ You should subscribe yourself to one or more of these mailing lists.
Instructions
+ for subscribing are on the <a href="/mailing-lists.php">Mailing Lists</a>
page.
+</p>
+
+<p>
+ SVN itself is quite easy to use. You can follow the steps listed on the
+ <a href="/svn.php">anonymous SVN</a> page for checking out your tree.
+ Please note that you do not have to log in to check out your tree; you will
+ not be asked for your username and password until you attempt to commit
changes.
+</p>
+
+<p>
+ Next, once you have your SVN tree you need to know the following commands.
+ They should all be executed from within the checked out tree. eg.
+ <tt>cd php-src</tt>.
+</p>
+
+<dl>
+ <dt><strong><tt>svn update</tt></strong></dt>
+ <dd>
+ This fetches all updates made by others and brings your tree up to date.
+ Before starting to edit anything in the tree you should do this. Generally
+ you would do this whenever you see a SVN commit message on the php-SVN
+ mailing list.</dd>
+ <dt><strong><tt>svn diff</tt></strong></dt>
+ <dd>
+ This displays all changes you have made anywhere in the tree in
+ <a href="http://en.wikipedia.org/wiki/Unified_diff";>unified diff</a> format.
+ This is a very good (and strongly recommended) way to review your changes
+ before you decide to commit them.
+ </dd>
+ <dt><strong><tt>svn commit</tt></strong></dt>
+ <dd>
+ This commits any changes you have made anywhere in the tree. A text
+ editor will pop up and you will need to describe the changes you made.
+ Please provide a good description here as it may help people in the
+ future when looking at your code changes.
+ </dd>
+</dl>
+<?php
+ site_footer();
+ exit;
+ } // endif: no error found
+} // endif: no data or checkread not checked
+
+else {
+ if (count($_POST)) {
+ print <<<EOT
+<p class="formerror">
+ We could not have said it more clearly. Read everything on
+ this page and look at the form you are submitting carefully.
+</p>
+EOT;
+ }
+?>
+
+<p>
+ All PHP development is done through a distributed revision control system
+ called SVN. This helps us track changes and it makes it possible for people
+ located in all corners of the world to collaborate on a project without
+ having to worry about stepping on each others' toes.
+</p>
+
+<p>
+ Please note that you do <strong>not</strong> need a SVN account to <a
+ href="/svn.php"><strong>access</strong> the SVN tree</a>, to use PHP,
+ or to write PHP scripts. You only need a SVN account if you will be a
+ regular contributor to the development of PHP itself.
+</p>
+
+<p>
+ And once again, since people just don't seem to understand this point:
+</p>
+
+<table border="0" cellpadding="3" class="standard">
+ <tr>
+ <th>Does Not Require SVN Account</th>
+ <th>Requires SVN Account</th>
+ </tr>
+ <tr>
+ <td class="sub">Learning PHP</td>
+ <td>Developing the PHP runtime</td>
+ </tr>
+ <tr>
+ <td class="sub">Coding in PHP</td>
+ <td>Maintaining an official, bundled PHP extension</td>
+ </tr>
+ <tr>
+ <td class="sub">Reading the PHP source</td>
+ <td><a href="/dochowto">Maintaining the documentation</a></td>
+ </tr>
+ <tr>
+ <td class="sub">Using PHP extensions</td>
+ <td><a href="/dochowto">Translating the documentation</a></td>
+ </tr>
+ <tr>
+ <td class="sub">Creating experimental PHP extensions</td>
+ <td>Maintaining www.php.net</td>
+ </tr>
+ <tr>
+ <td class="sub">Submitting a patch to PHP</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td class="sub">Adding notes to the documentation</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td class="sub">Writing web pages with PHP</td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td class="sub">Setting up a php.net mirror site</td>
+ <td> </td>
+ </tr>
+</table>
+
+<p>
+ If you are contributing a patch, a small fix, or another minor change you do
+ not need to ask for a SVN account before submitting it. Just send your patch
to
+ <a href="mailto:intern...@lists.php.net";>the internals mailing list</a>. You
+ should <a href="mailto:internals-subscr...@lists.php.net";>subscribe to that
+ list</a> to participate in any discussion your patch generates! Your patch may
+ not get noticed the first time. Make sure that when you send your patch, you
+ explain what it does. Make sure you use a clear subject when sending your
+ patch (you might even want to prefix it with <tt>"[PATCH]"</tt>). If nobody
+ seems to take notice after a few days, you might want to try resubmitting it.
+ Your original message might have gotten missed because of another heated
+ discussion.
+</p>
+
+<p>
+ Submitting patches and participating in the discussion on the 'internals' list
+ <strong>before</strong> requesting full SVN access is strongly suggested, so
+ the PHP development team can get to know you and what you'll be contributing.
+ It is suggested that all PHP developers (<strong>people developing PHP
+ itself</strong>, not people developing in PHP) subscribe to this list.
+ Similarly, if you plan on contributing documentation, you should
+ <a href="mailto:phpdoc-subscr...@lists.php.net";>subscribe to the
+ documentation mailing list</a>, and read the <a href="/dochowto">PHP
+ Documentation HOWTO</a>.
+</p>
+
+<p>
+ If you wish to contribute to the documentation please contact the translation
+ team for the language you wish to help with. If you have trouble finding the
+ team, ask on the phpdoc mailing list. Once you have made contact you may
+ apply for a SVN account here by including the name of one or more people from
+ the existing translation team that referred you and of course the language
+ you wish to translate to.
+</p>
+
+<p>
+ If you have a new PEAR package you wish to contribute, propose it
+ through the <a href="http://pear.php.net/pepr/";>PEPR system</a> on
+ <a href="http://pear.php.net/";>the PEAR website</a>. If you have a new PECL
+ extension you wish to contribute, bring it up on the appropriate
+ <a href="http://pecl.php.net/support.php";>PECL mailing list</a> first.
+ <br />
+ Once your PEAR package has been approved, or you get the sense that
+ people generally agree that your PECL contribution is worthwhile, you
+ may apply for a SVN account here. Specify the name of your PEAR package
+ or PECL contribution (single word SVN module name) and also reference an
+ existing account holder who can vouch for your contribution, or provide
+ a link to your PEAR proposal.
+</p>
+
+<p>
+ Okay, if you are still reading, then you may actually need a SVN account.
+ This is <strong>not</strong> an automatic process. Fill in the form below to
+ request an account. In the box next to "Purpose", describe what it is that
+ you intend to do with SVN access. If it isn't clear from what you've
+ described already, tell us what parts of the SVN repository you need access
+ to (for example, "phpdoc" is the documentation tree, "php-src/ext/readline"
+ is the PHP readline extension). If someone told you to fill out the form
+ here, make sure to mention them here!
+</p>
+
+<p>
+ The SVN account, once granted and activated (which could take a while, so be
+ patient!), gives you access to a number of things. First, and most
+ importantly, it gives you access to modify those parts of the PHP SVN tree for
+ which you have requested and been granted access. It also allows you to
comment
+ on and close bugs in our <a href="http://bugs.php.net/";>bug database</a>, and
+ allows you to modify the documentation notes in the <a
href="/manual/">annotated
+ manual</a>. Your SVN account also translates into a f...@php.net forwarding
email
+ address where <strong>foo</strong> is your SVN user id. Feel free to use it!
+</p>
+
+<h2>Request a SVN account</h2>
+
+<p class="warn">
+ Please note that you do <em>NOT</em> need a SVN account to study PHP. You do
+ <em>NOT</em> need a SVN account to learn PHP, to use PHP or to in any way do
+ anything at all with PHP. If you are sitting there wondering if you need a
+ SVN account, then you don't! If an existing SVN account holder suggested you
+ request an account, please mention their SVN id in the request.
+</p>
+<p class="warn">
+ Also note that information provided here will be sent to a public
+ mailing list.
+</p>
+
+<?php
+} // endif: no data submitted
+
+?>
+<form action="/svn-php.php" method="post">
+<table border="0" class="standard" style="width: 80%;">
+<tr>
+ <th class="subr">Full Name:</th>
+ <td><input type="text" size="50" name="fullname"
+ class="max" value="<?php if (isset($_POST['fullname'])) echo
clean($_POST['fullname']);?>" /></td>
+</tr>
+<tr>
+ <th class="subr">Email:</th>
+ <td><input type="text" size="50" name="email"
+ class="max" value="<?php if (isset($_POST['email'])) echo
clean($_POST['email']);?>" /></td>
+</tr>
+<tr>
+ <th class="subr">For what purpose do you require a SVN account:<br />
+ (check all that apply)</th>
+ <td>
+<?php
+$purposes = array("Learning PHP", "Coding in PHP", "Reading the PHP source",
+ "Using PHP extensions", "Creating experimental PHP extensions",
+ "Submitting a patch to PHP", "Adding notes to the documentation",
+ "Writing web pages with PHP", "Setting up a php.net mirror site");
+
+foreach ($purposes as $i => $p) { ?>
+ <input type="checkbox" name="purpose[<?php echo $i?>]" value="1"
+ checked="checked" /><?php echo $p; ?><br />
+<?php } ?>
+ </td>
+</tr>
+<tr>
+ <th class="subr">If your intended purpose is not in the list, <br />please
state it here:</th>
+ <td><textarea cols="50" rows="5" name="realpurpose" class="max"><?php if
(isset($_POST['realpurpose'])) echo
clean($_POST['realpurpose']);?></textarea></td>
+</tr>
+<tr>
+<th class="subr">Do you agree to follow the <a
href="license/contrib-guidelines-code.php">contribution guidelines</a>?</th>
+<td><input type="checkbox" name="guidelines" value="1" />Check the box if you
agree.</td>
+</tr>
+<tr>
+ <th class="subr">User ID:<br /> <small>(single word, lower case)</small></th>
+ <td><input type="text" size="10" name="id"
+ class="max" value="<?php if (isset($_POST['id'])) echo
clean($_POST['id']);?>" /></td>
+</tr>
+<tr>
+ <th class="subr">Requested Password:</th>
+ <td><input type="password" size="10" name="password"
+ class="max" value="<?php if (isset($_POST['password'])) echo
clean($_POST['password']);?>" /></td>
+</tr>
+<tr>
+ <th class="subr">Did you fill this form out correctly (yes/no)?</th>
+ <td><input type="text" size="10" name="yesno" class="max" value="no" /></td>
+</tr>
+<tr>
+ <th>Type of initial karma (who to send this request to):</th>
+ <td>
+ <select name="group">
+<?php
+foreach($groups as $group => $name) {
+ $selected = (isset($_POST["group"]) && $_POST["group"] == $group) ? '
selected="selected"' : '';
+ echo "<option value='$group'$selected>$name</option>\n";
+}
+?>
+ </select>
+ </td>
+</tr>
+<tr>
+ <th colspan="2"><input type="submit" value="Send Request" /></th>
+</tr>
+</table>
+</form>
+
+<?php site_footer();
Property changes on: web/php/trunk/svn-php.php
___________________________________________________________________
Added: svn:keywords
+ Id Rev
Added: svn:eol-style
+ native
Modified: web/php/trunk/urlhowto.php
===================================================================
--- web/php/trunk/urlhowto.php 2009-07-13 06:42:59 UTC (rev 283996)
+++ web/php/trunk/urlhowto.php 2009-07-13 08:14:46 UTC (rev 283997)
@@ -162,8 +162,8 @@
before the first step (PHP page search) mentioned above. Some examples
of shortcut aliases: <tt><?php echo $MYSITE; ?>whatisphp</tt>,
<tt><?php echo $MYSITE; ?>php4news</tt>. The latter is an external page
- alias, as it points to a file on the CVS server, containing information
- about changes in PHP. There are also some convinient aliases, like
+ alias, as it points to a file on the SVN server, containing information
+ about changes in PHP. There are also some convenient aliases, like
<tt><?php echo $MYSITE; ?>de/phpversion</tt> which displays the German
manual page for the phpversion() function.
</p>
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
