Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 21
Next checkpoint: 2011-11-16
Scope
Out of scope
- Bug linking will now be a separate project
Deliverables
Item |
Owner |
Expected date |
Status |
Signed off LEPs |
jml |
|
DONE |
sinzui |
2011-09-21 |
DONE |
|
sinzui |
2011-10-13 |
DONE |
|
sinzui |
2011-11-30 |
DEVELOPMENT |
|
Harden bugs and teams |
sinzui |
2011-11-16 |
DEVELOPMENT |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Feature documentation |
danhg |
|
|
Blog post |
danhg |
|
|
Action items for next checkpoint
- [huwshimi] Produce new mockups around security/privacy policy conundrum (options for one or two pages) TODO
- [danhg] User-test the mock-ups TODO
- [purple] Settle what are the requirements from stakeholders before we can turn-off the multi-tenancy feature for private bugs. DONE
- [purple] Send the PPA clean-up email TODO
- [purple] Change the policy around hiding own bug comment. TODO
- [purple] Add AJAX ui to delete bug task TODO
- [purple] Create report around branch privacy multi-tenancy. TODO
- [purple] Add and enable footgun feature flag to reduce growing the number of private bugs with multiple projects.
- [purple] Creating the access policy mechanism TODO
- [purple] Populating and maintaining the access policy data TODO
- [purple] Implement the +manage-disclosure UI
- [purple] Turn on +manage-disclosure and security through the access policy TODO
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
- Target picker
- Person picker: invite beta feedback
Exploratory testing
https://dev.launchpad.net/QA/ExploratoryTesting/Disclosure/TrustedPickers
- Daily testing by matsubara sent to the ~launchpad-dev list
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