LoCo events are often about reaching out to new users. I don't see any reason why we should require new users to not only create an Ubuntu SSO account (which is broken and not supported on the LoCo directory), or a Launchpad account (which is a software developer service) and then join a Launchpad team when they may or may not have anything to do with the LoCo.
And this is just to RSVP! This would be a horrible introduction to a new or potential Ubuntu user who was curious about "this Ubuntu thing" and just wanted to sign up. Especially if that attitude is "If you're not a locoteam member you have no business RSVPing on the LoCo directory". If that's the case, then I would actually consider the LoCo Directory project harmful to the kind of open attendance events I usually plan and would stop using the directory altogether. Please consider the intended audience of the directory when dealing with this bug. -- User referred to as "openiduser44" in event RSVP https://bugs.launchpad.net/bugs/574049 You received this bug notification because you are a member of loco- directory-dev, which is the registrant for loco-directory. Status in LoCo Directory: Triaged Bug description: I noticed that there's a user on one of my team's events -- http://loco.ubuntu.com/events/team/99/detail/ -- referred to as "openiduser44". Since there isn't a Launchpad user with that name, I'm rather confused as to who that person could be. If it's a Launchpad user, their actual username should be there; if LoCo Directory allows login from non-LP OpenIDs, those OpenIDs should be displayed instead of a placeholder username. This would be facilitated by fixing bug 540532 so loco-directory can link to the non-LP OpenID. _______________________________________________ Mailing list: https://launchpad.net/~loco-directory-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~loco-directory-dev More help : https://help.launchpad.net/ListHelp
