launchpad development|
Size: 3822
Comment: link in fastdowntime
|
← Revision 171 as of 2012-06-29 21:50:06 ⇥
Size: 5728
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| This page is a list of LEPs. See the LaunchpadEnhancementProposalProcess for more information. | = Launchpad enhancement proposals = |
| Line 3: | Line 3: |
| 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 [[LaunchpadEnhancementProposalProcess|Launchpad enhancement proposal process]]. = Working on now = == Coding now == LEPs that people are implementing. ||<tablestyle="width: 100%; text-align: center;" rowstyle="background: #2a2929; font-weight: bold; color: #f6bc05;">Project name & page||LEPs||Contact||Squad||Notes|| ||<|9>'''[[Projects/Disclosure|Disclosure]]'''||[[LEP/BetterPrivacy|Better Privacy]]||<|9>Curtis Hovey<<BR>>(sinzui)||<|9>Purple|| || ||||<-1>[[LEP/TrustedPickers|Trusted Pickers]]||||||Pickers should leave no room for doubt.|| ||||<-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.|| ||||<-1>[[LEP/ManagingDisclosure|Managing Disclosure]]||||||Project owners should be able to see who has what access to private artefacts.|| ||||<-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.|| ||'''Release features when they are done'''||[[LEP/ReleaseFeaturesWhenTheyAreDone|Release Features When They Are Done]]||Rob Collins (lifeless)||All|||| ||'''[[Projects/ParallelTesting|Parallel testing]]'''||[[LEP/ParallelTesting|Parallel testing]]||Gary Poster (gary_poster)||Yellow|||| == Interaction design == LEPs for which the Product team are developing the user experience. * [[/SimpleBugLinking]] none |
|
| Line 8: | Line 40: |
| * [[LEP/BugTaskSummaryCache]] | |
| Line 22: | Line 53: |
| * [[LEP/ReliableDBDeploys]] | |
| Line 25: | Line 55: |
| * [[LEP/BounceHandling]] | * [[LEP/ForwardAttachmentsUpstream]] * [[LEP/BugDependencies]] * [[LEP/SSH_OAuth]] * [[LEP/LessJunk]] * [[LEP/DebTags]] * [[LEP/ParallelEC2Command]] * [[LEP/LaunchpadJujuCharmForDevs]] * [[LEP/DisklessArchives]] |
| Line 29: | Line 66: |
| LEPs that need product strategist 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. | 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. * [[LEP/MailArchiver]] |
| Line 35: | Line 75: |
| * [[LEP/BounceHandling]] | |
| Line 39: | Line 80: |
| * [[LEP/BugsToFixedBinaries]] | |
| Line 42: | Line 84: |
| LEPs approved by the product strategist / technical architect as appropriate. | LEPs approved by the product manager / technical architect as appropriate. |
| Line 46: | Line 88: |
| * [[LEP/ParallelTesting]] | |
| Line 56: | Line 97: |
| = Being implemented = LEPs being worked on now. == Launchpad team == * [[LEP/DerivativeDistributions]] * [[LEP/ReleaseFeaturesWhenTheyAreDone]] * [[LEP/BetterPrivacy]] * [[LEP/TrustedPickers]] -- having enough information to choosing a person or project. * [[LEP/ManagingDisclosure]] -- Viewing who has access, knowing its kind, and seeing a summary of what is disclosed. * [[LEP/BugLinking]] -- Cloning and linking a private project bug to another project. * [[LEP/PrivateProjectsAndDistributions]] -- Projects and distributions can be made private and all subordinate artefacts are also private. |
|
| Line 75: | Line 99: |
| * [[LEP/DKIMAuthenticatedMail]] -- working for basic cases, see [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=dkim|bugs tagged dkim]] for more work | |
| Line 77: | Line 100: |
| * [[LEP/BugzillaComponents]] | |
| Line 80: | Line 104: |
| LEPs that have been coded & deployed, but are waiting signoff from the product strategist | LEPs that have been coded & deployed, but are waiting signoff from the product manager |
| Line 89: | Line 113: |
| * [[LEP/DerivedDistributions]] | |
| Line 102: | Line 127: |
| * [[LEP/BugTaskSummaryCache]] * [[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. |
|
| Line 110: | Line 138: |
| * [[LEP/BugzillaComponents]] -- stalled | |
| Line 113: | Line 140: |
| * [[LEP/BranchAccessToken]] -- abandoned in favour of extending existing mechanisms |
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 |
Curtis Hovey |
Purple |
|
||
Pickers should leave no room for doubt. |
||||
pages and actions should leave no room for doubt. |
||||
pages and actions should leave no room for doubt. |
||||
Allow commercial users service their own needs. |
||||
Launchpad knows which kind of data a bug or branch is to apply the rules. |
||||
Project owners should be able to see who has what access to private artefacts. |
||||
Projects can be made private and all subordinate artefacts are also private. |
||||
Allow private teams to collaborate with other teams ad data. |
||||
Release features when they are done |
Rob Collins (lifeless) |
All |
||
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
LEP/ApportOnStable (reviewed)
Needs review
Ready to code
LEPs approved by the product manager / technical architect as appropriate.
Contributors
LEP/ActivatingDevelopmentFromDesktop -- allow API clients to set SSH, GPG keys, etc
Contributors
LEP/ForkingLPServe -- deployment problems, somewhat stalled
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.
Registry/InvolvementPortletRefactor, LEP/ProjectConfiguration
LEP/DesktopWideLaunchpadIntegration -- integrate the Ubuntu desktop into Launchpad instead of individual apps
LEP/DKIMAuthenticatedMail -- done, see bugs tagged dkim for follow on work
LEP/CustomBugListings -- done but subject to another design review.
Deferred
- We shouldn't do this until we have a way of turning personal branches into trunk branches of new projects.
LEP/BuildFarmBuilderPools - abandoned for now
LEP/ResultsTracker - being prototyped outside of Launchpad, contact Marc Tardif
Code/MergeQueues/LEP -- Create queues for taking merge proposals to the actual merge step.
LEP/BranchAccessToken -- abandoned in favour of extending existing mechanisms
