Diff for "Projects/Disclosure"

Not logged in - Log In / Register
Differences between revisions 7 and 34 (spanning 27 versions)
⇤ ← Revision 7 as of 2011-06-14 14:22:42 →
Size: 2746
Editor: jml
Comment:
← Revision 34 as of 2011-09-09 10:13:19 → ⇥
Size: 4511
Editor: matthew.revell
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
'''Current week:''' 4
 '''Current week:''' 15<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-09-21
Line 10: Line 10:
 * [[LEP/BugLinking]]
Line 19: Line 18:
 * Private teams work out of scope, except where necessary to enable above
 * Any complicated bug linking beyond the bare case for cloning		  * Bug linking will now be a separate project
Line 22: Line 20:
== Blockers ==

== Special actions ==

 * jml to create a project picker LEP
 * jml to go through LEPs, organize along roadmap lines, convert as many requirements to stories as make sense
Line 33: Line 25:
|| [[LEP/TrustedPickers|Person pickers]] || || 2011-06-16 || INPROGRESS ||
|| Project pickers || || || ||
|| [[LEP/BugLinking|Bug cloning]] || || ||		 || [[LEP/TrustedPickers#person-pickers|Person pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=person-picker|person-picker]]) || sinzui || 2011-09-21 || DEVELOPMENT ||
|| [[LEP/TrustedPickers#project-pickers|Target pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=target-picker|target-picker]]) || sinzui || 2011-10-13 || DEVELOPMENT ||
|| [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-09-21 || Privacy ribbon LIVE, otherwise DEVELOPMENT ||
|| [[LEP/ManagingDisclosure#granting|Granting disclosure]] || || || ||
|| [[LEP/ManagingDisclosure#seeing|Seeing disclosure]] || || || ||
|| [[LEP/ManagingDisclosure#withdrawing|Withdrawing disclosure]] || || || ||
|| [[LEP/PrivateProjectsAndDistributions#projects|Private projects]] || || || ||
|| [[LEP/PrivateProjectsAndDistributions#distributions|Private distributions]] || || || ||
|| [[LEP/PrivateProjectsAndDistributions#entitlement|Basic entitlement]] || || || ||
|| Private teams (LEP to come) || || || ||
Line 39: Line 38:
 1. Person pickers
 1. Project / distribution pickers
 1. As a developer, I want to be able to clone a bug from one project to another project so that I can have separate conversations about the bug, each with their own disclosure level
 1. As a project owner, I want to see who has access (is subscribed to) private bugs and branches within my project, so that I can make sure that everyone who needs to have access has it, and no one who shouldn’t doesn’t.
 1. (2 cycles) As a project owner, I want to give users permission to see all of the private items in my project so that I have a simple way to induct new members into my private project.
 1. As a project owner, I want to see users with permission to see all of the private items in my project so that I can maintain control over who has access to my project.
 1. As a project owner, I want to prevent a user from accessing to my project or a bug/branch, so that private information is not disclosed and that owners can respond to a disclosure issue immediately
 1. (2 cycles) alpha level, opt-in only private projects
 1. Private distributions
 1. As a person with rights over a blacklisted name, I want to create a private project or distribution with a blacklisted name without any Launchpad admin intervention or any other privileges, so that I can just get my stuff done and not accidentally destroy everything		 == Notes ==
Line 50: Line 40:
== XXX - missing bits ==  * We have placed a hard cut-off of 2011-09-21 on picker work: any non-Critical bugs will be picked up by the maintenance squad following feature delivery
  * Filtering of picker results has gone well
  * Affiliation information will return to pickers soon
 * 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.
  * Matthew to 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.
 * Jon is rethinking the picker UI following complaints about how many clicks it takes to make a selection.
 * Performance woes in both pickers have several delayed the project.
  * Three people are now working on picker performance.
 * 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 expected early October. 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
Line 52: Line 59:
 * Link to user testing sessions
 * Link to exploratory testing
 * Link to mockups		 == Resources ==

=== User research ===

 * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/
 * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/CodySommerville
 * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/SteveMagoun
 * Target picker
 * Person picker: invite beta feedback

=== Exploratory testing ===

 * https://dev.launchpad.net/QA/ExploratoryTesting/Disclosure/TrustedPickers

=== Still needed ===
Line 56: Line 76:
 * Turn into template  * Private teams coverage in LEP


=== How are we going to link from deliverables to LEPs? ===

 * 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

Disclosure

See also disclosure tag

Squad started: 2011-05-23
Current week: 15
Next checkpoint: 2011-09-21

Scope

Out of scope

Deliverables

Item

Owner

Expected date

Status

Signed off LEPs

jml

DONE

Person pickers (person-picker)

sinzui

2011-09-21

DEVELOPMENT

Target pickers (target-picker)

sinzui

2011-10-13

DEVELOPMENT

Seeing legacy disclosure

2011-09-21

Privacy ribbon LIVE, otherwise DEVELOPMENT

Granting disclosure

Seeing disclosure

Withdrawing disclosure

Private projects

Private distributions

Basic entitlement

Private teams (LEP to come)

Feature documentation

mrevell

Blog post

mrevell

Notes

  • We have placed a hard cut-off of 2011-09-21 on picker work: any non-Critical bugs will be picked up by the maintenance squad following feature delivery
    • Filtering of picker results has gone well
    • Affiliation information will return to pickers soon
  • 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.
    • Matthew to 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.
  • Jon is rethinking the picker UI following complaints about how many clicks it takes to make a selection.
  • Performance woes in both pickers have several delayed the project.
    • Three people are now working on picker performance.
  • 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 expected early October. 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)