3185
Comment:
|
3701
|
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-02 |
Line 28: | Line 28: |
|| [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-10-19 || DEVELOPMENT || | || [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-11-02 || DEVELOPMENT || |
Line 30: | Line 30: |
|| +manage-disclosure alpha (minus search) || huwshimi, wallyworld, jcsackett || 2011-10-19 || || || [[LEP/SocialPrivateTeams | social private teams]] || || 2011-10-19 || DEVELOPMENT || |
|| +manage-disclosure alpha (minus search) || huwshimi, wallyworld, jcsackett || 2011-11-02 || || || [[LEP/SocialPrivateTeams | social private teams]] || || || STALLED || |
Line 38: | Line 38: |
|| Feature documentation || mrevell || || || || Blog post || mrevell || || || |
|| Feature documentation || danhg || || || || Blog post || danhg || || || Outcome of 2011-10-19 check-point: * 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 |
Line 43: | Line 48: |
* 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. |
* 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. |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 21
Next checkpoint: 2011-11-02
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-11-02 |
DEVELOPMENT |
|
+manage-disclosure design |
huwshimi, wallyworld, jcsackett |
2011-10-05 |
DONE |
+manage-disclosure alpha (minus search) |
huwshimi, wallyworld, jcsackett |
2011-11-02 |
|
|
|
STALLED |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Feature documentation |
danhg |
|
|
Blog post |
danhg |
|
|
Outcome of 2011-10-19 check-point:
- 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
Notes
- 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.
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