Disclosure

See also disclosure tag

Squad started: 2011-05-23
Current week: 23
Next checkpoint: 2011-11-30

Scope

• LEP/ManagingDisclosure

• LEP/PrivateProjectsAndDistributions

• LEP/TrustedPickers

• LEP/BetterPrivacy

• LEP/SocialPrivateTeams

Out of scope

• LEP/AuditTrail

• Bug linking will now be a separate project

Deliverables

Action items for next checkpoint

Harden bugs and teams

• [purple] Turn off PPA for open teams.
• [purple] Make the delete bugtask UI generally available.
• [purple] Announce the removal of sharing of private bugs.
• [purple] Send an email to people who have shared private bugs about what is going to happen with those bugs.
• [purple] Add and enable footgun feature flag to reduce growing the number of private bugs with multiple projects
• [purple] Create report around branch privacy multi-tenancy

Manage disclosure

• [purple] Implement clickable +managing-disclosure mock-ups
• [danhg] User-test the dynamic +managing-disclosure mock-ups
• [purple] Creating the access policy mechanism
• [purple] Implement the +manage-disclosure UI: LATER
• [purple] Populating and maintaining the access policy data: LATER
• [purple] Turn on +manage-disclosure and security through the access policy: LATER

Notes

Resources

User research

• https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/

• https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/CodySommerville

• https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/SteveMagoun

• Dan's rough notes from +manage-disclosure with tags for policies paper prototyping resaerch.

Exploratory testing

• Trusted pickers

• +manage-disclosure mock up testing

• Bug fixes exploratory testing

Still needed

How are we going to link from deliverables to LEPs?

• User stories in a LEP can be grouped, can be individual. Either way, must be able to be referenced
• A deliverable can correspond to a group of user stories or a single user story
• Product team uses the user stories when evaluating progress on feature