Launchpad itself

Launchpad Federation?

Asked by Marcus Granado

I currently understand that, eventually, the Launchpad source code will be released and other instances of specialized launchpads will start springing up around the Internet.

Is there any plans to provide an easy upstream and downstream integration between them, very much like a federation of independent states? I mean, something simple in the sense of pointing to some launchpads as upstream, and others as downstream. There would still be a tight integration of projects just like today's Launchpad has, but no central command, which would be good for the larger adoption of Launchpad.

If not, I would like to suggest such a feature: easy-to-couple bazaar-style launchpads, instead of the current centralized isolated paradigm used in Launchpad.net. This would also help to avoid fragmentation after the release of the Launchpad source code.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Matthew Paul Thomas (mpt) said : 		#1

In bug 50699, Mark Shuttleworth said "A better engineering solution to this would be federated communication
between bugzilla instances, and roundup, and sourceforge, and Launchpad ... However, it will take time to put the relevant standards and APIs in place to make all of those codebases exchange information automatically".

So yes, there are "plans" in the sense that we know we will need to support federation. There are not yet "plans" in the sense of detailed specifications for what those APIs etc should be. If you have ideas for those, we welcome your comments on the launchpad-users mailing list.

Revision history for this message
Steven Garrity (sgarrity) said : 		#2

Does the recent open-source release of Launchpad affect this question?

Can you help with this problem?

Provide an answer of your own, or ask Marcus Granado for more information if necessary.

To post a message you must log in.