You can find more information about SVN, and download clients for most major platforms, at the official SVN site.
If you would like to grab PHP sources or other PHP.net hosted project data from PHP.net, you can also use SVN. No SVN account is required.
'; site_header("Using SVN for PHP Development", array("current" => "FIXME")); $groups = array( "none" => "Choose One", "php" => "PHP Group", "pear" => "PEAR Group", "pecl" => "PECL Group", "doc" => "Doc Group", ); ?>$error
"; } else { ?>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 then please send an email to the appropriate mailing list:
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.
If you are not familiar with SVN, you should have a look at the various documentation resources available in the official SVN site. This is also where to get the most recent version of the SVN client.
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 Mailing Lists page.
SVN itself is quite easy to use. You can follow the steps listed on the anonymous SVN 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.
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. cd php-src.
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.
Please note that you do not need a SVN account to access the SVN tree, 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.
And once again, since people just don't seem to understand this point:
| Does Not Require SVN Account | Requires SVN Account |
|---|---|
| Learning PHP | Developing the PHP runtime |
| Coding in PHP | Maintaining an official, bundled PHP extension |
| Reading the PHP source | Maintaining the documentation |
| Using PHP extensions | Translating the documentation |
| Creating experimental PHP extensions | Maintaining www.php.net |
| Submitting a patch to PHP | |
| Adding notes to the documentation | |
| Writing web pages with PHP | |
| Setting up a php.net mirror site |
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 the internals mailing list. You should subscribe to that list 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 "[PATCH]"). 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.
Submitting patches and participating in the discussion on the 'internals' list before 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 (people developing PHP itself, not people developing in PHP) subscribe to this list. Similarly, if you plan on contributing documentation, you should subscribe to the documentation mailing list, and read the PHP Documentation HOWTO.
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.
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.
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.
Okay, if you are still reading, then you may actually need a SVN account. This is not 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!
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 bug database, and allows you to modify the documentation notes in the annotated manual. Your SVN account also translates into a foo@php.net forwarding email address where foo is your SVN user id. Feel free to use it!
Please note that you do NOT need a SVN account to study PHP. You do NOT 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.
Also note that information provided here will be sent to a public mailing list.