Diff for "Projects/Disclosure"

Not logged in - Log In / Register
Differences between revisions 39 and 43 (spanning 4 versions)
⇤ ← Revision 39 as of 2011-09-21 20:43:43 →
Size: 4483
Editor: sinzui
Comment:
← Revision 43 as of 2011-11-02 17:08:59 → ⇥
Size: 3396
Editor: flacoste
Comment: Updated based on checkpoint meeting
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
'''Current week:''' 17<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-10-05		 '''Current week:''' 21<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-16
Line 28: Line 29:
|| [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-09-22 || READY FOR SIGNOFF ||
|| +manage-disclosure design || huwshimi, wallyworld, jcsackett || 2011-10-05 || ||
|| +manage-disclosure alpha (minus search) || huwshimi, wallyworld, jcsackett || 2011-10-19 || ||
|| [[LEP/SocialPrivateTeams | social private teams]] || || 2011-10-19 || ||
|| [[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] 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
  * [purple] Settle what are the requirements from stakeholders before we can turn-off
  the multi-tenancy feature for private bugs. TODO
  * [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] Remove multi-tenancy around bug privacy. TODO
Line 43: Line 55:
 * Pickers will be ready for mrevell's sign-off on 2011-09-22.
 * wgrant, stevenk and lifeless will start work on nested private teams.
 * huwshimi, wallyworld and jcsackett will produce a design for +manage-disclosure pages and then implement it.
 * William is working on showing who can see private artefacts associated with a project. As a result, he is also making super fast all queries relating to privacy and Ubuntu.
 * Curtis is working on fixing the problem where changing a bug's privacy or security status doesn't yet automatically subscribe/unsubscribe the relevant people.
 * We will use UDS to research private teams
 * Private teams are now officially in-scope, following a period where they were tacitly in-scope due to the impact our failing team privacy has on other aspects of the Disclosure project.
  * Curtis will write a LEP
  * Team privacy is relatively easy, except for nesting private teams inside public teams, which will be a little more complicated to handle.
  * Curtis expects that tackling private teams will add six weeks to the Managing Disclosure project.
 * Performance woes in both pickers have several delayed the project.
 * The privacy ribbon is now live and appears to function well
 * Stakeholders might not consider this project complete if team privacy is not included
 * Private questions were expected early October (now unlikely). In prepartion, an admin can remove a question subscriber.
 * Decided against allowing hiding of the privacy ribbon.
 * At each checkpoint, make sure to go over [[LEP/BetterPrivacy]] and mark off which requirements have been met		 <<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] 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
  • [purple] Settle what are the requirements from stakeholders before we can turn-off the multi-tenancy feature for private bugs. TODO
  • [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] Remove multi-tenancy around bug privacy. 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)