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"?
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. 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. So -1 unless I hear a compelling argument as to why we need to do this right now. -DeWitt On Wed, Dec 17, 2008 at 6:36 PM, Scott Kveton <[email protected]> wrote: > > PHP version seems to be running fine, why Ruby-on-Rails really? Of course > > getting it fixed is perhaps a good thing too....just wondering, is there > a > > high usage/interest in rails? > > The membership software for the OIDF is written in Rails. > > I can't speak to the usage/interest in Rails as a platform but it > seems to be rather prevalent (like frameworks for PHP, Django for > Python, etc). > > - Scott > > > > > > On 12/18/2008 04:30 AM, Scott Kveton: > > > > Sorry for the all-caps ... just trying to get folks attention. > > > > RPX was deployed onto the OIDF members page earlier this month and > > there were a few concerns around the use of a non-vendor neutral > > technology for something like foundation voting. In addition, the > > Ruby plugin for OpenID has not be upgraded to meet the 2.0 > > specification needs. It was agreed to leave RPX in place until the > > end of the election but I'd like to make a motion around fixing the > > plugin and putting the membership software back where it was: > > > > As per the attached proposal I would like the OIDF to engage Refresh > > Media to update the Rails OpenID plugin and then deploy the OpenID > > 2.0-compliant version for the membership system. Total cost will be > > $1500-$2000 and the patches to the plugin will be submitted back to > > the Ruby community as open source and available for all Rails users. > > This motion will require responses from 7 board members with at least > > 4 +1's (57.1% in favor) from those responses by Wednesday 12/24/2008. > > > > - Scott > > > > > > ________________________________ > > _______________________________________________ > > board mailing list > > [email protected] > > http://openid.net/mailman/listinfo/board > > > > > > _______________________________________________ > > board mailing list > > [email protected] > > http://openid.net/mailman/listinfo/board > > > > > _______________________________________________ > board mailing list > [email protected] > http://openid.net/mailman/listinfo/board >
_______________________________________________ board mailing list [email protected] http://openid.net/mailman/listinfo/board
