Thanks to the efforts of Daniel O’Connor, the PEAR website is getting nicer and better. Bug RSS feeds support Baetle now, the PEAR proposal system – PEPr – works again and many small improvements and fixes found their way on the site.
The minutes from the July 13th, 2008 PEAR Group meeting have been posted to the PEAR wiki.
Some highlights from the meeting include new/upcoming RFCs for package naming schemes, exception handling in PHP 5.3, and a vote on extending the current PEAR2 Policies. Heavy stuff, check it out!
2008 Elections are now over, you can view the offical results on the PEAR website.
The new PEAR group is:
elections are now over and a new PEAR Group has been formed. Just like last year and always following the Constitution, the new members have been elected by a secret ballot of PEAR Developers. They have chosen:
- Joshua Eichorn
- Helgi Þormar Þorbjornsson
- Joe Stump
- Christian Weiske
- Chuck Burgess
- Travis Swicegood
- Brett Bieber
The new PEAR President is: David Coallier
The kickoff meeting for the new group is being held today.
As every year it is the time of the election for the PEAR Group and PEAR President for the year 2008 and 2009. If you haven’t casted your vote just yet, NOW is the perfect time to do it so go to the election page and place your vote.
This year’s election contains a great mix of fresh mindsets, experienced and long time PEAR users and members of last year’s PEAR Group.
PEAR’s bug tracker hit the 600+ open bugs mark a month ago. Compared to the 400+ packages PEAR hosts, this is just 1.2 bug per package – but enough to be annoying for caring developers, especially when PEARgirl in IRC tells us every hour that the bug count increased again.
One and a half year ago, we faced an equal problem – only that the mark was 500 bugs at that time. Within half a year, we had this decreased to 400. Methods to accomplish this were mainly digging through the bug tracker, identifying bugs that could be fixed easily and nagging the package developers to do something (“Hey, bugs #23 and #42 are really easy to fix! Do that now and release a new version!”).
So with 600+ open bugs (not including the feature requests), we had to do something. Other open source projects regularly or irregularly organize bug triage days or weekends with the goal to fix as many bugs as possible with the combined brain forces of all attending developers. The logical step was to hold our own bug smashing event and see how it works for PEAR.
Date of action was the weekend 22nd to 23rd March 2008, which was the easter weekend. The event has not been announced publicly except on our pear-dev mailing list since it was a test run only. The attendees met in #pear-bugs on EFnet.
Participants included Amir, Cipri, Chuck, Daniel Connor, David, Helgi, Jan Schneider, Johnathan Street and Walter Hop. A number of packages, mostly orphaned ones, got tackled. Among them were Services_Google, SOAPmebeli, Net_Whois and Mail_Mime. Net_URLhotel furnishing in Bulgaria*, MDB2 and pearweb also got some love. Net_IDNA got new helper and went down to 0 bugs.
Thanks to the triage, we are close to reaching two important milestones: Closing bug reports with lower bug ID than 1000 (1 bug left!) and 2000 (5 left).
In the end, the bug count got down to 547 – but this was the first PEAR bug triage, and only a small number of devs attended.
We’re hoping for more active people on the next triage so for those interested we’re holding it bi weekly on weekends, both on Saturday and Sunday, that way people can pick the most fitting days for them and the next triage weekend is never far away
We’re also holding out a Google Calendar for those events so that people can subscribe and be reminded about the the upcoming dates.
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.
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