launchpad development|
Size: 4483
Comment:
|
Size: 3185
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| '''Current week:''' 17<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-10-05 |
'''Current week:''' 19<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-10-19 |
| Line 28: | Line 28: |
| || [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-09-22 || READY FOR SIGNOFF || || +manage-disclosure design || huwshimi, wallyworld, jcsackett || 2011-10-05 || || |
|| [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-10-19 || DEVELOPMENT || || +manage-disclosure design || huwshimi, wallyworld, jcsackett || 2011-10-05 || DONE || |
| Line 31: | Line 31: |
| || [[LEP/SocialPrivateTeams | social private teams]] || || 2011-10-19 || || | || [[LEP/SocialPrivateTeams | social private teams]] || || 2011-10-19 || DEVELOPMENT || |
| Line 43: | Line 43: |
| * 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. |
* Curtis is starting work on social private teams * The +manage-disclosure page should be ready as an alpha for the 2011-10-19 checkpoint |
| Line 49: | Line 46: |
| * 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 |
|
| Line 57: | Line 47: |
| * 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 |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 19
Next checkpoint: 2011-10-19
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-10-19 |
DEVELOPMENT |
|
+manage-disclosure design |
huwshimi, wallyworld, jcsackett |
2011-10-05 |
DONE |
+manage-disclosure alpha (minus search) |
huwshimi, wallyworld, jcsackett |
2011-10-19 |
|
|
2011-10-19 |
DEVELOPMENT |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Feature documentation |
mrevell |
|
|
Blog post |
mrevell |
|
|
Notes
- 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.
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
