945
Comment:
|
4511
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
See also [[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=disclosure|disclosure tag]] '''Squad started:''' 2011-05-23<<BR>> '''Current week:''' 15<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-09-21 |
|
Line 5: | Line 10: |
* [[LEP/BugLinking]] | |
Line 14: | Line 18: |
* Private teams work out of scope, except where necessary to enable above * Any complicated bug linking beyond the bare case for cloning |
* Bug linking will now be a separate project |
Line 17: | Line 20: |
== Blockers == | |
Line 19: | Line 21: |
== Special actions == | == Deliverables == |
Line 21: | Line 23: |
* jml to go through LEPs, organize along roadmap lines, convert as many requirements to stories as make sense | || '''Item''' || '''Owner''' || '''Expected date''' || '''Status''' || || Signed off LEPs || jml || || DONE || || [[LEP/TrustedPickers#person-pickers|Person pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=person-picker|person-picker]]) || sinzui || 2011-09-21 || DEVELOPMENT || || [[LEP/TrustedPickers#project-pickers|Target pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=target-picker|target-picker]]) || sinzui || 2011-10-13 || DEVELOPMENT || || [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-09-21 || Privacy ribbon LIVE, otherwise DEVELOPMENT || || [[LEP/ManagingDisclosure#granting|Granting disclosure]] || || || || || [[LEP/ManagingDisclosure#seeing|Seeing disclosure]] || || || || || [[LEP/ManagingDisclosure#withdrawing|Withdrawing disclosure]] || || || || || [[LEP/PrivateProjectsAndDistributions#projects|Private projects]] || || || || || [[LEP/PrivateProjectsAndDistributions#distributions|Private distributions]] || || || || || [[LEP/PrivateProjectsAndDistributions#entitlement|Basic entitlement]] || || || || || Private teams (LEP to come) || || || || || Feature documentation || mrevell || || || || Blog post || mrevell || || || |
Line 23: | Line 38: |
== XXX - missing bits == | == Notes == |
Line 25: | Line 40: |
* Deliverables * Signed off LEPs * Any user testing sessions * Any RTs * Announcement * Maybe feature-level deliverables (e.g. 'person pickers') * Where does exploratory testing go? * Where do mockups go? * Link to bug tag |
* 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 * 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. * Matthew to 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. * Jon is rethinking the picker UI following complaints about how many clicks it takes to make a selection. * Performance woes in both pickers have several delayed the project. * Three people are now working on picker performance. * 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 expected early October. 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 === Still needed === |
Line 35: | Line 76: |
* Turn into template | * Private teams coverage in LEP === 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 |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 15
Next checkpoint: 2011-09-21
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 |
DEVELOPMENT |
|
sinzui |
2011-10-13 |
DEVELOPMENT |
|
|
2011-09-21 |
Privacy ribbon LIVE, otherwise DEVELOPMENT |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Private teams (LEP to come) |
|
|
|
Feature documentation |
mrevell |
|
|
Blog post |
mrevell |
|
|
Notes
- 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
- 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.
- Matthew to 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.
- Jon is rethinking the picker UI following complaints about how many clicks it takes to make a selection.
- Performance woes in both pickers have several delayed the project.
- Three people are now working on picker performance.
- 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 expected early October. 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
Still needed
Somehow fit in two week cycle -- https://wiki.canonical.com/Launchpad/PolicyandProcess/FeatureDevelopment
- Private teams coverage in LEP
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