Diff for "Projects/Disclosure"

Not logged in - Log In / Register

Differences between revisions 47 and 48
Revision 47 as of 2011-11-30 15:36:06
Size: 3700
Editor: matsubara
Comment:
Revision 48 as of 2011-11-30 20:02:55
Size: 3413
Editor: flacoste
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
'''Current week:''' 23<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-30
'''Current week:''' 25<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-14
Line 29: Line 28:
|| Harden bugs and teams || sinzui || 2011-11-30 || DEVELOPMENT ||
|| [[LEP/ManagingDisclosure|Managing disclosure]] ||sinzui || 2011-01-30 || DEVELOPMENT ||
|| Harden bugs and teams || sinzui || 2011-12-14 || DEVELOPMENT ||
|| [[LEP/ManagingDisclosure|Managing disclosure]] ||sinzui || 2012-01-30 || DEVELOPMENT ||
Line 42: Line 41:
  * [purple] Turn off PPA for open teams.
  * [purple] Make the delete bugtask UI generally available.
  * [purple] Announce the removal of sharing of private bugs.
  * [purple] Send an email to people who have shared private bugs about what
  is going to happen with those bugs.
  * [purple] Add and enable footgun feature flag to reduce growing the number
  * [purple] Modify the footgun feature flag to keep multi-tenancy for
  security bugs.
  * [purple] Enable footgun feature flag to reduce growing the number
Line 49: Line 45:
  * [purple] Create report around branch privacy multi-tenancy
Line 53: Line 48:
  * [purple] Implement clickable +managing-disclosure mock-ups
Line 55: Line 49:
  * [purple] Creating the access policy mechanism   * [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
Line 57: Line 53:
  * [purple] Implement the +manage-disclosure UI: LATER
  * [purple] Populating and maintaining the access policy data: LATER
== Actions for later ==
Line 63: Line 59:
<<PageList(regex:^LEP/Disclosure/Checkpoint-*)>> <<PageList(regex:^Projects/Disclosure/Checkpoint-*)>>

Disclosure

See also disclosure tag

Squad started: 2011-05-23
Current week: 25
Next checkpoint: 2011-11-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)