launchpad development|
Size: 2700
Comment:
|
Size: 3978
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| '''Current week:''' 4<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-06-15 |
'''Current week:''' 13<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-09-07 |
| Line 11: | Line 10: |
| * [[LEP/BugLinking]] | |
| Line 21: | Line 19: |
| * Any complicated bug linking beyond the bare case for cloning | * Bug linking will now be a separate project |
| Line 23: | Line 21: |
| == Blockers == * Open questions on [[LEP/BugLinking]] == Special actions == * jml & sinzui to resolve open questions on [[LEP/BugLinking]] |
|
| Line 35: | Line 26: |
| || [[LEP/TrustedPickers#person-pickers|Person pickers]] || || 2011-06-16 || CHECKPOINT || || [[LEP/TrustedPickers#project-pickers|Project pickers]] || || 2011-06-23 || INPROGRESS || || [[LEP/BugLinking#user-stories|Bug cloning]] || || || || [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || || || [[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]] || || || |
|| [[LEP/TrustedPickers#person-pickers|Person pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=person-picker|person-picker]]) || sinzui || 2011-09-07 || BETA-TESTING, UI rethink to reduce clicks to make a selection || || [[LEP/TrustedPickers#project-pickers|Target pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=target-picker|target-picker]]) || sinzui || 2011-09-07 || DEVELOPMENT, performance issues causing delay || || [[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]] || || || || |
| Line 50: | Line 40: |
| * 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 * 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. |
|
| Line 59: | Line 60: |
| * Target picker * Person picker: invite beta feedback === Exploratory testing === * https://dev.launchpad.net/QA/ExploratoryTesting/Disclosure/TrustedPickers |
|
| Line 62: | Line 69: |
| * Link to exploratory testing * Link to mockups |
|
| Line 65: | Line 70: |
| * Private teams coverage in LEP |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 13
Next checkpoint: 2011-09-07
Scope
Out of scope
- Private teams work out of scope, except where necessary to enable above
- Bug linking will now be a separate project
Deliverables
Item |
Owner |
Expected date |
Status |
Signed off LEPs |
jml |
|
DONE |
sinzui |
2011-09-07 |
BETA-TESTING, UI rethink to reduce clicks to make a selection |
|
sinzui |
2011-09-07 |
DEVELOPMENT, performance issues causing delay |
|
|
2011-09-21 |
Privacy ribbon LIVE, otherwise DEVELOPMENT |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Feature documentation |
mrevell |
|
|
Blog post |
mrevell |
|
|
Notes
- 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
- 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
