• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

Disclosure

See also disclosure tag

Squad started: 2011-05-23
Current week: 4
Next checkpoint: 2011-06-15

Scope

• LEP/BugLinking

• LEP/ManagingDisclosure

• LEP/PrivateProjectsAndDistributions

• LEP/TrustedPickers

• LEP/BetterPrivacy

Out of scope

• LEP/AuditTrail

• Private teams work out of scope, except where necessary to enable above
• Any complicated bug linking beyond the bare case for cloning

Blockers

• Open questions on LEP/BugLinking

Special actions

• jml to create a project picker LEP
• jml to go through LEPs, organize along roadmap lines, convert as many requirements to stories as make sense

• jml & sinzui to resolve open questions on LEP/BugLinking

Deliverables

Notes

• At each checkpoint, make sure to go over LEP/BetterPrivacy and mark off which requirements have been met

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

Still needed

• Link to exploratory testing
• Link to mockups

• Somehow fit in two week cycle -- https://wiki.canonical.com/Launchpad/PolicyandProcess/FeatureDevelopment

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