Diff for "Projects/Disclosure"

Not logged in - Log In / Register

Differences between revisions 43 and 44
Revision 43 as of 2011-11-02 17:08:59
Size: 3396
Editor: flacoste
Comment: Updated based on checkpoint meeting
Revision 44 as of 2011-11-02 23:04:31
Size: 3497
Editor: flacoste
Comment: Update based on conversation with lifeless and OEM
Deletions are marked like this. Additions are marked like this.
Line 42: Line 42:
  * [purple] Fix the bug that prevents admins from setting privileged bug status. TODO
  * [purple] Review the split script and get agreement from stakeholders on its output so that
  we can run it unattended. TODO
Line 46: Line 43:
  the multi-tenancy feature for private bugs. TODO   the multi-tenancy feature for private bugs. DONE
Line 51: Line 48:
  * [purple] Remove multi-tenancy around bug privacy. TODO   * [purple] Add and enable footgun feature flag to reduce growing the number of private bugs with multiple projects.
  * [purple] Creating the access policy mechanism TODO
  * [purple] Populating and maintaining the access policy data TODO
  * [purple] Implement the +manage-disclosure UI
  * [purple] Turn on +manage-disclosure and security through the access policy TODO

Disclosure

See also disclosure tag

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

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

Managing disclosure

sinzui

2011-11-30

DEVELOPMENT

Harden bugs and teams

sinzui

2011-11-16

DEVELOPMENT

social private teams

Private projects

Private distributions

Basic entitlement

Feature documentation

danhg

Blog post

danhg

Action items for next checkpoint

  • [huwshimi] Produce new mockups around security/privacy policy conundrum (options for one or two pages) TODO
  • [danhg] User-test the mock-ups TODO
  • [purple] Settle what are the requirements from stakeholders before we can turn-off the multi-tenancy feature for private bugs. DONE
  • [purple] Send the PPA clean-up email TODO
  • [purple] Change the policy around hiding own bug comment. TODO
  • [purple] Add AJAX ui to delete bug task TODO
  • [purple] Create report around branch privacy multi-tenancy. TODO
  • [purple] Add and enable footgun feature flag to reduce growing the number of private bugs with multiple projects.
  • [purple] Creating the access policy mechanism TODO
  • [purple] Populating and maintaining the access policy data TODO
  • [purple] Implement the +manage-disclosure UI
  • [purple] Turn on +manage-disclosure and security through the access policy TODO

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)