Diff for "Projects/Disclosure"

Not logged in - Log In / Register

Differences between revisions 37 and 38
Revision 37 as of 2011-09-21 15:52:14
Size: 4455
Comment:
Revision 38 as of 2011-09-21 20:43:23
Size: 4452
Editor: sinzui
Comment:
Deletions are marked like this. Additions are marked like this.
Line 30: Line 30:
|| Private teams and nested private teams (LEP to come) || || 2011-10-19 || || || [[LEP/SocialPrivateTeams | social private teams]] || || 2011-10-19 || ||

Disclosure

See also disclosure tag

Squad started: 2011-05-23
Current week: 17
Next checkpoint: 2011-10-05

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

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

social private teams

2011-10-19

Granting disclosure

Seeing disclosure

Withdrawing disclosure

Private projects

Private distributions

Basic entitlement

Feature documentation

mrevell

Blog post

mrevell

Notes

  • 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

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)