launchpad development|
Size: 3185
Comment:
|
Size: 3396
Comment: Updated based on checkpoint meeting
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| '''Current week:''' 19<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-10-19 |
'''Current week:''' 21<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-16 |
| Line 28: | Line 29: |
| || [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-10-19 || DEVELOPMENT || || +manage-disclosure design || huwshimi, wallyworld, jcsackett || 2011-10-05 || DONE || || +manage-disclosure alpha (minus search) || huwshimi, wallyworld, jcsackett || 2011-10-19 || || || [[LEP/SocialPrivateTeams | social private teams]] || || 2011-10-19 || DEVELOPMENT || || [[LEP/ManagingDisclosure#granting|Granting disclosure]] || || || || || [[LEP/ManagingDisclosure#seeing|Seeing disclosure]] || || || || || [[LEP/ManagingDisclosure#withdrawing|Withdrawing disclosure]] || || || || |
|| [[LEP/ManagingDisclosure|Managing disclosure]] ||sinzui || 2011-11-30 || DEVELOPMENT || || Harden bugs and teams || sinzui || 2011-11-16 || DEVELOPMENT || || [[LEP/SocialPrivateTeams | social private teams]] || || || || |
| Line 38: | Line 35: |
| || Feature documentation || mrevell || || || || Blog post || mrevell || || || |
|| 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] Fix the bug that prevents admins from setting privileged bug status. TODO * [purple] Review the split script and get agreement from stakeholders on its output so that we can run it unattended. TODO * [purple] Settle what are the requirements from stakeholders before we can turn-off the multi-tenancy feature for private bugs. TODO * [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] Remove multi-tenancy around bug privacy. TODO |
| Line 43: | Line 55: |
| * Curtis is starting work on social private teams * The +manage-disclosure page should be ready as an alpha for the 2011-10-19 checkpoint * We will use UDS to research private teams * Private questions were expected early October (now unlikely). In prepartion, an admin can remove a question subscriber. |
<<PageList(regex:^LEP/Disclosure/Checkpoint-*)>> |
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] Fix the bug that prevents admins from setting privileged bug status. TODO
- [purple] Review the split script and get agreement from stakeholders on its output so that we can run it unattended. TODO
- [purple] Settle what are the requirements from stakeholders before we can turn-off the multi-tenancy feature for private bugs. TODO
- [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] Remove multi-tenancy around bug privacy. 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
