launchpad development|
Size: 1178
Comment: Really rough roadmap.
|
Size: 3965
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''DRAFT -- don't believe a word this says''' | ## page was renamed from VersionFourDotO/Roadmap |
| Line 3: | Line 3: |
| There are three major areas of development for Launchpad 4.0: getting bugs off Ubuntu, enabling the daily builds story and tighter cross-project collaboration in translations. | <<Anchor(road-ahead)>> = The Road Ahead = |
| Line 5: | Line 6: |
| This page tries to present a rough roadmap as to how we'll do these. | '''''This section is a draft. Don't rely on it.''''' |
| Line 7: | Line 8: |
| = Bugs off Ubuntu = | We're starting to get some idea of what we think we should do for the second half of 2010. We'll probably change our minds between now and June, but we'd like to start letting you know what we are thinking. |
| Line 9: | Line 10: |
| == Bug heat == | == Derivative distributions == |
| Line 11: | Line 12: |
| == Q&A on bugs == | We want to allow our commercial customers to create distributions on Launchpad that are derived from Ubuntu. We want them to have full archive building support, great bug filing workflows and full package branch support too. |
| Line 13: | Line 14: |
| == Bug forwarding == | == Privacy, permissions and notification == |
| Line 15: | Line 16: |
| Privacy is a mess for Canonical's internal stakeholders, permissions are a mess for everyone and Launchpad sends way too much email. We need to decouple visibility from subscription and mutability from ownership and provide a clear, simple way to control who can read & write to what. | |
| Line 16: | Line 18: |
| = Daily builds = == Generic build infrastructure == == Building source package branches with recipes == == Full recipe interface == == Code imports for all major packages == * bzr-svn support * bzr-hg support = Translations integration = '''XXX - fill this in.''' = Supporting infrastructure = * UI for selecting an archive * Improved package / product linking * JIT registration of projects for creating imports * Crowd-sourcing * code import maintenance * bug import maintenance * project / package linking = Exceptions = These are things that don't fit into the above themes, but we have to do to satisfy external obligations. == Archive snapshots == |
See our [[LaunchpadEnhancementProposalProcess|LEPs]]: * [[LEP/PermissionsAndNotifications]] * [[LEP/BetterPrivacy]] * [[LEP/AuditTrail]] |
| Line 52: | Line 25: |
| == Branch privacy for distributions == | * [[https://blueprints.launchpad.net/ubuntu/+spec/foundations-lucid-software-center-repository-based-index|Archive index]] * [[https://blueprints.launchpad.net/ubuntu/+spec/foundations-lucid-ratings-and-reviews-in-software-center|Ratings and reviews]] * [[https://blueprints.launchpad.net/ubuntu/+spec/foundations-lucid-user-contributed-metadata-for-software-center|User-contributed metadata]] == Desktop integration == The Ubuntu desktop should be a wonderful platform for developers who want to write apps for the Ubuntu desktop. Launchpad is a core part of the way developers write applications for the Ubuntu desktop. It should be really easy for people to get started with Launchpad. In addition, we want to make sure that the Ubuntu One auth experience and the Launchpad auth experience line up well. == Performance == Launchpad is too slow, make it faster. <<Anchor(about)>> = About this page = This page is a rough guide on what we're doing over the next few months as part of our [[VersionFourDotO|current development cycle]]. == Using the page == Use this page to keep track of what we are planning on doing, and when. If you think "I'd like to know what to expect of Launchpad over the coming months", then this is the page to follow. We intend to maintain this page for future planning cycles of Launchpad, so if you are at all interested in having a say in Launchpad development '''<<Action(subscribe, subscribe now)>>'''. We've crammed as many links as we could find into the page. These links themselves often link to other things. Follow these links and explore the dark and dangerous world of Launchpad development. == The dates == "Dec 2009" means "targeted to the rollout at the end of December 2009". Each month is linked to the Launchpad release milestone for that date, so you can see what we're ''actually'' doing. Note that the dates here aren't actually ''commitments'', they are just our best guesses. == How complete is it? == Sometimes we'll do cool stuff and won't note it down here. Follow our blog for things like that. Also, this is mostly about Canonical-sponsored development. Community contributors are welcome to join in, but are just as welcome to scratch whatever itches them. == Questions? == This page is maintained by the [[https://launchpad.net/~jml|Launchpad Product Strategist]]. If you have any questions, contact the strategist, or begin a discussion on the [[https://launchpad.net/~launchpad-users|Launchpad users mailing list]]. This page is, and probably always will be a work-in-progress. If our plans change, we'll try to make sure you hear about it. If you have any ideas on how we can do that better — or make the roadmap more useful — contact the strategist or make a note on the page itself. |
The Road Ahead
This section is a draft. Don't rely on it.
We're starting to get some idea of what we think we should do for the second half of 2010. We'll probably change our minds between now and June, but we'd like to start letting you know what we are thinking.
Derivative distributions
We want to allow our commercial customers to create distributions on Launchpad that are derived from Ubuntu. We want them to have full archive building support, great bug filing workflows and full package branch support too.
Privacy, permissions and notification
Privacy is a mess for Canonical's internal stakeholders, permissions are a mess for everyone and Launchpad sends way too much email. We need to decouple visibility from subscription and mutability from ownership and provide a clear, simple way to control who can read & write to what.
See our LEPs:
Software Centre support
Desktop integration
The Ubuntu desktop should be a wonderful platform for developers who want to write apps for the Ubuntu desktop. Launchpad is a core part of the way developers write applications for the Ubuntu desktop. It should be really easy for people to get started with Launchpad. In addition, we want to make sure that the Ubuntu One auth experience and the Launchpad auth experience line up well.
Performance
Launchpad is too slow, make it faster.
About this page
This page is a rough guide on what we're doing over the next few months as part of our current development cycle.
Using the page
Use this page to keep track of what we are planning on doing, and when. If you think "I'd like to know what to expect of Launchpad over the coming months", then this is the page to follow.
We intend to maintain this page for future planning cycles of Launchpad, so if you are at all interested in having a say in Launchpad development subscribe now.
We've crammed as many links as we could find into the page. These links themselves often link to other things. Follow these links and explore the dark and dangerous world of Launchpad development.
The dates
"Dec 2009" means "targeted to the rollout at the end of December 2009". Each month is linked to the Launchpad release milestone for that date, so you can see what we're actually doing.
Note that the dates here aren't actually commitments, they are just our best guesses.
How complete is it?
Sometimes we'll do cool stuff and won't note it down here. Follow our blog for things like that.
Also, this is mostly about Canonical-sponsored development. Community contributors are welcome to join in, but are just as welcome to scratch whatever itches them.
Questions?
This page is maintained by the Launchpad Product Strategist. If you have any questions, contact the strategist, or begin a discussion on the Launchpad users mailing list.
This page is, and probably always will be a work-in-progress. If our plans change, we'll try to make sure you hear about it. If you have any ideas on how we can do that better — or make the roadmap more useful — contact the strategist or make a note on the page itself.
