Diff for "Projects/Disclosure"

Not logged in - Log In / Register

Differences between revisions 45 and 46
Revision 45 as of 2011-11-16 21:10:47
Size: 3520
Editor: flacoste
Comment: Update action items based on checkpoint
Revision 46 as of 2011-11-17 14:36:45
Size: 3600
Comment:
Deletions are marked like this. Additions are marked like this.
Line 72: Line 72:
 * Target picker
 * Person picker: invite beta feedback
 * [[/ManageDisclosureTagsInitialResearch|Dan's rough notes]] from +manage-disclosure with tags for policies paper prototyping resaerch.

Disclosure

See also disclosure tag

Squad started: 2011-05-23
Current week: 23
Next checkpoint: 2011-11-30

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-11-30

DEVELOPMENT

Managing disclosure

sinzui

2011-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] 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 of private bugs with multiple projects
  • [purple] Create report around branch privacy multi-tenancy

Manage disclosure

  • [purple] Implement clickable +managing-disclosure mock-ups
  • [danhg] User-test the dynamic +managing-disclosure mock-ups
  • [purple] Creating the access policy mechanism
  • [purple] Implement the +manage-disclosure UI: LATER
  • [purple] Populating and maintaining the access policy data: 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)