launchpad development|
Size: 3628
Comment:
|
Size: 2528
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| '''Current week:''' 4<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-06-15 |
'''Current week:''' 8<<BR>> '''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-07-26 |
| Line 11: | Line 11: |
| * [[LEP/BugLinking]] | |
| Line 21: | Line 20: |
| * Any complicated bug linking beyond the bare case for cloning | * Bug linking will now be a separate project |
| Line 23: | Line 22: |
| == Blockers == * Open questions on [[LEP/BugLinking]] == 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 * jml & sinzui to resolve open questions on [[LEP/BugLinking]] |
|
| Line 37: | Line 27: |
| || [[LEP/TrustedPickers#person-pickers|Person pickers]] || || 2011-06-16 || INPROGRESS || || [[LEP/TrustedPickers#project-pickers|Project pickers]] || || 2011-06-16 || INPROGRESS || || [[LEP/BugLinking|Bug cloning]] || || || |
|| [[LEP/TrustedPickers#person-pickers|Person pickers]] || || 2011-08-09 || INPROGRESS || || [[LEP/TrustedPickers#project-pickers|Project pickers]] || || 2011-08-16 || INPROGRESS || || [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || || || [[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 43: | Line 39: |
| 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 52: | Line 41: |
| == XXX - missing bits == | * At each checkpoint, make sure to go over [[LEP/BetterPrivacy]] and mark off which requirements have been met |
| Line 54: | Line 43: |
| * Link to user testing sessions * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/ * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/CodySommerville * https://wiki.canonical.com/Launchpad/UserResearch/Disclosure/SteveMagoun * Link to exploratory testing |
== 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 === Exploratory testing === * https://dev.launchpad.net/QA/ExploratoryTesting/Disclosure/TrustedPickers === Still needed === |
| Line 61: | Line 59: |
| * Turn into template | |
| Line 66: | Line 63: |
| * Change LEPs to have multiple users stories in a section after the intro and before the constraints |
Disclosure
See also disclosure tag
Squad started: 2011-05-23
Current week: 8
Next checkpoint: 2011-07-26
Scope
Out of scope
- 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 |
|
2011-08-09 |
INPROGRESS |
|
|
2011-08-16 |
INPROGRESS |
|
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
|
|
||
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
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
Exploratory testing
Still needed
- Link to mockups
Somehow fit in two week cycle -- https://wiki.canonical.com/Launchpad/PolicyandProcess/FeatureDevelopment
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
