On 09/18/2012 01:02 PM, Aaron Bentley wrote: >> Not so, the blueprint can be edited to remove the personal >> information about a user. > > This is also true of bugs. We commonly file apprort bugs as private > (user) and then clean them up later, so I don't see how it > demonstrates that a blueprint *cannot* contain private user data. > Maybe the distinction you see is that some bugs *must* contain user data?
While we can hide comment (make the USERDATA) to make a bug public, we cannot make parts of the bug active or comment zero USERDATA. So it is not like blueprints. [aside] Purple added bug task deletion as a means to remove unwanted access to a bug. Maybe we want to support blueprint deletion too. Apport is a nightmare. The Ubuntu community is using Lp as a crash database, then marking user bugs to be duplicates of bugs the user cannot see. The UI warns that this should not be done. Apport needs spanking. -- Curtis Hovey http://launchpad.net/~sinzui
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
