PEAR Development on Github

Like many other projects, many components of PEAR have started a migration to github.

We have two primary organisations set up for PEAR and PEAR2.

While the existing PEAR packages will continue to use the pear.php.net distribution and bug tracking capabilities; it’s never been easier to contribute to a PEAR package – simply fork; add your changes and send us a pull request.

If your preferred packages aren’t yet on github, please feel free to drop us a line on the pear-dev mailing list.

This entry was posted in Uncategorized. Bookmark the permalink.

3 Responses to PEAR Development on Github

  1. Alan Knowles says:

    Probably should go on the mailing list, but I’ve not had time to post this, github currently has a huge problem for PEAR development.

    The commit emails do not include the patches… (only a link to them, and a long wait when you review on a mobile device….)

    This means commits are missing peer review, and security review.

    I’m guessing not a huge problem at present as most of the packages that have been moved are basically ‘the attic’ ones, but until github supports propper commit emails, It would be a good idea to hold off on migrating the remaining core packages until either this is fixed (not sure if github has settings for that) or we find an alternative, (git.php.net or gitorious)

    Alan

  2. doconnor says:

    I’m actually finding the commit emails to be a non issue. Certainly where there are changes happening from external people; the fork/pull request model is actually letting me review better.
    IE: https://github.com/pear/Console_Getargs/pull/1 is out there for comment and review.

  3. Thomas says:

    Hi, the go-pear.php installation option still refers to the old svn and does not work!