launchpad development|
Size: 4497
Comment:
|
Size: 4455
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 27: | Line 27: |
| || [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-09-21 || Privacy ribbon LIVE, otherwise DEVELOPMENT || | || [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-09-22 || READY FOR SIGNOFF || || +manage-disclosure design || huwshimi, wallyworld, jcsackett || 2011-10-05 || || || +manage-disclosure alpha (minus search) || huwshimi, wallyworld, jcsackett || 2011-10-19 || || || Private teams and nested private teams (LEP to come) || || 2011-10-19 || || |
| Line 31: | Line 34: |
| || Private teams (LEP to come) || || || || | |
| Line 40: | Line 42: |
| * We have placed a hard cut-off of 2011-09-21 on picker work: any non-Critical bugs will be picked up by the maintenance squad following feature delivery * Filtering of picker results has gone well * Affiliation information will return to pickers soon |
* Pickers will be ready for mrevell's sign-off on 2011-09-22. * wgrant, stevenk and lifeless will start work on nested private teams. * huwshimi, wallyworld and jcsackett will produce a design for +manage-disclosure pages and then implement it. |
| Line 47: | Line 49: |
| * Matthew to write a LEP | * Curtis will write a LEP |
| Line 50: | Line 52: |
| * Jon is rethinking the picker UI following complaints about how many clicks it takes to make a selection. | |
| Line 52: | Line 53: |
| * Three people are now working on picker performance. | |
| Line 55: | Line 55: |
| * Private questions expected early October. In prepartion, an admin can remove a question subscriber. | * Private questions were expected early October (now unlikely). In prepartion, an admin can remove a question subscriber. |
| Line 72: | Line 72: |
| * Daily testing by matsubara sent to the ~launchpad-dev list | |
| Line 74: | Line 75: |
* Somehow fit in two week cycle -- https://wiki.canonical.com/Launchpad/PolicyandProcess/FeatureDevelopment * Private teams coverage in LEP |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 17
Next checkpoint: 2011-10-05
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 |
|
|
2011-09-22 |
READY FOR SIGNOFF |
|
+manage-disclosure design |
huwshimi, wallyworld, jcsackett |
2011-10-05 |
|
+manage-disclosure alpha (minus search) |
huwshimi, wallyworld, jcsackett |
2011-10-19 |
|
Private teams and nested private teams (LEP to come) |
|
2011-10-19 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Feature documentation |
mrevell |
|
|
Blog post |
mrevell |
|
|
Notes
- Pickers will be ready for mrevell's sign-off on 2011-09-22.
- wgrant, stevenk and lifeless will start work on nested private teams.
- huwshimi, wallyworld and jcsackett will produce a design for +manage-disclosure pages and then implement it.
- William is working on showing who can see private artefacts associated with a project. As a result, he is also making super fast all queries relating to privacy and Ubuntu.
- Curtis is working on fixing the problem where changing a bug's privacy or security status doesn't yet automatically subscribe/unsubscribe the relevant people.
- We will use UDS to research private teams
- Private teams are now officially in-scope, following a period where they were tacitly in-scope due to the impact our failing team privacy has on other aspects of the Disclosure project.
- Curtis will write a LEP
- Team privacy is relatively easy, except for nesting private teams inside public teams, which will be a little more complicated to handle.
- Curtis expects that tackling private teams will add six weeks to the Managing Disclosure project.
- Performance woes in both pickers have several delayed the project.
- The privacy ribbon is now live and appears to function well
- Stakeholders might not consider this project complete if team privacy is not included
- Private questions were expected early October (now unlikely). In prepartion, an admin can remove a question subscriber.
- Decided against allowing hiding of the privacy ribbon.
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
- 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
