Skip to content


Subversion checkout URL

You can clone with
Download ZIP
PHP JavaScript CSS XSLT HTML Makefile
Latest commit 8e9b4ee @saltybeagle saltybeagle Merge pull request #10 from stof/patch-2
Add missing space between HTML attributes
Failed to load latest commit information.
cron Read from config
doc The proper way (at least for the pearweb box) to understand the xmlrp…
include Load jQuery from the CDN using HTTPS
public_html Add missing space between HTML attributes
resources Use lightbulb instead of question mark for 'note' background.
rfc * Some notes on stuff to do with the stats
scripts Make sure we show the latest version as when outputting.
sql Add index to files table
templates Add recaptcha for user notes
tests Swap doctype to xhtml5; as per…
weeklynews * Removing the files which are now in the archives.
.travis.yml Add travis
README Updated README to have release instructions
TODO * Removing some finished tasks from the todo list
package-channel.xml fix package_channel.php
package-election.xml update package-election.xml
package-gopear.xml Fix date
package-index.xml prepare release of pearweb_index-1.22.2
package-manual.xml Revert changes to package-manual.xml from c03295d
package-pepr.xml Prep for release
package-qa.xml Regen package
package.php release pearweb-1.26.1
package.xml release pearweb-1.26.1
package_channel.php fix package_channel.php
package_election.php update package-election.xml
package_index.php prepare release of pearweb_index-1.22.2
package_manual.php Fix package-manual.xml generation script
package_pepr.php Prep for release
package_qa.php Update package-qa.xml
pearweb.php Fix some lingering CVS references. Update php versions. A few wording…
pearweb_election.php replace web-dir with www-dir
pearweb_pepr.php replace web-dir with www-dir
rollback.php require MDB2



Read this before starting to hack on the PEAR website.

1) Coding Standards

    Code for the PEAR website strictly follows the PEAR Coding Standards 

    If changes that do not follow these standards are committed to the 
    repository, they will be reverted.

    Usage of '@' to silence warnings and notices is discouraged.  Use it
    only if no clean solution exists.

2) Only commit working code

    People constantly committing code that makes (parts of) the website 
    inaccessible will lose their SVN karma.

    Test your changes before committing them.  If you are unable to set 
    up a test environment, you must not commit anything!

3) Usage of header comment blocks

    Every newly added text file has to carry a header comment block
    similar to the following:

       | PEAR Web site version 1.0                                            |
       | Copyright (c) 2005 The PEAR Group                                    |
       | This source file is subject to version 2.02 of the PHP license,      |
       | that is bundled with this package in the file LICENSE, and is        |
       | available at through the world-wide-web at                           |
       |                                 |
       | If you did not receive a copy of the PHP license and are unable to   |
       | obtain it through the world-wide-web, please send a note to          |
       | so we can mail you a copy immediately.               |
       | Author: Martin Jansen <>                                   |

4) Performance

    The PEAR website can be considered a high traffic website, which is
    why a content cache is employed.  If new sections/pages are added, 
    one has to make sure that they get cached if it makes sense.  (Most
    of the time it makes sense.)

    Also one has to ensure that newly added code does not lead to 
    performance issues or bottlenecks.

5) Dependencies

    If new dependencies are introduced, they must be written down in

    If possible, non-PEAR dependencies and dependencies on packages with
    only beta- or alpha-releases must be avoided.

6) Talk first, code later

    If you want to implement new features, ask the PEAR webmaster team 
    [2] first.  Otherwise you may run into serious trouble.

7) Packaging & deployment
See the instructions in for production deployment

Ensure that you have deployed and tested the changes on
  $ pear upgrade -f package.xml
or a specific area:
  $ pear upgrade -f package-pepr.xml

Once you have tested your changes, you can proceed.

Third, make the appropriate pearweb release and push it to Be sure to update the relevant package_*.php file and generate the new package.xml

  $ vim package_pepr.php
  $ php package_pepr.php make
  $ git commit -m "Release preparation" package-pepr.xml package_pepr.php
  $ pear package package-pepr.xml
  $ git tag -a pearweb_pepr-1.2.3 -m 'PEARWeb_PEPR-1.2.3'

Join the #pear IRC channel on efnet, and discuss the changes you are about to make.

  $ ssh
  $ sudo pear upgrade pearweb
  $ sudo pear upgrade pearweb_pepr

Apply any mysql, crontab changes manually.

Verify that is still functioning and update this changelog.


Something went wrong with that request. Please try again.