All ubuntu users *are* welcome. The LoCo Directory design is based on
the fact that there are underlying Launchpad teams to arrange the users.
Whilst nobody is saying a LoCo *needs* to make use of Launchpad for this
feature, I have no issues with maintaining the approach of getting a
richer experience if teams do.
The LoCo Directory should strive to be as inclusive as possible, but
LoCo's are not mandated to use it.
I further suggest:
-> Login
If member of ~locoteams: proceed
else: redirect to page suggesting join.
LoCo Directory being a LoCo resource, if attendee's aren't a member of a
LoCo; then I would suggest they are 'invited' by members of the LoCo and
use the "guests" feature.
If this bug is fixed in this manner, I would suggest opening a new bug
of "Ability to mark attending an event, if not a LoCo member", and these
users are shown in a separate table.
--
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
