Disclosure

Scope

jml to go through LEPs, organize along roadmap lines, convert as many requirements to stories as make sense

Person pickers
Project / distribution pickers
As a developer, I want to be able to clone a bug from one project to another project so that I can have separate conversations about the bug, each with their own disclosure level
As a project owner, I want to see who has access (is subscribed to) private bugs and branches within my project, so that I can make sure that everyone who needs to have access has it, and no one who shouldn’t doesn’t.
(2 cycles) As a project owner, I want to give users permission to see all of the private items in my project so that I have a simple way to induct new members into my private project.
As a project owner, I want to see users with permission to see all of the private items in my project so that I can maintain control over who has access to my project.
As a project owner, I want to prevent a user from accessing to my project or a bug/branch, so that private information is not disclosed and that owners can respond to a disclosure issue immediately
(2 cycles) alpha level, opt-in only private projects
Private distributions
As a person with rights over a blacklisted name, I want to create a private project or distribution with a blacklisted name without any Launchpad admin intervention or any other privileges, so that I can just get my stuff done and not accidentally destroy everything

Deliverables
- Any user testing sessions
- Any RTs
- Maybe feature-level deliverables (e.g. 'person pickers')
Where does exploratory testing go?
Where do mockups go?
Somehow fit in two week cycle -- https://wiki.canonical.com/Launchpad/PolicyandProcess/FeatureDevelopment
Turn into template