launchpad development|
Size: 3413
Comment:
|
Size: 4029
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| '''Current week:''' 25<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-12-14 |
'''Current week:''' 27<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2012-01-04 |
| Line 28: | Line 28: |
| || Harden bugs and teams || sinzui || 2011-12-14 || DEVELOPMENT || || [[LEP/ManagingDisclosure|Managing disclosure]] ||sinzui || 2012-01-30 || DEVELOPMENT || || [[LEP/SocialPrivateTeams | social private teams]] || || || || |
|| [[LEP/SocialPrivateTeams | social private teams]] || sinzui || 2012-01-04 || DEVELOPMENT || || [[LEP/ManagingDisclosure|Managing disclosure]] ||sinzui || 2012-01-18 || DEVELOPMENT || || Harden bugs and teams || sinzui || 2012-02-01 || DEVELOPMENT || |
| Line 48: | Line 48: |
| * [danhg] User-test the dynamic +managing-disclosure mock-ups * [huwshimi] Should we change the bug tags to look like these new tags? * [purple] Implement a draft +manage-disclosure UI |
* [purple] Implement tweaked +manage-disclosure clickable mock-up * [danhg] User-test the tweaked clickable +managing-disclosure mock-ups |
| Line 52: | Line 51: |
| * [huwshimi]: speak to sinzui about how to present embargoed security bugs in the UI * [danhg]: speak to sinzui to then rewrite the privacy ribbon messages to take account of the new situations it must handle * [EVERYONE!]: we will refer to "Sharing" rather than "Disclosure" * [purple]: replace references to "disclosure" with "sharing" === Social private teams === * Purple: PPA subscribers should have access to only the archive itself * Purple: Subscribers to a private team's branch should be permitted to see the branch and its merge proposals * Purple: priv teams can be package maintainers * Purple: priv teams can subscribe to blueprints * Purple: priv teams can subscribe to bugs * Purple: we will fix the situation where you can lose access to your private team * Purple: warn in the picker when you're about to expose the name of a private team * huwshimi: speak to jcsackett about the design of the warning * danhg: test the warnings |
|
| Line 75: | Line 92: |
=== 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 |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 27
Next checkpoint: 2012-01-04
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-01-04 |
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
- [purple] Modify the footgun feature flag to keep multi-tenancy for security bugs.
- [purple] Enable footgun feature flag to reduce growing the number of private bugs with multiple projects
Manage disclosure
- [purple] Implement tweaked +manage-disclosure clickable mock-up
- [danhg] User-test the tweaked clickable +managing-disclosure mock-ups
- [purple] Populating and maintaining the access policy data
- [huwshimi]: speak to sinzui about how to present embargoed security bugs in the UI
- [danhg]: speak to sinzui to then rewrite the privacy ribbon messages to take account of the new situations it must handle
- [EVERYONE!]: we will refer to "Sharing" rather than "Disclosure"
- [purple]: replace references to "disclosure" with "sharing"
Social private teams
- Purple: PPA subscribers should have access to only the archive itself
- Purple: Subscribers to a private team's branch should be permitted to see the branch and its merge proposals
- Purple: priv teams can be package maintainers
- Purple: priv teams can subscribe to blueprints
- Purple: priv teams can subscribe to bugs
- Purple: we will fix the situation where you can lose access to your private team
- Purple: warn in the picker when you're about to expose the name of a private team
- huwshimi: speak to jcsackett about the design of the warning
- danhg: test the warnings
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.
