<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: The WP-OpenID+ upgrade/bug fix bounty</title>
	<atom:link href="http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/</link>
	<description>Clever Tagline Unavailable At Publication Time</description>
	<pubDate>Tue, 02 Dec 2008 21:13:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Iwaruna.com &#187; OpenID for comments in Iwaruna.com</title>
		<link>http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-700</link>
		<dc:creator>Iwaruna.com &#187; OpenID for comments in Iwaruna.com</dc:creator>
		<pubDate>Sun, 12 Aug 2007 19:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-700</guid>
		<description>[...] of these issues might be due to differences between WordPress version 2.1 and 2.2, as noted by Michael Gracie. His article helpfully links to a list of open WP-OpenID+ [...]</description>
		<content:encoded><![CDATA[<p>[...] of these issues might be due to differences between WordPress version 2.1 and 2.2, as noted by Michael Gracie. His article helpfully links to a list of open WP-OpenID+ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Gracie</title>
		<link>http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-466</link>
		<dc:creator>Michael Gracie</dc:creator>
		<pubDate>Wed, 25 Jul 2007 04:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-466</guid>
		<description>I've just found this as well: http://the-notebook.org/12/01/2006/openid-comments-for-wordpress/ (h/t to &lt;a href="http://mashable.com/2007/07/24/wordpress-comments/" rel="nofollow"&gt;Mashable&lt;/a&gt;).

Sounds sketchy.  Any thoughts?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just found this as well: <a href="http://the-notebook.org/12/01/2006/openid-comments-for-wordpress/" rel="nofollow">http://the-notebook.org/12/01/2006/openid-comments-for-wordpress/</a> (h/t to <a href="http://mashable.com/2007/07/24/wordpress-comments/" rel="nofollow">Mashable</a>).</p>
<p>Sounds sketchy.  Any thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Gracie</title>
		<link>http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-461</link>
		<dc:creator>Michael Gracie</dc:creator>
		<pubDate>Tue, 24 Jul 2007 04:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-461</guid>
		<description>Will, You both did great work, and deserve all the thanks.  I've modified the delivery directions per your instructions - that is certainly the best way to maintain continuity.

As for producing a new version for 2.2, I think that is fine.  In fact, while I received the same error messages as others, I was actually able to get OpenID comments to properly post with the plug-in.  My apprehension about install was primarily related to the other flaws you found, as I already noted.  Nonetheless, others didn't have similar luck, which is why I put up the bounty.

I think getting the functionality in place is the most important thing - OpenID now obviously has major legs and I'd like to see as many people accepting it as possible.  Since you and Alan have worked with the Wordpress community before, whatever you feel is the best approach is certainly fine by me.

It would be great if you could keep me informed, so I can fork up the money as promptly as possible.</description>
		<content:encoded><![CDATA[<p>Will, You both did great work, and deserve all the thanks.  I&#8217;ve modified the delivery directions per your instructions - that is certainly the best way to maintain continuity.</p>
<p>As for producing a new version for 2.2, I think that is fine.  In fact, while I received the same error messages as others, I was actually able to get OpenID comments to properly post with the plug-in.  My apprehension about install was primarily related to the other flaws you found, as I already noted.  Nonetheless, others didn&#8217;t have similar luck, which is why I put up the bounty.</p>
<p>I think getting the functionality in place is the most important thing - OpenID now obviously has major legs and I&#8217;d like to see as many people accepting it as possible.  Since you and Alan have worked with the Wordpress community before, whatever you feel is the best approach is certainly fine by me.</p>
<p>It would be great if you could keep me informed, so I can fork up the money as promptly as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Norris</title>
		<link>http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-459</link>
		<dc:creator>Will Norris</dc:creator>
		<pubDate>Tue, 24 Jul 2007 01:08:17 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-459</guid>
		<description>Thanks for the kind words, Michael.... Alan and I have been talking a little this last week with a couple of other people to try and figure out the WP 2.2 issue, no complete solution that I'm aware of.  You can alternately change #2 in your bounty to have them provide Alan and/or me a patch of their changes and we can commit them upstream.  If someone is interested in contributing long-term to the plug-in, I'm certainly open to that as well.

As a side note, I have a couple of other uncommitted changes I was working on some time ago, but they currently require WP 2.2.  I could probably make it work with earlier versions, but it would be difficult due to missing actions that were added more recently.  Do you think too many people would be opposed to the next release being WP 2.2+ ?  If it can fix whatever the current issue is and include these additional features?  I generally like to maintain as much backward compatibility as possible unless there is a really good reason not to.  Avoiding really ugly hacks might be a good enough reason. :)</description>
		<content:encoded><![CDATA[<p>Thanks for the kind words, Michael&#8230;. Alan and I have been talking a little this last week with a couple of other people to try and figure out the WP 2.2 issue, no complete solution that I&#8217;m aware of.  You can alternately change #2 in your bounty to have them provide Alan and/or me a patch of their changes and we can commit them upstream.  If someone is interested in contributing long-term to the plug-in, I&#8217;m certainly open to that as well.</p>
<p>As a side note, I have a couple of other uncommitted changes I was working on some time ago, but they currently require WP 2.2.  I could probably make it work with earlier versions, but it would be difficult due to missing actions that were added more recently.  Do you think too many people would be opposed to the next release being WP 2.2+ ?  If it can fix whatever the current issue is and include these additional features?  I generally like to maintain as much backward compatibility as possible unless there is a really good reason not to.  Avoiding really ugly hacks might be a good enough reason. <img src='http://michaelgracie.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Gracie</title>
		<link>http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-458</link>
		<dc:creator>Michael Gracie</dc:creator>
		<pubDate>Mon, 23 Jul 2007 22:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-458</guid>
		<description>David, thanks very much.</description>
		<content:encoded><![CDATA[<p>David, thanks very much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Recordon</title>
		<link>http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-457</link>
		<dc:creator>David Recordon</dc:creator>
		<pubDate>Mon, 23 Jul 2007 21:52:40 +0000</pubDate>
		<guid isPermaLink="false">http://michaelgracie.com/2007/07/23/the-wp-openid-upgradebug-fix-bounty/#comment-457</guid>
		<description>I'd personally be willing to throw in $25 as well.</description>
		<content:encoded><![CDATA[<p>I&#8217;d personally be willing to throw in $25 as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
