Diff for "Projects/Disclosure"

Not logged in - Log In / Register

Differences between revisions 48 and 49
Revision 48 as of 2011-11-30 20:02:55
Size: 3413
Editor: flacoste
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 7: Line 7:
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-14 '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-12-14
Line 68: Line 68:
 * [[/ManageDisclosureTagsInitialResearch|Dan's rough notes]] from +manage-disclosure with tags for policies paper prototyping resaerch.  * [[/ManageDisclosureTagsInitialResearch|Dan's rough notes]] from +manage-disclosure with tags for policies paper prototyping research.

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)