On Tue, Aug 31, 2010 at 12:02, Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: > Ęvar Arnfjörš Bjarmason <avarab@xxxxxxxxx> writes: > >> I've used Launchpad somewhat for translating and it's friendly to >> contributors & has an active community, but it seems to require that >> we BSD-license our translations[1], which would be a showstopper since >> we'd have to contact everyone who's been submitting GPL-2-only strings >> to Git for the last 5 years. > > I don't think so: > > ,----[ https://help.launchpad.net/Translations/LicensingFAQ ] > | I have no problem with BSD myself, but I also uploaded translations > | from upstream. What do I do? > | > | As long as the uploads were marked as translations that were published > | elsewhere, they fall under a separate copyright regime: those imports > | will retain their original copyright license. The BSD licence only > | applies to translations that are (as far as the system knows) original > | to Launchpad. > `---- > > So, my understanding is: Git's code, and strings, would remain what > they are, but things contributed _through launchpad_ would be BSD. Ah yes. It seems as if Git's strings and derived works would be marked GPL-2. That sounds good. Like I said I hadn't looked in any of this in detail, or the legal issues involved. Anyway, the main issue with Launchpad that I've had as a user/translator is getting translations back out of the system. To download a *.po file you have to log in and submit a request for a *.po file download. Sometimes it can take hours for you to get a mail back. Downloading a large amount of translations through this system in Launchpad would be very painful. But maybe they have a better API now that we could use. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html