Other Launchpad intalls in use?

I’ve been wondering about this for a while: Are there any other installations of (the wonderuflly AGPL’d) Launchpad in use by a project (or group of projects)? And, if so, are they doing any fancy distributed bug tracking awesomeness like the bug comment import feature with bugzilla? It would be great to see how other groups use the power of Launchpad in their own way.

What might even be more interesting is if a development company was using Launchpad as their internal dev platform (because they either didn’t want to pay Canonical to let them host a proprietary project or they simply wanted all their development to be hosted on their own servers); how are the features of LP either used or not used in that case?

flattr this!

6 comments.

  1. I wanted to have my own instance a while ago, mostly for the bugs and maybe the answers and blueprints parts, but in its current form, installing and maintaining up-to-date such a beast is a nightmare. The install guide is oriented toward lp.net developers and contributors, not toward sysadmins wanting their own instance. The code is nowhere near a packageable state (at least it wasn’t last time i looked). I guess the latter has been made on purpose – or should i say, no effort has been made in that direction – and that won’t change anytime soon, unless someone else grabs it and rounds all the corners to make it fit. (i even considered doing it as i like creating complex packages, but it defied my purpose, which was to spend more time in my various projects by using more efficient tools and less on maintaining those tools).

    I’d be happy to learn that someone is working on this.

  2. You might be saddened to know that the guys working on launchpad in #launchpad on freenode officially suggested I _not_ setup another launchpad instance. Some of these people were Canonical employees.

    I wanted to play with mirroring the gnome bugzilla in a dev launchpad instance just to see how the software worked. I was primarily told that launchpad (as software) is unable to sync with another launchpad instance and would be strongly discouraged from doing what I’d envisioned. I was also told that while they were very interested in any improvements that I might make, they did not want another big launchpad instance. They promote launchpad.net as a service vs launchpad as an open source bugtracker.

    So… my official opinion on this is that Launchpad is dumped code that is not really a community effort. Canonical is against any competing big launchpad installs and is very uninterested in splitting parts of it off such as Malone so that someone can use it as a stand alone bugtracker.

    If you really want, I can dig up IRC logs of these conversations. Email me for more details.

  3. I highly doubt it. I’ve been trying to set it up in a VM at work for a few weeks now, and it is very much impossible. The lack of / incomplete / incorrect documentation, bizarre deployment process, and hidden / unavailable components makes for way too high of a secret sauce to normalcy ratio for any human to figure out. We’d *like* to use it for a group of projects (both FLOSS and proprietary, both public and internal), but so far my attempts to give it a trial run have been an utter failure.

    At this point we’d rather just pay Canonical to do it for us, but they don’t offer hosted instances that could use our domain name & branding, so sadly that’s not an option.

  4. One of my authors has tried installing LP briefly after it was made available under AGPLv3. The resulting article (in German) shows that it was quite tricky.

    http://www.linux-magazin.de/Online-Artikel/Ubuntus-Softwareprojektverwaltung-Launchpad-selbst-installiert

  5. http://lists.debian.org/debian-devel/2010/09/msg00539.html

  6. I was looking at various build systems and bug tracking tools for Mageia, but it seems that I am not the only one who faced some issue when trying to host launchpad.

    That’s unfortunate, because after all the communication that was made about launchpad being opensource, people who look at it see that it benefit to almost no one except Canonical. And after all the discussion about contributing upstream, this is not helping Canonical reputation in free software land.

Post a comment.