ubuntu-bengali-manual team mailing list archive

[Neal Bussett <neal@xxxxxxxxxxx>]

There's no reason for a team to be an open team.

There's even less reason to restrict event attendance to members of that
team.  The technical restriction (assuming we want to change nothing
regarding SSOs yet want to always have a 'real' name) is that the user
has a LP profile.  We should not place an artificial restriction above
that.  (I'm not even sure we want to put a hard restriction on that,
perhaps saying "you'll be anonymous if you continue, which isn't as
helpful as creating a LP profile before continuing!" is a better
solution.)

Use case:  User A is a member of LoCo Team B.  She is on travel and
happens to be in the area of LoCo Team C.  She decides to attend that
event and let people know she is coming on the loco directory.

User A is not a member of Team C (she doesn't really have to be a member
of team B either, she might not be 'into' the whole LoCo thing, instead
deciding to spend her time as a developer, MOTU, Marketing Team, Artwork
Team, etc, or even working on some other project that makes use of
launchpad).

-- 
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 Ubuntu
Bengali Manual, which is subscribed to 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.