Diff for "Projects/Disclosure"

Not logged in - Log In / Register

Differences between revisions 51 and 52
Revision 51 as of 2011-12-15 15:39:02
Size: 4313
Comment:
Revision 52 as of 2011-12-15 15:55:43
Size: 4455
Comment:
Deletions are marked like this. Additions are marked like this.
Line 45: Line 45:
  * [mrevell]: Agree on the terminology and mutural exclusivity behaviour of security/propietary bugs. Respond to Curtis' email on the list.

Disclosure

See also disclosure tag

Squad started: 2011-05-23
Current week: 27
Next checkpoint: 2012-01-04

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

social private teams

sinzui

2012-01-04

DEVELOPMENT

Managing disclosure

sinzui

2012-01-18

DEVELOPMENT

Harden bugs and teams

sinzui

2012-02-01

DEVELOPMENT

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
  • [mrevell]: Agree on the terminology and mutural exclusivity behaviour of security/propietary bugs. Respond to Curtis' email on the list.

Manage disclosure

  • [purple] Implement tweaked +manage-disclosure clickable mock-up
  • [danhg] User-test the tweaked clickable +managing-disclosure mock-ups
  • [purple] Populating and maintaining the access policy data
  • [huwshimi]: speak to sinzui about how to present embargoed security bugs in the UI
  • [danhg]: speak to sinzui to then rewrite the privacy ribbon messages to take account of the new situations it must handle
  • [EVERYONE!]: we will refer to "Sharing" rather than "Disclosure"
  • [purple]: replace references to "disclosure" with "sharing"

Social private teams

  • [purple]: PPA subscribers should have access to only the archive itself
  • [purple]: Subscribers to a private team's branch should be permitted to see the branch and its merge proposals
  • [purple]: priv teams can be package maintainers
  • [purple]: priv teams can subscribe to blueprints
  • [purple]: priv teams can subscribe to bugs
  • [purple]: we will fix the situation where you can lose access to your private team
  • [purple]: warn in the picker when you're about to expose the name of a private team
  • [huwshimi]: speak to jcsackett about the design of the warning
  • [danhg]: test the warnings
  • [mrevell]: seek agreement from stakeholders on how adding a private team to a private team should work
  • [danhg]: what should someone who is not a member of a private team see when they visit that private team's overview page? Dan to gather data. (bug 904293)

Actions for later

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

Notes

Resources

User research

Exploratory testing

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