Diff for "LEP"

Not logged in - Log In / Register

Differences between revisions 153 and 171 (spanning 18 versions)
Revision 153 as of 2011-10-18 00:44:00
Size: 5106
Editor: mbp
Comment: fix links
Revision 171 as of 2012-06-29 21:50:06
Size: 5728
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
||<|5>'''[[Projects/Disclosure|Disclosure]]'''||[[LEP/BetterPrivacy|Better Privacy]]||<|5>Curtis Hovey<<BR>>(sinzui)||<|5>Purple||&nbsp;|| ||<|9>'''[[Projects/Disclosure|Disclosure]]'''||[[LEP/BetterPrivacy|Better Privacy]]||<|9>Curtis Hovey<<BR>>(sinzui)||<|9>Purple||&nbsp;||
Line 18: Line 18:
||||<-1>[[LEP/PrivacyTransitions|Privacy Transitions ]]||||||pages and actions should leave no room for doubt.||
||||<-1>[[LEP/HardenedBugsProjectsTeams | Harden bugs, projects and teams]]||||||pages and actions should leave no room for doubt.||
||||<-1>[[LEP/LEP/Entitlement | Basic Entitlement]]|||||| Allow commercial users service their own needs. ||
||||<-1>[[LEP/InformationTypes | Information types]]||||||Launchpad knows which kind of data a bug or branch is to apply the rules.||
Line 19: Line 23:
||||<-1>[[LEP/PrivateProjectsAndDistributions|Private Projects and Distributions ]]||||||Projects and distributions can be made private and all subordinate artefacts are also private.||
||||<-1>Private teams &mdash; LEP to come||||||||
||||<-1>[[LEP/PrivateProjects|Private Projects]]||||||Projects can be made private and all subordinate artefacts are also private.||
||||<-1>[[LEP/SocialPrivateTeams| Social private teams]]||||||Allow private teams to collaborate with other teams ad data.||
Line 22: Line 26:
||'''[[Projects/ParallelTesting|Parallel testing]]'''||[[LEP/ParallelTesting|Parallel testing]]||Gary Poster (gary_poster)||Yellow||||
Line 27: Line 32:
||<tablestyle="width: 100%; text-align: center;" rowstyle="background: #2a2929; font-weight: bold; color: #f6bc05;">Project name & page||LEPs||Contact||Squad||Notes||
||'''[[Projects/CustomBugListings|Custom bug listings]]'''||[[LEP/CustomBugListings|Custom bug listings]]||Deryck Hodge (deryck)||Orange||||
 * [[/SimpleBugLinking]]
Line 30: Line 34:
none
Line 53: Line 58:
 * [[LEP/LessJunk]]
 * [[LEP/DebTags]]
 * [[LEP/ParallelEC2Command]]
 * [[LEP/LaunchpadJujuCharmForDevs]]
 * [[LEP/DisklessArchives]]
Line 57: Line 67:


 * [[LEP/MailArchiver]]
Line 67: Line 80:
 * [[LEP/BugsToFixedBinaries]]
Line 74: Line 88:
 * [[LEP/ParallelTesting]]
Line 86: Line 99:
 * [[LEP/DKIMAuthenticatedMail]] -- live, see [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=dkim|bugs tagged dkim]] for more work
Line 116: Line 128:
 * [[LEP/DKIMAuthenticatedMail]] -- done, see [[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=dkim|bugs tagged dkim]] for follow on work
 * [[LEP/CustomBugListings]] -- done but subject to another design review.

Launchpad enhancement proposals

Here you'll find links to proposals (LEPs) that people, both within the Canonical Launchpad team and the wider Launchpad community, have made for a way to change Launchpad.

This is good page to use to get a view of what's coming up for Launchpad and what's currently in progress.

You can also add your own LEP by following the Launchpad enhancement proposal process.

Working on now

Coding now

LEPs that people are implementing.

Project name & page

LEPs

Contact

Squad

Notes

Disclosure

Better Privacy

Curtis Hovey
(sinzui)

Purple

 

Trusted Pickers

Pickers should leave no room for doubt.

Privacy Transitions

pages and actions should leave no room for doubt.

Harden bugs, projects and teams

pages and actions should leave no room for doubt.

Basic Entitlement

Allow commercial users service their own needs.

Information types

Launchpad knows which kind of data a bug or branch is to apply the rules.

Managing Disclosure

Project owners should be able to see who has what access to private artefacts.

Private Projects

Projects can be made private and all subordinate artefacts are also private.

Social private teams

Allow private teams to collaborate with other teams ad data.

Release features when they are done

Release Features When They Are Done

Rob Collins (lifeless)

All

Parallel testing

Parallel testing

Gary Poster (gary_poster)

Yellow

Interaction design

LEPs for which the Product team are developing the user experience.

none

Drafting

LEPs that are being drafted.

Ready for review

LEPs that need product manager approval or LEPs that no one is actually scheduled to work on yet. We only get truly serious about LEPs when there is a truly serious intent to implement them.

Needs resources

Needs review

Ready to code

LEPs approved by the product manager / technical architect as appropriate.

Contributors

Contributors

Deployed

LEPs that have been coded & deployed, but are waiting signoff from the product manager


Done

LEPs that are done. This is our victory list.

Deferred

LEP (last edited 2012-06-29 21:50:06 by matthew.revell)