Diff for "Projects/Disclosure"

Not logged in - Log In / Register

Differences between revisions 2 and 49 (spanning 47 versions)
Revision 2 as of 2011-06-14 12:34:19
Size: 945
Editor: jml
Comment:
Revision 49 as of 2011-11-30 20:03:25
Size: 3413
Editor: flacoste
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
See also [[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=disclosure|disclosure tag]]

'''Squad started:''' 2011-05-23<<BR>>
'''Current week:''' 25<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-12-14
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 ||
|| Harden bugs and teams || sinzui || 2011-12-14 || DEVELOPMENT ||
|| [[LEP/ManagingDisclosure|Managing disclosure]] ||sinzui || 2012-01-30 || DEVELOPMENT ||
|| [[LEP/SocialPrivateTeams | social private teams]] || || || ||
|| [[LEP/PrivateProjectsAndDistributions#projects|Private projects]] || || || ||
|| [[LEP/PrivateProjectsAndDistributions#distributions|Private distributions]] || || || ||
|| [[LEP/PrivateProjectsAndDistributions#entitlement|Basic entitlement]] || || || ||
|| Feature documentation || danhg || || ||
|| Blog post || danhg || || ||
Line 23: Line 37:
== XXX - missing bits == == Action items for next checkpoint ==
Line 25: Line 39:
 * Deliverables
   * Signed off LEPs
   * Any user testing sessions
   * Any RTs
   * Announcement
   * Maybe feature-level deliverables (e.g. 'person pickers')
 * Where does exploratory testing go?
 * Where do mockups go?
 * Link to bug tag
 * 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 ===

  * [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] Populating and maintaining the access policy data

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

=== 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: 25
Next checkpoint: 2011-12-14

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

Harden bugs and teams

sinzui

2011-12-14

DEVELOPMENT

Managing disclosure

sinzui

2012-01-30

DEVELOPMENT

social private teams

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

  • [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] Populating and maintaining the access policy data

Actions for later

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

Notes

Resources

User research

Exploratory testing

Still needed

  • 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

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