Requiring loco teams membership IMHO is stupid. We already require users to use launchpad's openid provider instead of any open id provider (even for users simply trying to confirm their attendance to an event)
Event attendance and other admin functions should not be related. I think (although this might be a different bug) we need to allow ANY openid provider for users to sign up for events. (If we want events with big turn outs) My understanding of the using the loco directory instead of FB and Gcal would be some sort of openness in some form or manner limiting users to LP (for none admin functions) seems to defeat the point of this. Either way this is a bug and effects my team as well and I would love to know how they event got to the "openiduser" status?? http://loco.ubuntu.com/events/team/666/detail/ -- You received this bug notification because you are a member of loco- directory-dev, which is the registrant for loco-directory. https://bugs.launchpad.net/bugs/574049 Title: User referred to as "openiduser44" in event RSVP 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
