Diff for "Projects/Disclosure"

Not logged in - Log In / Register
Differences between revisions 4 and 32 (spanning 28 versions)
⇤ ← Revision 4 as of 2011-06-14 14:10:30 →
Size: 2677
Editor: jml
Comment:
← Revision 32 as of 2011-08-19 14:42:01 → ⇥
Size: 3213
Editor: matthew.revell
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
'''Squad started:''' 2011-05-23<<BR>>
'''Current week:''' 8<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-08-24
Line 7: Line 10:
 * [[LEP/BugLinking]]
Line 17: Line 19:
 * Any complicated bug linking beyond the bare case for cloning  * Bug linking will now be a separate project
Line 19: Line 21:
== Blockers ==

== Special actions ==

 * jml to go through LEPs, organize along roadmap lines, convert as many requirements to stories as make sense
Line 29: Line 26:
|| Person pickers || || 2011-06-16 || INPROGRESS ||
|| Project pickers || || ||		 || [[LEP/TrustedPickers#person-pickers|Person pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=person-picker|person-picker]]) || sinzui || 2011-08-09 || USER-ACCEPTANCE ||
|| [[LEP/TrustedPickers#project-pickers|Target pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=target-picker|target-picker]]) || sinzui || 2011-08-23 || DEVELOPMENT, some performance issues causing delay ||
|| [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || || 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]] || || || ||
Line 34: 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 45: Line 40:
== XXX - missing bits ==  * At each checkpoint, make sure to go over [[LEP/BetterPrivacy]] and mark off which requirements have been met
 * 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.
Line 47: Line 46:
 * Deliverables
   * Any user testing sessions
   * Any RTs
   * Maybe feature-level deliverables (e.g. 'person pickers')
 * Where does exploratory testing go?
 * Where do mockups go?		 == 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 ===

 * Link to mockups
Line 54: Line 64:
 * Turn into template

=== 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: 8
Next checkpoint: 2011-08-24

Scope

Out of scope

  • LEP/AuditTrail

  • Private teams work out of scope, except where necessary to enable above
  • Bug linking will now be a separate project

Deliverables

Item

Owner

Expected date

Status

Signed off LEPs

jml

DONE

Person pickers (person-picker)

sinzui

2011-08-09

USER-ACCEPTANCE

Target pickers (target-picker)

sinzui

2011-08-23

DEVELOPMENT, some performance issues causing delay

Seeing legacy disclosure

Privacy ribbon LIVE, otherwise DEVELOPMENT

Granting disclosure

Seeing disclosure

Withdrawing disclosure

Private projects

Private distributions

Basic entitlement

Feature documentation

mrevell

Blog post

mrevell

Notes

  • At each checkpoint, make sure to go over LEP/BetterPrivacy and mark off which requirements have been met

  • 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.

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)