We have all agreed we're not going to do anything until the elections are done, no disagreement.
Nor was I advocating "experimenting" on the OIDF website. I think the question that was originally put to the BOD was should we spend $2K to update the text box implementation to fix the bugs that were reported with i-names and directed identity. There was a lot of discussion about when and whether to spend that $2K, at which point I offered a suggestion to put a different front end on RPX as one alternative, either for the near term (cost deferral) or long term (cost reduction). If neither of those proposals is acceptable, that's fine, it was only a suggestion in response to a lot of dialog on the thread. So if the majority of the board prefers to spend the $2K to fix the text box implementation we had originally, then that's what we should do, and have Refresh Media start soon so that they can make the change as soon as the elections are over. If we want to do something else to save/delay costs, improve the UX, switch vendors from Refresh, etc. then those proposals should be shared with the BOD as well as alternatives to consider. If there are no other proposals to consider, then a simple vote on $2K for Refresh's proposal should wrap this up. Cheers, Brian ============== Brian Kissel Cell: 503.866.4424 Fax: 503.296.5502 From: [email protected] [mailto:[email protected]] On Behalf Of Dick Hardt Sent: Thursday, December 18, 2008 10:44 AM To: [email protected] Cc: larry drebes Subject: Re: [OpenID board] BOARD VOTE: Motion to update Rails plugin andOpenID.net ... On 18-Dec-08, at 10:27 AM, Brian Kissel wrote: I don't know how much more clear I can be. I'm NOT advocating for RPX, I'm advocating for a better UX on the OIDF website. Rip out RPX today, that's fine. Ask the community how we can improve OpenID login on the OIDF website, then get volunteers to implement it or pay Refresh or anyone else to implement it. But let's make the OIDF website a showcase of the goodness of OpenID for users and RPs. Like it or not, the OIDF website is a showcase for the broader market, not just a tool for OIDF members. If we can improve UX and maintain neutrality, great. But let's not sacrifice UX for neutrality if we know that the existing neutral UX is NOT intuitive. Would love to see some ideas on what we could be doing to improve intuitiveness rather than just saying a text box is neutral, so let's just take the easy path and go that way. Would like to hear from some others on how we can improve intuitiveness and whether it's important, not only on our website, but as a fundamental goal for the OIDF. That is more clear -- although your other comments indicate you are justifying why it is ok to use RPX. OpenID UX is an issue. I do NOT think the OIDF website is the place to experiment, particularly during an election process. This is a technical issue -- and the OIDF is there to facilitate resolving the problem -- the Foundation bylaws explicitly forbid the Foundation from directly resolving technical issues. There is pretty active discussion on UX issues on the lists now. I think people are looking at how to solve it -- and there is NO clear solution that has gained consensus. I think we are WAY off topic on this thread now. -- Dick __________ Information from ESET NOD32 Antivirus, version of virus signature database 3703 (20081218) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com
_______________________________________________ board mailing list [email protected] http://openid.net/mailman/listinfo/board
