There’s a known issue with the Phergie 2.0.3 release that prevents some events from being processed. This is due to three circumstances:

1. Human error – In an effort to push the release out more quickly to replace the existing Phergie 1.x installation on Freenode with a 2.x instance, this issue was simply overlooked and somehow didn’t present itself distinctly during rudimentary testing. This was a big mistake on our part and we apologize to any affected users.
2. Lack of sufficient unit testing – This is something we’re working on. However, the problem was actually with two Phergie core components that had full code coverage. This shows that, while code coverage can be useful to expose blocks of code that are definitely not covered by any tests, don’t assume code is fully covered simply because code coverage says it is.
3. Unexpected behavior – What appears to be a bug in PHP itself, specifically in the FilterIterator class, contributed to the problem. Oddly, this class also appears to have full code coverage, affirming the related point above.

For those users affected, there are two options for dealing with this issue pending the next release.

1. Downgrade to Phergie 2.0.2 – Not ideal, but that release was relatively stable.
2. Patch 2.0.3 – The patch is in the git repository if you’d like to apply the patch to fix the issue yourself.
3. Run Phergie bleeding edge – This is done by cloning the git repository, placing your settings file on the same level as the Phergie directory, and running the phergie.php script there.

We’re hoping to make another release within the next couple of weeks.

My profound apologies for the even longer delay on this release — believe me, I felt it when putting together the changelog for it — but I’m elated to announce that Phergie 2.0.3 is now available. You can read about the many bug fixes and exciting new additions in this release on the Changelog page. With this release, we’ll be attempting to replace the dated Phergie 1.x installation running on the Freenode network with this new 2.x release. Once again, our thanks go out to all of our users and contributors for their help in making the Phergie project a continued success!

In an article released today, Developer.com outlined their top 10 PHP projects “pushing the envelope” by using the language in unusual and interesting ways. Phergie made #8 on the list with a mention of its recent inclusion in a StatusNet Google Summer of Code project. The Phergie team is honored to have their work featured alongside other spectacular PHP projects and thanks Developer.com for helping to spread the word about the Phergie project. A special thanks to Chris Cornutt, a Phergie enthusiast and the lead developer of PHPDeveloper.org and Joind.in, for bringing this article to our attention.

Luke Fitzgerald AKA darkip posted an update today on his Google Summer of Code project for which he’s building a Phergie plugin to interface with StatusNet. The Phergie team is excited to see his progress, has enjoyed working with him immensely, and appreciates the contributions he’s made back to the Phergie project.

Luke Fitzgerald AKA darkip recently joined the ranks of Phergie contributors. As it turns out, he’s also participating in the Google Summer of Code program — and using Phergie to do it! He’s developing an IRC plugin on top of Phergie to interface with StatusNet and has already made several contributions to the Phergie project as a result. We feel privileged to have him working with us and humbled to see our team’s work included in a GSoC effort.

The Phergie project now has a Google Group! Because not all users or developers frequent IRC, it was decided that some sort of mailing list medium was needed where users and developers can come together to discuss issues and potential new features as well as to offer support to the community. We hope you’ll join and we thank you for your continued contributions.

Who: Everyone and anyone who loves Phergie and wants to help make her better!

What: The Phergie Hackathon

Where: The #phergie channel of the Freenode IRC network

When: Saturday, June 19 from 10 AM CDT till the last person leaves

Why: We’re gearing up for a 2.0.3 release and we’re looking to knock out as many bugs as we can that currently block us from replacing the old Phergie 1.x instance currently running on Freenode with a 2.x instance.

How: Just show up in the IRC channel, pick a ticket from the laundry list, and start hacking. Feel free to post any questions you may have to the channel. If you want to hit the ground running on the day of the Hackathon, decide what ticket you’d like to work on and take a look at the developer docs and source code beforehand.

Hope to see you there!

Thanks to the efforts of Jess Planck, the Phergie project finally has a logo! You’ll now see it sported in the page header on this web site. The colors of the image have been designed such that Phergie shirts are a definite possibility in the future. Please take a moment to send a shout out to Jess on Twitter and thank him for his contribution!

Brandon Savage, who recently began contributing to the Phergie project, published a blog post today that spotlights the Phergie project as an example of good architecture and creating a low barrier to entry for prospective contributors. His kind words and evangelism of the project are appreciated as are the excellent points that he makes on the post’s overarching topic.