<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Yes, I agree with you in general. If one of the missions of OpenID are
to find a better way and easier to use user interface than this should
be tackled accordingly within the existing framework. This should
include R&D and its targets should be defined, funds allocated etc.
and is a noble goal - go for it!<br>
<br>
If the result of said effort will be usable for the foundation depends
on its vendor neutrality - perhaps the mission itself could strive for
vendor neutrality/implement-ability as well, then it could be
implemented here. However, OIDF is for foundation members, those aren't
the masses and ultimate target perhaps, but those who know about
OpenID, hackers, spec writers, fans and whoever else. I'm certain that
we can handle it the way it worked up to the middle of the election.<br>
<br>
On 12/18/2008 07:58 PM, Brian Kissel:
<blockquote
cite="mid:419E40647338514BBA4F8031282090AE1978F62173@VMBX107.ihostexchange.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
        {mso-style-priority:99;
        mso-style-link:"Plain Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.5pt;
        font-family:Consolas;
        color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        color:black;}
span.PlainTextChar
        {mso-style-name:"Plain Text Char";
        mso-style-priority:99;
        mso-style-link:"Plain Text";
        font-family:Consolas;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">I’m not
insisting on anything.
What I am questioning is whether we can find a way, any way, to make
the UX on
OIDF more intuitive. If Google, Yahoo, AOL, Verisign, Vidoop, or the
OIDF
membership community can come up with a more intuitive way to log into
our
website, I think that’s a win and we should consider those options.
For those
who haven’t talked to hundreds of mainstream RPs (not blogging sites
with tech savvy
users), typing in a URL is not intuitive for the masses. Maybe someday
it will
be, but today it isn’t – period. So it’s all well and good to be
“neutral” but
if we want to drive adoption and usage, we need to respond to what the
market
wants, or at least offer them options that are more compelling than
what they’ve
told us so far is clearly not.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">When we
talked with the former
ED of the Bluetooth SIG, he gave an example about demonstrating
Bluetooth for
press and analysts. The initial demos he gave were using a Toshiba
laptop and
mouse because Toshiba was one of the founding members of the SIG. But
the user
experience at that time was pretty bad with Toshiba, so it didn’t serve
the
purpose of getting press and analysts excited about the reliability and
ease of
use of Bluetooth. He then switched to doing demos with an Apple laptop
and
mouse (even though Apple wasn’t yet a member of the SIG), and the demos
were a
smashing success and resulted in much more favorable press and analysts
coverage.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">All I’m
saying is that we can’t
be dogmatic, we need to think about what our mission is, then make sure
we’ve
evaluated the best ways to achieve our mission. If we can drive
adoption and
usage equally well with a “neutral” approach to everything we do on our
website, with press & analysts, etc. that’s great. But I think
we’ll find
over time that we need to be pragmatic and make tradeoffs. We recently
moved
our wiki to PB Wiki which is provided by a vendor, presumably because
it gave
us the functionality we needed at a reasonable cost. We didn’t write
our own
wiki software. Many of the committees are using Google docs for
collaboration,
and that’s OK.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">We have a
lot of creative
members of the OIDF, why don’t we ask them how to improve the UX of the
OIDF
website login in a way that will be intuitive for the masses that we
ultimately
hope to serve? If we’re going to spend $2K, I’d advocate spending it
on
implementing that UX.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color: navy;">Cheers,</span><span
style="color: navy;"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: navy;"><br>
Brian<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="color: navy;">==============<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color: navy;">Brian Kissel<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color: navy;">Cell: 503.866.4424<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="color: navy;">Fax: 503.296.5502<o:p></o:p></span></b></p>
</div>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">
<a class="moz-txt-link-abbreviated" href="mailto:board-bounces@openid.net">board-bounces@openid.net</a>
[<a class="moz-txt-link-freetext" href="mailto:board-bounces@openid.net">mailto:board-bounces@openid.net</a>] <b>On Behalf Of </b>Eddy Nigg
(StartCom Ltd.)<br>
<b>Sent:</b> Thursday, December 18, 2008 9:15 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:board@openid.net">board@openid.net</a><br>
<b>Subject:</b> Re: [OpenID board] BOARD VOTE: Motion to update Rails
plugin
andOpenID.net ...<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On 12/18/2008 06:59 PM, Brian Kissel: <o:p></o:p></p>
<p class="MsoPlainText">Agreed there is no consensus on the UX for
OpenID
;-) Not sure there ever will be. And to be clear, I was not
requesting nor advocating paying anything to JanRain, only offering
that we
could do that for free if requested. Seems like the simplest,
quickest,
cheapest thing would be to have Refresh Media put the text box on the
front of
RPX. If AOL were willing to modify their UX at MapQuest to include the
top X (10, 15, 20?) commercial OPs, would that be a better UX? <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom: 12pt;"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";"><br>
Nooooo! Why are you insisting on it? We want an OpenID <b>vendor
neutral</b>
interface. I really don't understand, is this a promotional circus for
commercial providers or is this the OpenID Foundation? My provider
would be
most likely within the top ten or twenty, this isn't the point, it's
about what
a foundation is and represents.<br>
<br>
<o:p></o:p></span></p>
<div>
<table class="MsoNormalTable" cellpadding="0" cellspacing="0"
border="0">
<tbody>
<tr>
<td colspan="2" style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">Regards <o:p></o:p></span></p>
</td>
</tr>
<tr>
<td colspan="2" style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";"> <o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">Signer: <o:p></o:p></span></p>
</td>
<td style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">Eddy
Nigg, <a moz-do-not-send="true" href="http://www.startcom.org">StartCom
Ltd.</a><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">Jabber: <o:p></o:p></span></p>
</td>
<td style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";"><a
moz-do-not-send="true" href="xmpp:startcom@startcom.org">startcom@startcom.org</a><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">Blog: <o:p></o:p></span></p>
</td>
<td style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";"><a
moz-do-not-send="true" href="http://blog.startcom.org">Join the
Revolution!</a><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">Phone: <o:p></o:p></span></p>
</td>
<td style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";">+1.213.341.0390<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td colspan="2" style="padding: 0in;">
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";"> <o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
</div>
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";"><br>
<br>
<br>
__________ Information from ESET NOD32 Antivirus, version of virus
signature
database 3703 (20081218) __________<br>
<br>
The message was checked by ESET NOD32 Antivirus.<br>
<br>
<a moz-do-not-send="true" href="http://www.eset.com">http://www.eset.com</a><o:p></o:p></span></p>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:board@openid.net">board@openid.net</a>
<a class="moz-txt-link-freetext" href="http://openid.net/mailman/listinfo/board">http://openid.net/mailman/listinfo/board</a>
</pre>
</blockquote>
</body>
</html>