#14, @Robert. Someone who has access to private data and is irresponsible or careless is always a danger, no more in this than any other scenario. Obviously private attachments would need to be clearly marked as private.
Why would it be confusing to have attachments marked 'private'? Private means 'private', if someone's confused by the word they can find a dictionary! A private attachment is no more confusing than a private bug. And having public bugs marked as duplicates of private bugs is a LOT more confusing and irritating.
Remco's suggestion (#13) looks excellent to me.
What is really holding back change in this area? Is it the ideas that are not deemed fit for purpose, or is it lack of resources to improve Launchpad?
#14, @Robert. Someone who has access to private data and is irresponsible or careless is always a danger, no more in this than any other scenario. Obviously private attachments would need to be clearly marked as private.
Why would it be confusing to have attachments marked 'private'? Private means 'private', if someone's confused by the word they can find a dictionary! A private attachment is no more confusing than a private bug. And having public bugs marked as duplicates of private bugs is a LOT more confusing and irritating.
Remco's suggestion (#13) looks excellent to me.
What is really holding back change in this area? Is it the ideas that are not deemed fit for purpose, or is it lack of resources to improve Launchpad?