I think we need a balance between being useful, reasonable to implement and "best practice". As i said previously, we can't mandate how LoCo teams run their admin, but we can provide a richer experience for their users if they decide to make it open membership.
For my opinion, users have no place adding events or marking attendance if they are not a member of ~locoteams. If the user: A) Hasn't yet joined a LoCo team (giving them membership of ~locoteams), they should be encouraged to do so. B) If a user CAN'T join their LoCo team as it isn't open, then that is an issue at the team level that needs to be resolved - which i see as unrelated to the LoCo Directory. -- If a potential user wants to come, but isn't a member - then i don't think it's unreasonable for them to be a ~locoteam members "Guest". -- 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
