Diff for "Projects/Disclosure"

Not logged in - Log In / Register
Differences between revisions 1 and 42 (spanning 41 versions)
⇤ ← Revision 1 as of 2011-06-14 12:25:03 →
Size: 531
Editor: jml
Comment:
← Revision 42 as of 2011-11-02 15:56:59 → ⇥
Size: 3769
Editor: flacoste
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
See also [[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=disclosure|disclosure tag]]

'''Squad started:''' 2011-05-23<<BR>>
'''Current week:''' 21<<BR>>
'''Next [[PolicyandProcess/FeatureDevelopmentCheckpoint|checkpoint]]:''' 2011-11-02
Line 5: Line 10:
 * [[LEP/BugLinking]]
Line 10: Line 14:
 * [[LEP/SocialPrivateTeams]]
Line 14: Line 19:
 * 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 17: Line 21:
== Blockers ==
Line 19: Line 22:
== Special actions == == Deliverables ==
Line 21: Line 24:
 * jml to go through LEPs, organize along roadmap lines, convert as many requirements to stories as make sense || '''Item''' || '''Owner''' || '''Expected date''' || '''Status''' ||
|| Signed off LEPs || jml || || DONE ||
|| [[LEP/TrustedPickers#person-pickers|Person pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=person-picker|person-picker]]) || sinzui || 2011-09-21 || DONE ||
|| [[LEP/TrustedPickers#project-pickers|Target pickers]] ([[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=target-picker|target-picker]]) || sinzui || 2011-10-13 || DONE ||
|| [[LEP/ManagingDisclosure#seeing-legacy|Seeing legacy disclosure]] || || 2011-11-02 || DEVELOPMENT ||
|| +manage-disclosure design || huwshimi, wallyworld, jcsackett || 2011-10-05 || DONE ||
|| +manage-disclosure alpha (minus search) || huwshimi, wallyworld, jcsackett || 2011-11-02 || ||
|| Harden bugs and teams || sinzui || 2011-11-16 || IN PROGRESS ||
|| [[LEP/SocialPrivateTeams | social private teams]] || || || STALLED ||
|| [[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]] || || || ||
|| Feature documentation || danhg || || ||
|| Blog post || danhg || || ||

Outcome of 2011-10-19 check-point:

 * We need a plan for how to tackle social private teams: do we spin it out to another squad?
 * Jon, Ian and Dan will work on a round of user testing of +manage-disclosure

== Notes ==

 * Consulting with stakeholders has taken much of the squad's time during this past two weeks.
 * Stakeholders need to manually clean-up bugs where there's a private bug task on a public bug. Purple have written a script that lets stakeholders delete bug tasks and this needs to be passed to stakeholders with instructions.
 * Social private teams are hard:
  * We may want to spin social private teams out to a separate squad
 * The complexity of private distros is likely to extend this project to April 2012.
 * The +manage-disclosure page needs another round of user testing. Ian and Jon to lead that with Dan's help.



== 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
 * Daily testing by matsubara sent to the ~launchpad-dev list

=== Still needed ===


=== 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: 21
Next checkpoint: 2011-11-02

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-11-02

DEVELOPMENT

+manage-disclosure design

huwshimi, wallyworld, jcsackett

2011-10-05

DONE

+manage-disclosure alpha (minus search)

huwshimi, wallyworld, jcsackett

2011-11-02

Harden bugs and teams

sinzui

2011-11-16

IN PROGRESS

social private teams

STALLED

Granting disclosure

Seeing disclosure

Withdrawing disclosure

Private projects

Private distributions

Basic entitlement

Feature documentation

danhg

Blog post

danhg

Outcome of 2011-10-19 check-point:

  • We need a plan for how to tackle social private teams: do we spin it out to another squad?
  • Jon, Ian and Dan will work on a round of user testing of +manage-disclosure

Notes

  • Consulting with stakeholders has taken much of the squad's time during this past two weeks.
  • Stakeholders need to manually clean-up bugs where there's a private bug task on a public bug. Purple have written a script that lets stakeholders delete bug tasks and this needs to be passed to stakeholders with instructions.
  • Social private teams are hard:
    • We may want to spin social private teams out to a separate squad
  • The complexity of private distros is likely to extend this project to April 2012.
  • The +manage-disclosure page needs another round of user testing. Ian and Jon to lead that with Dan's help.

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)