On Tue, Sep 21, 2010 at 4:58 PM, Curtis Hovey <[email protected]> wrote: > A Brief Primer on Launchpad Privacy (issue 4) > ============================================= > > Private Primary Contexts > ------------------------ > > A private project, distro, project group, team, meeting or possibly user may > have any Launchpad ID. The "private" name prefix used by private teams was > rejected by team owners; no person was concerned about other users guessing > their names through deduction during the registration process. We can consider > requiring a private prefix if Canonical and its partners request it. >
They'll have to fight very hard for it. If people want unguessable names, they should come up with unguessable names. I understand the motivations for the current "private-" prefix – it served us well in its time – but it looks ugly and sloppy and I would very much like to see it go away. > > Project Groups > .............. > ... > Project Groups are problematic and several issues must be fixed before privacy > can be added. ... Perhaps now is the time to change the way they work. However, if we do so, I'd rather we do it explicitly as a thing separate from the privacy work, and make the privacy requirements part of the more general requirements for project group behavior. > > User and Meetings > ................. > > Users and meetings qualify to support privacy because of the primary context > rule. We do not have any use cases for a private person, so there is no > immediate plans to implement privacy for users. There have been requests > to support private meetings (sprints). We do not have immediate plans > to add privacy, but it can be considered. > Add privacy. To me, this privacy project is about getting our privacy story consistent and complete. jml _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
