Those of you on linkedin.com should join the PEAR group, it is open to all. Those of you on facebook.com should join the PEAR group, just search for “PEAR” and it will pop up.
These groups are primarily for fun, but also act as networking tools to get to know the people who are developing and using PEAR. The official support channels for PEAR are still the mailing lists and bug tracker, and are listed at http://pear.php.net/support.php
Please read the following document and post your comments on the wiki using the discussion page. Comments are opened for a period of two weeks.
It is very important that you comment as these standards will define PEAR2.
New developers need quite a time to familiarize themselves with the rules and conventions in PEAR. With the new role of mentors in PEAR2, they will have a contact person they can ask in that cases.
But in many cases the same questions will get asked which will get boring for the mentoring developer, so we need a Mini-FAQ with a list of things the newbie should know.
Which information should go onto that list in your eyes? Comments appreciated!
A common request for PEAR is too use SVN instead of CVS for source code management. As part of the PEAR2 project we are making that happen.
I’m happy to announce that we now have an SVN repo ready for testing. Web access at http://svn.pear.php.net with the SVN url being http://svn.pear.php.net/repo
Were still working out all the naming conventions (and the rules for getting code into PEAR2). But SVN access should be widely available soon. Feel free to leave comments and suggestions.
Update: the svn url is now http://svn.pear.php.net/PEAR2
The PEAR Project has lost a member of its community. Bertrand Gugger (toggg) passed away in the night from June 16th to 17th after suffering a heart attack.
Bertrand was involved in the maintenance of several important PEAR packages, including the Validate package family.
He leaves behind a wife and four children, who have our deepest sympathy. He will be missed.
The SPIP project, where Bertrand was involved as well, has compiled a list of his achievements as a tribute to him. It is available at
Today, the latest incarnation of the PEAR Installer, version 1.6.0, was released at pear.php.net (http://pear.php.net/PEAR to download,
pear upgrade PEAR to upgrade).
This release fixes a number of major regressions introduced in PEAR 1.5.2 that were not fixed in PEAR 1.5.3 or PEAR 1.5.4, and is recommended for immediate upgrade.
New features are mostly minor and include:
- minor improvements to the output of list-all, list, list-upgrades, search. Channel is displayed for many of these commands by default, and with an optional switch for the others
- implementation of code coverage reports using xdebug for .phpt-based tests with the
pear run-tests command. This is somewhat experimental, and bug reports are expected on this new feature, but problems found will be fixed in 1.6.1
The march to Pyrus, the next generation installer for PEAR, and the repository of packages designed for Pyrus (PEAR2) continues. Maintenance on 1.x will continue to contain bug fixes and security fixes, but the pace of new features is going to slow considerably.
If you find any bugs, please report them at http://pear.php.net/bugs/report.php?package=PEAR
I hope this release will be a great upgrade for all of you!
A few minutes ago, the PEAR Group finished its third meeting, which was the first attended by newly elected PEAR Group member Paul Jones (welcome Paul!). In addition to other things discussed, the one that really interests me, and I suspect all of you, is the future direction of the repository and the PEAR Installer.
I’m happy to announce that big changes are in the works. First of all, a brand new channel will be created for PEAR’s new PHP5+ packages, and a brand new installer is being created for these packages. The new installer will be named “Pyrus” (pyrus is the genus of the pear fruit), and the new channel is yet to be named, so if you have any ideas, feel free to post comments to this blog entry to help us come up with a good one. In addition, new packages written for this new channel will be hosted in a new Subversion repository to be hosted at svn.pear.php.net
More details about Pyrus will be forthcoming as the code is written. Currently, it lives in http://cvs.php.net/viewvc.cgi/pear-core/PEAR2 and is very much pre-devel stability.
Thanks for using PEAR, the best is yet to come!
Finally after having a tie in the initial PEAR Group Election, we have ran a runoff election between the two tied parties Justin Patrin and Paul M. Jones.
After the regular time for an election, the choice has been made by the community on the seventh member of the PEAR Group.
I would like to personally congratulate both participants and hope that we will continue and keep on doing constructive work within PEAR even though we cannot keep both of you in.
Furthermore, special congratulations to Paul M. Jones who has been elected as the 7th member. Looking forward for solid and hard work
Thanks to all the voters for taking the time to vote.
It’s been a great ride so far.
PEAR has undergone a minor revolution in culture in the past several months, and as your newly elected president, I’m excited to start telling you about it. This blog is just one example of the new ways PEAR will be reaching out to the larger PHP community. Although the transfer of power to the newly elected PEAR Group finally completed on May 25 with the election of Paul Jones as the final member, already activity to make some significant changes has taken place.
The PEAR Group will be deciding most of the details, it is my job to reach out to you, programmers of PHP who are looking for a faster or better way to solve the problems you solve every day so that you can focus on the important things.
Plans are well under way to ramp up activity on promoting PHP 5 with new PEAR packages, and we have heard the criticisms loud and clear of the first incarnation of PEAR. Fortunately, we also know what is working and have no plans to throw the baby out with the bathwater. At this stage, I can’t go into details, as official policy has to be decided by the PEAR Group (next meeting is on June 3, so expect news quite soon), but stay tuned to this blog for up-to-the-minute musings by members of the PEAR Group and myself as PEAR blossoms in its new spring.
This is the official blog of PEAR‘s (PHP Extension and Application Repository) elected President and PEAR Group, the two heads of PEAR. Here, you will find announcements as well as brainstorming and the general excitement and bustle of this vibrant open source community.