Diff for "Projects/Disclosure"

Not logged in - Log In / Register
Differences between revisions 40 and 44 (spanning 4 versions)
⇤ ← Revision 40 as of 2011-10-07 09:57:09 →
Size: 3185
Editor: matthew.revell
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 6: Line 6:
'''Current week:''' 19<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-10-19		 '''Current week:''' 21<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-16
Line 28: Line 29:
|| [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-10-19 || DEVELOPMENT ||
|| +manage-disclosure design || huwshimi, wallyworld, jcsackett || 2011-10-05 || DONE ||
|| +manage-disclosure alpha (minus search) || huwshimi, wallyworld, jcsackett || 2011-10-19 || ||
|| [[LEP/SocialPrivateTeams | social private teams]] || || 2011-10-19 || DEVELOPMENT ||
|| [[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 38: Line 35:
|| Feature documentation || mrevell || || ||
|| Blog post || mrevell || || ||		 || 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
Line 43: Line 56:
 * Curtis is starting work on social private teams
 * The +manage-disclosure page should be ready as an alpha for the 2011-10-19 checkpoint
 * We will use UDS to research private teams
 * Private questions were expected early October (now unlikely). In prepartion, an admin can remove a question subscriber.
 <<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)