3769
Comment:
|
3600
|
Deletions are marked like this. | Additions are marked like this. |
Line 6: | Line 6: |
'''Current week:''' 21<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-02 |
'''Current week:''' 23<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-30 |
Line 28: | Line 29: |
|| [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-11-02 || DEVELOPMENT || || +manage-disclosure design || huwshimi, wallyworld, jcsackett || 2011-10-05 || DONE || || +manage-disclosure alpha (minus search) || huwshimi, wallyworld, jcsackett || 2011-11-02 || || || Harden bugs and teams || sinzui || 2011-11-16 || IN PROGRESS || || [[LEP/SocialPrivateTeams | social private teams]] || || || STALLED || || [[LEP/ManagingDisclosure#granting|Granting disclosure]] || || || || || [[LEP/ManagingDisclosure#seeing|Seeing disclosure]] || || || || || [[LEP/ManagingDisclosure#withdrawing|Withdrawing disclosure]] || || || || |
|| Harden bugs and teams || sinzui || 2011-11-30 || DEVELOPMENT || || [[LEP/ManagingDisclosure|Managing disclosure]] ||sinzui || 2011-01-30 || DEVELOPMENT || || [[LEP/SocialPrivateTeams | social private teams]] || || || || |
Line 42: | Line 38: |
Outcome of 2011-10-19 check-point: | == Action items for next checkpoint == |
Line 44: | Line 40: |
* We need a plan for how to tackle social private teams: do we spin it out to another squad? * Jon, Ian and Dan will work on a round of user testing of +manage-disclosure |
=== 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 |
Line 49: | Line 63: |
* Consulting with stakeholders has taken much of the squad's time during this past two weeks. * Stakeholders need to manually clean-up bugs where there's a private bug task on a public bug. Purple have written a script that lets stakeholders delete bug tasks and this needs to be passed to stakeholders with instructions. * Social private teams are hard: * We may want to spin social private teams out to a separate squad * The complexity of private distros is likely to extend this project to April 2012. * The +manage-disclosure page needs another round of user testing. Ian and Jon to lead that with Dan's help. |
<<PageList(regex:^LEP/Disclosure/Checkpoint-*)>> |
Line 65: | Line 72: |
* Target picker * Person picker: invite beta feedback |
* [[/ManageDisclosureTagsInitialResearch|Dan's rough notes]] from +manage-disclosure with tags for policies paper prototyping resaerch. |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 23
Next checkpoint: 2011-11-30
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 |
|
Harden bugs and teams |
sinzui |
2011-11-30 |
DEVELOPMENT |
sinzui |
2011-01-30 |
DEVELOPMENT |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Feature documentation |
danhg |
|
|
Blog post |
danhg |
|
|
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
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