launchpad development|
Size: 3817
Comment:
|
Size: 3576
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| '''Current week:''' 27<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2012-01-04 |
'''Current week:''' 31<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2012-02-01 |
| Line 28: | Line 28: |
| || [[LEP/SocialPrivateTeams | social private teams]] || sinzui || 2012-01-04 || DEVELOPMENT || | || [[LEP/SocialPrivateTeams | social private teams]] || sinzui || 2012-02-01 || DEVELOPMENT || |
| Line 41: | Line 41: |
| * [danhg] Announcement based on the language and introducing proprietary bugs and branches. | * [danhg] and [sinzui]: Blog post based on Curtis's email abot language and introducing proprietary bugs and branches. |
| Line 45: | Line 45: |
| * [purple] Produce tweaked +manage-sharing clickable mock-up * [danhg] User-test the tweaked clickable +managing-sharing mock-ups * [huwshimi] Review revised clickable mock-up and suggest any necessary changes. * [purple] Populating and maintaining the access policy data * [danhg]: speak to sinzui to then rewrite the privacy ribbon messages to take account of the new situations it must handle * For later: record and warn the user about disclosing private teams to private projects. Precisely state that you are exposing your team to a project only. * [mrevell] When the warnings are ready (see above), test with stakeholders. |
* [danhg]: Another round of testing on the clickable mock-up * [danhg]: Propose further testing of flat mock-ups, dependent on results of the clickable testing * [purple] Populating and maintaining the access policy data * [purple]: change the ribbon wording when the ENUMs are in the database. * [purple] For later: record and warn the user about disclosing private teams to private projects. Precisely state that you are exposing your team to a project only. * [mrevell] When the warnings are ready (see above), test with stakeholders. |
| Line 55: | Line 54: |
| * [purple]: UI ready to be signed off * [mrevell]: UI signed off * [danhg]: what should someone who is not a member of a private team see when they visit that private team's overview page? Dan to gather data. (bug 904293) |
* [matsubara]: Acceptance testing |
| Line 65: | Line 62: |
| * [wgrant] Dirt cheap entitlement coming | * [purple] Dirt cheap entitlement coming. SteveK likely to start. |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 31
Next checkpoint: 2012-02-01
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 |
2012-02-01 |
DEVELOPMENT |
|
sinzui |
2012-01-18 |
DEVELOPMENT |
|
Harden bugs and teams |
sinzui |
2012-02-01 |
DEVELOPMENT |
|
|
|
|
|
|
|
|
|
|
|
|
Feature documentation |
danhg |
|
|
Blog post |
danhg |
|
|
Action items for next checkpoint
Harden bugs and teams
- [danhg] and [sinzui]: Blog post based on Curtis's email abot language and introducing proprietary bugs and branches.
Manage disclosure
- [danhg]: Another round of testing on the clickable mock-up
- [danhg]: Propose further testing of flat mock-ups, dependent on results of the clickable testing
- [purple] Populating and maintaining the access policy data
- [purple]: change the ribbon wording when the ENUMs are in the database.
- [purple] For later: record and warn the user about disclosing private teams to private projects. Precisely state that you are exposing your team to a project only.
- [mrevell] When the warnings are ready (see above), test with stakeholders.
Social private teams
- [matsubara]: Acceptance testing
Private projects
- [mrevell] Check with Danilo if private projects are still necessary to them.
Entitlement
- [purple] Dirt cheap entitlement coming. SteveK likely to start.
Actions for later
- [purple] Turn on +manage-disclosure and security through the access policy: LATER
Notes
- Projects/Disclosure/Checkpoint-2011-11-02
- Projects/Disclosure/Checkpoint-2011-11-16
- Projects/Disclosure/Checkpoint-2011-11-30
- Projects/Disclosure/Checkpoint-2011-12-14
- Projects/Disclosure/Checkpoint-2012-01-19
- Projects/Disclosure/Checkpoint-2012-02-01
- Projects/Disclosure/Checkpoint-2012-02-15
- Projects/Disclosure/Checkpoint-2012-02-29
- Projects/Disclosure/Checkpoint-2012-03-14
- Projects/Disclosure/Checkpoint-2012-03-29
- Projects/Disclosure/Checkpoint-2012-04-25
- Projects/Disclosure/Checkpoint-2012-06-06
- Projects/Disclosure/Checkpoint-2012-07-05
- Projects/Disclosure/Checkpoint-2012-08-29
- Projects/Disclosure/Checkpoint-2012-09-14
- Projects/Disclosure/Checkpoint-2012-09-26
- Projects/Disclosure/Checkpoint-2012-10-10
- Projects/Disclosure/Checkpoint-2012-11-07
- Projects/Disclosure/Checkpoint-2012-11-21
- Projects/Disclosure/Checkpoint-2012-12-05
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
Dan's rough notes from +manage-disclosure with tags for policies paper prototyping research.
