I am more than glad to announce the arrival, the announcement of the new PEAR Group for 2009 and 2010. With a few fresh faces in the Group, this year looks very promising with the mix of both new blood and experienced PEAR Group members.

Those selected include Chuck Burgess, Ken Guest, Christian Weiske and Brett Bieber. The PEAR Group helps to guide the PEAR project as a while and push out initiatives like the updated package manager - Pyrus.

As every year, the elections for the PEAR Group and PEAR President are happening. This year due to a few factors and messages lost in translation, we decided to extend the elections period by 10 days so more people would have time to vote! So remember to cast your vote at http://pear.php.net/election/ and you have until the the 5th of August 2009.

There's both group elections and an an election for president that all PEAR developers can vote on. Hurry! The deadline is Wednesday, August 15th!

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.

Those elected include Joshua Eichorn, Christian Weiske, Chuck Bugress and Travis Swicegood. This year's President id David Coallier. You can find out more on the PEAR website page for the elections.

My place as I consider it and as Greg mentioned on the mailing list yesterday is much more "ambassadorial" than "presidential" and being the PEAR ambassador around the world, I'll be glad to discuss, argue, improve the general idea of PEAR to anyone. I'll also be happy to discuss PEAR2 if anyone is interested but first and foremost I'll be happy to help our new PEAR Group (which I am pretty sure won't need help ) and the community.

You can find out more about the results of this year's elections on the PEAR election pages from pear.php.net.

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.

You can find out more about the elections from the page for the Presidental election and for the Group elections. You must be a PEAR developer in order to vote.

It is now this time of the year again where the PEAR Group throws in the PEAR Group Nominations. The nominated people will then be called for votes by the community and 7 lucky (even though luck has nothing to do with it) will be elected as the new PEAR Group member for the year 2008-2009.

The entire PHP community is requested to nominate who they think would make the best addition to the group, regardless of how they're related to the PEAR project. Nominations should be sent to Martin Jansen by midnight (UTC) May 31st.

I would like to say thanks to everyone who has voted for both the rest of the Team, and I :-). So the new PEAR Group team is built of the following members: Martin Jansen, Arnaud Limbourg, Joshua Eichorn, Christian Weiske, Helgi Thormar, Paul M. Jones, Justin Patrin and finally myself David Coallier.

Team, here we go, let's get some good and solid work done! I am looking forward for such cooperation with both PEAR contributors and other frameworks out there!

He also includes a lengthy listing of some of his personal work for the upcoming months, including work on several of the PEAR pcakges - MDB2, Text_CAPTCHA_Numeral, pearweb (the PEAR website), Image_Transform, and HTML_AJAX.

This is a reminder to get out and vote for your favorite PEAR contenders who wish to be part of the new PEAR governing group.

The vote is for PEAR developers only, so the rest of the community will just need to wait and see the outcome. She also references this post from Joshua Eichorn with several of the candidates' names and links to their PEAR pages for a list of the projects they've worked with. Included in the list are Joshua himself, David Coallier, and Paul Jones (of the Solar framework).

I am confident that both of the proposals will help in improving collaboration in PEAR, mainly because they basically provide the same organization we used to have for all of PEAR (which worked great in the beginning), now for categories of related packages.

He reasons that, since PEAR is such a huge project, it needs this kind of approach - a method to the madness - to help keep the project on the right path.