The WP-OpenID+ upgrade/bug fix bounty

OpenIDNot a $5,000 bounty – without sponsors like this we’d run out of dog food around here.

Will Norris was kind (and smart) enough to assemble the WP-OpenID+ plug-in for WordPress users. Built on previous work, this plug-in was created around v2.1 of the WordPress platform. I had previously installed it, and found it fantastic; unfortunately by the time I got around to cleaning up archives and taking this weblog live, I had already moved up to WordPress 2.2. I’ve since had problems with it, and I’ve noticed several folks across the web have had some issues with the combination as well. In addition, Will himself noted several flaws with his own work, the most important of which I believe is the need to honor the “anyone can register” component (that which can prevent account creation for everyone who comments on your blog).

worlds-smartest-collieI’m keen to start allowing OpenID access here, and would love to see this plug-in updated. Mr. Norris is very busy nowadays (he is getting married – offer congratulations!), and I think he’s done enough work already (as has Alan Castonguay, who built the previous version and deserves much credit as well). As my collie dog has shown more prowess at hacking code than his owner (although who owns who is the subject of much debate around here), I was thinking about paying him to do it. We agreed that a pound of ground top sirloin would suffice, but I remain concerned about his cholesterol intake. Your diet I’m not going to fret over, and I suspect someone can do a better job than he anyway.

Therefore, I am starting a little bounty to clean up this plug-in. Requirements are simple: 1) fix all the bugs listed in the plug-in directory and note it (however that happens is beyond me); 2) deliver a zip file of the updated plug-in to myself and the WordPress community for testing (on the latter part, again clueless as to how that happens) deliver the changes directly to either Will or Alan (who will have them committed); and 3) have a Paypal account ready so I can pay you. I’m committing $25, and if anyone else wants to make a contribution, note that and the amount in the comments. In addition, it wouldn’t be very cost efficient to rack up duplicative Paypal charges for the purpose of consolidating payment though me, so please be prepared to pay up directly – I know there is honor among open source developers, and there sure as hell better be among those that use their fine work.

That’s it, and thanks in advance.

NOTE: This bounty is in no way affiliated with the OpenID code bounty, nor do I wish to infer that it is. There has been some discussion about including OpenID in the WordPress core, but for now it seems it will remain a plug-in. The intention here is to help ensure those plug-ins are ready and available for all WordPress users.

RUNNING UPDATE: The bounty is up to $50.

UPDATE: See comments for additional information.


I’d personally be willing to throw in $25 as well.

Michael Gracie says:

David, thanks very much.

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. 🙂

Michael Gracie says:

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.

Michael Gracie says:

I’ve just found this as well: (h/t to Mashable).

Sounds sketchy. Any thoughts?

[…] 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+ […]

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.