William Grant, 2010-09-23 16:31:57 +1000 : [...]
> While Launchpad.net does not provide Debian PPAs, what prevents you from > taking the Launchpad code, rebranding it, and running your own instance? Based on a presentation given by Jonathan Lange (product strategist for Launchpad) at LSM this summer, the Launchpad code was never *really* intended to be run in other instances than launchpad.net. It was initially a “that would be nice” feature, but nobody really took some time to do it, and it wasn't a constraint taken into account when designing the evolutions. The code was eventually made publicly available after much nagging, but a friend of mine who tried installing it ran away screaming, much like I initially ran away screaming when I started fiddling with Sourceforge. It took several years (and two forks/renamings) to have *Forge packages that can actually be installed with a reasonably low effort. Also, still according to Jonathan, there are several people working full-time on Launchpad sysadmin at Canonical. We at Debian don't have that kind of resources. > It does require some changes to work with Debian's suites, but that > would be far easier than reimplementing all the functionality yourself. Given the above, I strongly doubt that. Adding PPA-like functionality to FusionForge *might* be easier, since we already have Alioth, but even that would be a significant amount of work, if only to setup the build-daemons for that new service. Roland, Source^WGForge^WFusionForge maintainer since summer of 2000 and *still* not quite mad (or am I?). -- Roland Mas Bada, bada, ba-da-da-daaa, doudou, doudou, dou-dou-dou-dou-baaa. -- in Song without words #1 (Paul Leavitt) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8739t0g8g3....@mirexpress.internal.placard.fr.eu.org
