Diff for "Projects/Disclosure"

Not logged in - Log In / Register
Differences between revisions 42 and 44 (spanning 2 versions)
⇤ ← Revision 42 as of 2011-11-02 15:56:59 →
Size: 3769
Editor: flacoste
Comment:
← 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 7: Line 7:
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-02 '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-16
Line 28: Line 29:
|| [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-11-02 || DEVELOPMENT ||
|| +manage-disclosure design || huwshimi, wallyworld, jcsackett || 2011-10-05 || DONE ||
|| +manage-disclosure alpha (minus search) || huwshimi, wallyworld, jcsackett || 2011-11-02 || ||
|| Harden bugs and teams || sinzui || 2011-11-16 || IN PROGRESS ||
|| [[LEP/SocialPrivateTeams | social private teams]] || || || STALLED ||
|| [[LEP/ManagingDisclosure#granting|Granting disclosure]] || || || ||
|| [[LEP/ManagingDisclosure#seeing|Seeing disclosure]] || || || ||
|| [[LEP/ManagingDisclosure#withdrawing|Withdrawing disclosure]] || || || ||		 || [[LEP/ManagingDisclosure|Managing disclosure]] ||sinzui || 2011-11-30 || DEVELOPMENT ||
|| Harden bugs and teams || sinzui || 2011-11-16 || DEVELOPMENT ||
|| [[LEP/SocialPrivateTeams | social private teams]] || || || ||
Line 42: Line 38:
Outcome of 2011-10-19 check-point: == Action items for next checkpoint ==
Line 44: Line 40:
 * We need a plan for how to tackle social private teams: do we spin it out to another squad?
 * Jon, Ian and Dan will work on a round of user testing of +manage-disclosure		   * [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
Line 49: Line 56:
 * Consulting with stakeholders has taken much of the squad's time during this past two weeks.
 * Stakeholders need to manually clean-up bugs where there's a private bug task on a public bug. Purple have written a script that lets stakeholders delete bug tasks and this needs to be passed to stakeholders with instructions.
 * Social private teams are hard:
  * We may want to spin social private teams out to a separate squad
 * The complexity of private distros is likely to extend this project to April 2012.
 * The +manage-disclosure page needs another round of user testing. Ian and Jon to lead that with Dan's help.

 <<PageList(regex:^LEP/Disclosure/Checkpoint-*)>>

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)