On Saturday 06 November 2010 19:56:39 Martin Pool wrote: > On 29 October 2010 12:47, Julian Edwards <[email protected]> wrote: > > I don't think a fixed policy is useful. Privacy can mean either > > a) existence is hidden > > b) contents are hidden > > > > I've seen a combination of these used in different places and it makes > > sense to decide which one you need at the time it's being implemented. > > I don't think a single fixed policy will do either. I think having a > set of policies and principles about when they are used could be good, > for the sake of consistency across the application and for the sake of > user understandability. It can be hard to reason about who does or > does not have access to something at the moment.
Another thing we really ought to be doing is to indicate in the UI if you are seeing something that other people cannot see, because right now you have no idea if it's private or not. This will prevent inadvertent slip ups where an admin could talk about something on his screen that nobody else should know about. _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
