So the Rails part is incidental, right? Thus the motion could be rephrased as "pay Refresh Media $2k to upgrade their plugin to support OpenID 2.0 and, as per the usual arrangement, open source the code"?<br><br>
If so, I have no objections to that motion per se, but I'd also say a) the executive committee should be able to authorize this spending out of a pre-approved budget and hence it shouldn't need a board vote, and b) I'd rather us not vote on anything non-critical until the incoming BoD is in place in a couple of weeks. <br>
<br>I very much like Brian's earlier point about making sure that the new ED and incoming board have as much of a budget to work with as possible.<br><br>So -1 unless I hear a compelling argument as to why we need to do this right now.<br>
<br>-DeWitt<br><br><div class="gmail_quote">On Wed, Dec 17, 2008 at 6:36 PM, Scott Kveton <span dir="ltr"><<a href="mailto:scott@kveton.com">scott@kveton.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">> PHP version seems to be running fine, why Ruby-on-Rails really? Of course<br>
> getting it fixed is perhaps a good thing too....just wondering, is there a<br>
> high usage/interest in rails?<br>
<br>
</div>The membership software for the OIDF is written in Rails.<br>
<br>
I can't speak to the usage/interest in Rails as a platform but it<br>
seems to be rather prevalent (like frameworks for PHP, Django for<br>
Python, etc).<br>
<font color="#888888"><br>
- Scott<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
<br>
> On 12/18/2008 04:30 AM, Scott Kveton:<br>
><br>
> Sorry for the all-caps ... just trying to get folks attention.<br>
><br>
> RPX was deployed onto the OIDF members page earlier this month and<br>
> there were a few concerns around the use of a non-vendor neutral<br>
> technology for something like foundation voting. In addition, the<br>
> Ruby plugin for OpenID has not be upgraded to meet the 2.0<br>
> specification needs. It was agreed to leave RPX in place until the<br>
> end of the election but I'd like to make a motion around fixing the<br>
> plugin and putting the membership software back where it was:<br>
><br>
> As per the attached proposal I would like the OIDF to engage Refresh<br>
> Media to update the Rails OpenID plugin and then deploy the OpenID<br>
> 2.0-compliant version for the membership system. Total cost will be<br>
> $1500-$2000 and the patches to the plugin will be submitted back to<br>
> the Ruby community as open source and available for all Rails users.<br>
> This motion will require responses from 7 board members with at least<br>
> 4 +1's (57.1% in favor) from those responses by Wednesday 12/24/2008.<br>
><br>
> - Scott<br>
><br>
><br>
> ________________________________<br>
> _______________________________________________<br>
> board mailing list<br>
> <a href="mailto:board@openid.net">board@openid.net</a><br>
> <a href="http://openid.net/mailman/listinfo/board" target="_blank">http://openid.net/mailman/listinfo/board</a><br>
><br>
><br>
> _______________________________________________<br>
> board mailing list<br>
> <a href="mailto:board@openid.net">board@openid.net</a><br>
> <a href="http://openid.net/mailman/listinfo/board" target="_blank">http://openid.net/mailman/listinfo/board</a><br>
><br>
><br>
_______________________________________________<br>
board mailing list<br>
<a href="mailto:board@openid.net">board@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/board" target="_blank">http://openid.net/mailman/listinfo/board</a><br>
</div></div></blockquote></div><br>