Diff for "Projects/Disclosure"

Not logged in - Log In / Register

Differences between revisions 3 and 50 (spanning 47 versions)
Revision 3 as of 2011-06-14 13:55:07
Size: 1284
Editor: jml
Comment:
Revision 50 as of 2011-12-15 14:12:07
Size: 4029
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
'''Squad started:''' 2011-05-23<<BR>>
'''Current week:''' 27<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2012-01-04
Line 7: Line 10:
 * [[LEP/BugLinking]]
Line 12: Line 14:
 * [[LEP/SocialPrivateTeams]]
Line 16: Line 19:
 * Private teams work out of scope, except where necessary to enable above
 * Any complicated bug linking beyond the bare case for cloning
 * Bug linking will now be a separate project
Line 19: Line 21:
== Blockers ==

== Special actions ==

 * jml to go through LEPs, organize along roadmap lines, convert as many requirements to stories as make sense
Line 27: Line 24:
|| Item || Owner || Expected date || Status || || '''Item''' || '''Owner''' || '''Expected date''' || '''Status''' ||
Line 29: Line 26:
|| Person pickers || || 2011-06-16 || INPROGRESS ||
|| Project pickers || || ||
|| Feature documentation || mrevell || || ||
|| Blog post || mrevell || || ||
|| [[LEP/TrustedPickers#person-pickers|Person pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=person-picker|person-picker]]) || sinzui || 2011-09-21 || DONE ||
|| [[LEP/TrustedPickers#project-pickers|Target pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=target-picker|target-picker]]) || sinzui || 2011-10-13 || DONE ||
|| [[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 ||
|| [[LEP/PrivateProjectsAndDistributions#projects|Private projects]] || || || ||
|| [[LEP/PrivateProjectsAndDistributions#distributions|Private distributions]] || || || ||
|| [[LEP/PrivateProjectsAndDistributions#entitlement|Basic entitlement]] || || || ||
|| Feature documentation || danhg || || ||
|| Blog post || danhg || || ||
Line 34: Line 37:
== XXX - missing bits == == Action items for next checkpoint ==
Line 36: Line 39:
 * Deliverables
   * Signed off LEPs
   * Any user testing sessions
   * Any RTs
   * Maybe feature-level deliverables (e.g. 'person pickers')
 * Where does exploratory testing go?
 * Where do mockups go?
 * Somehow fit in two week cycle -- https://wiki.canonical.com/Launchpad/PolicyandProcess/FeatureDevelopment
 * Turn into template
=== 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 ==

<<PageList(regex:^Projects/Disclosure/Checkpoint-*)>>

== 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
 * [[/ManageDisclosureTagsInitialResearch|Dan's rough notes]] from +manage-disclosure with tags for policies paper prototyping research.

=== Exploratory testing ===

 * [[/QA/ExploratoryTesting/Disclosure/TrustedPickers|Trusted pickers]]
 * [[/QA/ExploratoryTesting/Disclosure/ManagingDisclosure|+manage-disclosure mock up testing]]
 * [[QA/ExploratoryTesting/Disclosure/|Bug fixes exploratory testing]]

Disclosure

See also disclosure tag

Squad started: 2011-05-23
Current week: 27
Next checkpoint: 2012-01-04

Scope

Out of scope

Deliverables

Item

Owner

Expected date

Status

Signed off LEPs

jml

DONE

Person pickers (person-picker)

sinzui

2011-09-21

DONE

Target pickers (target-picker)

sinzui

2011-10-13

DONE

social private teams

sinzui

2012-01-04

DEVELOPMENT

Managing disclosure

sinzui

2012-01-18

DEVELOPMENT

Harden bugs and teams

sinzui

2012-02-01

DEVELOPMENT

Private projects

Private distributions

Basic entitlement

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

Resources

User research

Exploratory testing

Projects/Disclosure (last edited 2012-11-07 16:06:12 by flacoste)