Differences between revisions 1 and 52 (spanning 51 versions)

Disclosure

Scope

Out of scope

LEP/AuditTrail
Bug linking will now be a separate project

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
[mrevell]: Agree on the terminology and mutural exclusivity behaviour of security/propietary bugs. Respond to Curtis' email on the list.

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
[mrevell]: seek agreement from stakeholders on how adding a private team to a private team should work
[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)

Actions for later

[purple] Turn on +manage-disclosure and security through the access policy: LATER

Notes

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.

-  ⇤ ← Revision 1 as of 2011-06-14 12:25:03 → 
  Size: 531
  Editor: jml
  Comment:
+   ← Revision 52 as of 2011-12-15 15:55:43 → ⇥
  Size: 4455
  Editor: matthew.revell
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 3:
+See also [[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=disclosure|disclosure tag]]

'''Squad started:''' 2011-05-23<<BR>>
'''Current week:''' 27<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2012-01-04
-Line 5:
+Line 10:
- * [[LEP/BugLinking]]
-Line 10:
+Line 14:
+ * [[LEP/SocialPrivateTeams]]
-Line 14:
+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 17:
+Line 21:
-== Blockers ==
-Line 19:
+Line 22:
-== Special actions ==
+== Deliverables ==
-Line 21:
+Line 24:
- * jml to go through LEPs, organize along roadmap lines, convert as many requirements to stories as make sense
+|| '''Item''' || '''Owner''' || '''Expected date''' || '''Status''' ||
|| Signed off LEPs || jml || || DONE ||
|| [[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 || || ||

== 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
  * [mrevell]: Agree on the terminology and mutural exclusivity behaviour of security/propietary bugs. Respond to Curtis' email on the list.

=== 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
 * [mrevell]: seek agreement from stakeholders on how adding a private team to a private team should work
 * [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)

 

== 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]]

launchpad development

Diff for "Projects/Disclosure"

Disclosure

Scope

Out of scope

Deliverables

Action items for next checkpoint

Harden bugs and teams

Manage disclosure

Social private teams

Actions for later

Notes

Resources

User research

Exploratory testing