<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Phergie</title>
	<atom:link href="http://phergie.org/feed/" rel="self" type="application/rss+xml" />
	<link>http://phergie.org</link>
	<description>A PHP IRC Bot</description>
	<lastBuildDate>Wed, 09 Nov 2011 14:15:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>PHPWM Presentation on Phergie</title>
		<link>http://phergie.org/2011/11/09/phpwm-presentation-on-phergie/</link>
		<comments>http://phergie.org/2011/11/09/phpwm-presentation-on-phergie/#comments</comments>
		<pubDate>Wed, 09 Nov 2011 14:15:31 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Articles]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=95</guid>
		<description><![CDATA[Alex Mace gave a presentation at a recent PHPWM user group meeting on Phergie and the XMPP driver he&#8217;s been developing for her. It&#8217;s a great quick high-level overview of Phergie&#8217;s history and architecture and Alex&#8217;s experiences in implementing the XMPP driver. Go check it out!]]></description>
			<content:encoded><![CDATA[<p><a title="Alex Mace (alexmace) on Twitter" href="https://twitter.com/#!/alexmace">Alex Mace</a> gave <a title="Phergie, An IRC (and XMPP) Bot" href="http://www.slideshare.net/alexmace/phergie-an-irc-and-xmpp-bot">a presentation</a> at a recent <a title="start    [West Midlands PHP User Group (PHPWM)]" href="http://phpwm.org.uk">PHPWM user group</a> meeting on Phergie and the <a title="alexmace/phergie at xmpp - GitHub" href="https://github.com/alexmace/phergie/tree/xmpp">XMPP driver</a> he&#8217;s been developing for her. It&#8217;s a great quick high-level overview of Phergie&#8217;s history and architecture and Alex&#8217;s experiences in implementing the XMPP driver. Go check it out!</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2011/11/09/phpwm-presentation-on-phergie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Phergie 2.1.0 Released</title>
		<link>http://phergie.org/2011/08/15/phergie-2-1-0-released/</link>
		<comments>http://phergie.org/2011/08/15/phergie-2-1-0-released/#comments</comments>
		<pubDate>Mon, 15 Aug 2011 23:01:40 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Releases]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=93</guid>
		<description><![CDATA[After over 11 months — trust us, we don&#8217;t want to go that long without a release ever again — Phergie 2.1.0 is now available. You can read about the many bug fixes and new additions in this release on the Changelog page. This release sports several new plugins, a number of new plugin features [...]]]></description>
			<content:encoded><![CDATA[<p>After over 11 months — trust us, we don&#8217;t want to go that long without a release ever again — Phergie 2.1.0 is now available. You can read about the many bug fixes and new additions in this release on the <a title="Changelog — Phergie" href="/changelog">Changelog</a> page. This release sports several new plugins, a number of new plugin features and updates, numerous bug fixes, and a few unit test and coding standard compliance improvements. As always, our thanks go out to all of our users and contributors for their help in making the Phergie project a continued success!</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2011/08/15/phergie-2-1-0-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GitHub Repo Relocation</title>
		<link>http://phergie.org/2011/07/13/github-repo-relocation/</link>
		<comments>http://phergie.org/2011/07/13/github-repo-relocation/#comments</comments>
		<pubDate>Wed, 13 Jul 2011 05:16:07 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Announcements]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=90</guid>
		<description><![CDATA[Until now, the main GitHub repository for the Phergie project had been kept under a single user account at http://github.com/elazar/phergie. It has been transferred to an organization on GitHub. The new repo address is http://github.com/phergie/phergie. There are a few reasons for this transfer: A new core team will be given merge rights to streamline acceptance [...]]]></description>
			<content:encoded><![CDATA[<p>Until now, the main <a title="GitHub" href="http://github.com">GitHub</a> repository for the Phergie project had been kept under a single user account at <a title="elazar/phergie - GitHub" href="http://github.com/elazar/phergie">http://github.com/elazar/phergie</a>. It has been transferred to an organization on GitHub. The new repo address is <a title="phergie/phergie - GitHub" href="http://github.com/phergie/phergie">http://github.com/phergie/phergie</a>.</p>
<p>There are a few reasons for this transfer:</p>
<ul>
<li>A new core team will be given merge rights to streamline acceptance of contributions where it was previously limited by the availability of a single developer.</li>
<li>Eventually, plugins and other sub-projects can be split off into their own repositories within the same organization to be developed independently from the main project and to allow more fine-grained grants of merge rights.</li>
</ul>
<p>Any pull requests and issues should be directed to the transferred repository. Any existing clones of the original repository will need to have their upstream remotes updated to point to the new location. This can be done using the following command:</p>
<p><code>git remote set-url upstream git://github.com/phergie/phergie.git</code></p>
<p>Any questions about this change can be directed to the #phergie IRC channel on Freenode or in a comment on this post.</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2011/07/13/github-repo-relocation/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Using Phergie with Upstart</title>
		<link>http://phergie.org/2011/03/02/using-phergie-with-upstart/</link>
		<comments>http://phergie.org/2011/03/02/using-phergie-with-upstart/#comments</comments>
		<pubDate>Wed, 02 Mar 2011 15:46:18 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Articles]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=88</guid>
		<description><![CDATA[Anthony Wlodarski has posted an example of an Upstart script he wrote to easily start, stop, and restart Phergie. The script source is open and freely available. Thanks to Anthony for taking the time to write up, publish, and tell us about his blog post on this neat method of controlling Phergie.]]></description>
			<content:encoded><![CDATA[<p><a title="ant.i.am | Herpity derp???" href="http://anthonyw.net">Anthony Wlodarski</a> has posted <a title="Using Phergie with Upstart (a.k.a. Phergie #winning) | ant.i.am" href="http://anthonyw.net/2011/03/using-phergie-with-upstart/">an example</a> of an <a title="upstart - event-based init daemon" href="http://upstart.ubuntu.com">Upstart</a> script he wrote to easily start, stop, and restart Phergie. The script source is open and freely available. Thanks to Anthony for taking the time to write up, publish, and tell us about his blog post on this neat method of controlling Phergie.</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2011/03/02/using-phergie-with-upstart/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Yii Framework Using Phergie</title>
		<link>http://phergie.org/2010/12/03/yii-framework-using-phergie/</link>
		<comments>http://phergie.org/2010/12/03/yii-framework-using-phergie/#comments</comments>
		<pubDate>Fri, 03 Dec 2010 14:18:21 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Articles]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=86</guid>
		<description><![CDATA[The increasingly popular Yii Framework project recently implemented a Phergie bot, which they&#8217;ve named YiiBot, in their #yii IRC channel on the Freenode network. One of their developers, tydeas, has made a few appearances in the #phergie channel to ask questions and discuss Phergie. He has produced several custom Phergie plugins for use in YiiBot. [...]]]></description>
			<content:encoded><![CDATA[<p>The increasingly popular <a title="Yii Framework: Best for Web 2.0 Development" href="http://www.yiiframework.com/">Yii Framework</a> project recently <a title="YiiBot in irc.freenode.org #yii - Yii Framework Forum" href="http://www.yiiframework.com/forum/index.php?/topic/13190-yiibot-in-ircfreenodeorg-yii/">implemented a Phergie bot</a>, which they&#8217;ve named YiiBot, in their #yii IRC channel on the <a title="About the Network" href="http://freenode.net">Freenode</a> network. One of their developers, tydeas, has made a few appearances in the #phergie channel to ask questions and discuss Phergie. He has produced several custom Phergie plugins for use in YiiBot. We&#8217;re very excited at this development and hope that the Yii project continues to use and extend Phergie, and perhaps even contribute some of their plugins back to the project!</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2010/12/03/yii-framework-using-phergie/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>New Unit Testing Docs</title>
		<link>http://phergie.org/2010/09/29/new-unit-testing-docs/</link>
		<comments>http://phergie.org/2010/09/29/new-unit-testing-docs/#comments</comments>
		<pubDate>Wed, 29 Sep 2010 14:15:54 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Announcements]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=85</guid>
		<description><![CDATA[The Developers page now includes a section on unit testing Phergie plugins. Efforts to improve code coverage of the Phergie codebase continue, so if you&#8217;d like to help out, find a plugin lacking a unit test suite and write one. If you&#8217;re developing your own plugins to contribute back to the project, try to include [...]]]></description>
			<content:encoded><![CDATA[<p>The <a title="Developers — Phergie" href="/developers">Developers</a> page now includes <a title="Developers — Phergie" href="/developers/#Unit_Testing">a section</a> on unit testing Phergie plugins. Efforts to improve <a title="Chapter 15. Code Coverage Analysis" href="http://www.phpunit.de/manual/3.4/en/code-coverage-analysis.html">code coverage</a> of the Phergie codebase continue, so if you&#8217;d like to help out, find a plugin lacking a unit test suite and write one. If you&#8217;re developing your own plugins to contribute back to the project, try to include unit test suites for them when you submit them. Our continued thanks go out to all of our contributors.</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2010/09/29/new-unit-testing-docs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Phergie 2.0.4 Released</title>
		<link>http://phergie.org/2010/09/28/phergie-2-0-4-released/</link>
		<comments>http://phergie.org/2010/09/28/phergie-2-0-4-released/#comments</comments>
		<pubDate>Tue, 28 Sep 2010 11:57:49 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Releases]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=83</guid>
		<description><![CDATA[Phergie 2.0.4 is now available. You can read about the many bug fixes and new additions in this release on the Changelog page. This release sports significant improvements in stability and unit test code coverage. As always, our thanks go out to all of our users and contributors for their help in making the Phergie [...]]]></description>
			<content:encoded><![CDATA[<p>Phergie 2.0.4 is now available. You can read about the many bug fixes and new additions in this release on the Changelog page. This release sports significant improvements in stability and unit test code coverage. As always, our thanks go out to all of our users and contributors for their help in making the Phergie project a continued success!</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2010/09/28/phergie-2-0-4-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Known Issue in Phergie 2.0.3</title>
		<link>http://phergie.org/2010/08/08/known-issue-in-phergie-2-0-3/</link>
		<comments>http://phergie.org/2010/08/08/known-issue-in-phergie-2-0-3/#comments</comments>
		<pubDate>Sun, 08 Aug 2010 15:31:11 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Announcements]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=80</guid>
		<description><![CDATA[There&#8217;s a known issue with the Phergie 2.0.3 release that prevents some events from being processed. This is due to three circumstances: Human error &#8211; 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 [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s a known issue with the Phergie 2.0.3 release that prevents some events from being processed. This is due to three circumstances:</p>
<ol>
<li>Human error &#8211; 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&#8217;t present itself distinctly during rudimentary testing. This was a big mistake on our part and we apologize to any affected users.</li>
<li>Lack of sufficient unit testing &#8211; This is something we&#8217;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&#8217;t assume code is fully covered simply because code coverage says it is.</li>
<li>Unexpected behavior &#8211; What appears to be <a title="Bug #52560 :: FilterIterator errantly returns null for first element" href="http://bugs.php.net/bug.php?id=52560">a bug</a> in PHP itself, specifically in the <a title="PHP: FilterIterator - Manual" href="http://php.net/filteriterator">FilterIterator</a> class, contributed to the problem. Oddly, this class also <a title="LCOV - PHP Code Coverage - spl/spl_iterators.c" href="http://gcov.php.net/PHP_5_2/lcov_html/spl/spl_iterators.c.gcov.php" class="broken_link">appears to have full code coverage</a>, affirming the related point above.</li>
</ol>
<p>For those users affected, there are two options for dealing with this issue pending the next release.</p>
<ol>
<li>Downgrade to Phergie 2.0.2 &#8211; Not ideal, but that release was relatively stable.</li>
<li>Patch 2.0.3 &#8211; The <a title="Commit 84fb294f32a8ddf2fbbf2a5a9835c88149a85a4b to elazar's phergie - GitHub" href="http://github.com/elazar/phergie/commit/84fb294f32a8ddf2fbbf2a5a9835c88149a85a4b#diff-0">patch</a> is in the git repository if you&#8217;d like to apply the patch to fix the issue yourself.</li>
<li>Run Phergie bleeding edge &#8211; 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.</li>
</ol>
<p>We&#8217;re hoping to make another release within the next couple of weeks.</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2010/08/08/known-issue-in-phergie-2-0-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Phergie 2.0.3 Released</title>
		<link>http://phergie.org/2010/08/02/phergie-2-0-3-released/</link>
		<comments>http://phergie.org/2010/08/02/phergie-2-0-3-released/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 02:31:00 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Releases]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=79</guid>
		<description><![CDATA[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&#8217;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 [...]]]></description>
			<content:encoded><![CDATA[<p>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&#8217;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 <a title="Changelog — Phergie" href="/changelog#2.0.3">Changelog</a> page. With this release, we&#8217;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!</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2010/08/02/phergie-2-0-3-released/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Phergie Mention on Developer.com</title>
		<link>http://phergie.org/2010/07/31/phergie-mention-on-developer-com/</link>
		<comments>http://phergie.org/2010/07/31/phergie-mention-on-developer-com/#comments</comments>
		<pubDate>Sat, 31 Jul 2010 00:35:34 +0000</pubDate>
		<dc:creator>Matthew Turland</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[gsoc]]></category>
		<category><![CDATA[statusnet]]></category>

		<guid isPermaLink="false">http://phergie.org/?p=76</guid>
		<description><![CDATA[In an article released today, Developer.com outlined their top 10 PHP projects &#8220;pushing the envelope&#8221; 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 [...]]]></description>
			<content:encoded><![CDATA[<p>In <a title="10 Experimental PHP Projects Pushing the Envelope — Developer.com" href="http://www.developer.com/open/article.php/10930_3896056_1/10-Experimental-PHP-Projects-Pushing-the-Envelope.htm">an article</a> released today, <a title="Developer.com: Your Home for Java and Open Source Development Knowledge" href="http://developer.com">Developer.com</a> outlined their top 10 PHP projects &#8220;pushing the envelope&#8221; by using the language in unusual and interesting ways. <a title="10 Experimental PHP Projects Pushing the Envelope — Developer.com" href="http://www.developer.com/open/article.php/10930_3896056_2/10-Experimental-PHP-Projects-Pushing-the-Envelope.htm">Phergie made #8</a> on the list with a mention of its <a title="Phergie — A PHP IRC Bot" href="/phergie-in-statusnet-gsoc-project/">recent inclusion</a> 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 <a title="Chris Cornutt (enygma) on Twitter" href="http://twitter.com/enygma">Chris Cornutt</a>, a Phergie enthusiast and the lead developer of <a title="PHPDeveloper: PHP News, Views and Community" href="http://phpdeveloper.org">PHPDeveloper.org</a> and <a title="Start - Joind.in" href="http://joind.in/">Joind.in</a>, for bringing this article to our attention.</p>
]]></content:encoded>
			<wfw:commentRss>http://phergie.org/2010/07/31/phergie-mention-on-developer-com/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

