Spanish language GPL need to be shipped in builds

[mako]

As part of solving the #4265 and coming into compliance with the GPL and with the spirit of free software, several change to the current builds are needed.

One easy step will be the inclusion of a Spanish language GPL in each build. Ideally, this should be done in the content library and in the olpc-licenses package.

SJ should be able to handle the content library and Dennis should be able to add this to the next version of olpc-licenses.

[gnu]

The FSF provides Spanish language translations of GPLv3 and GFDLv1.2 on its Translations page:

http://www.gnu.org/licenses/translations.html

There are various other languages represented, which are of interest to OLPC, such as French, Italian and German. The page also includes instructions on how to make your own translations into new languages, and submit them to FSF for sharing.

Large numbers of translations of GPLv2 and LGPLv2 are available in the Internet Archive's preserved copy of that page, from 2007. These also include Arabic, Brazilian Portuguese, etc. See:

http://web.archive.org/web/20070623052116/http://www.gnu.org/licenses/translations.html

I have asked FSF to restore the translations of older license versions (since lots of software is still governed by older licenses), but meanwhile, you can use the versions from the Internet Archive. Enable Javascript when accessing that page, which rewrites the URLs in it, so you will be able to click through to the archived translations themselves from 2007.

For Spanish, here are the exact URLs to use:

GPLv3: http://www.viti.es/gnu/licenses/gpl.html

GPLv2: http://web.archive.org/web/20070624222334/www.garaitia.com/new/gpl-spanish.php

LGPLv2.1: http://web.archive.org/web/20070621203137/gugs.sindominio.net/licencias/lgpl-es.html

GFDLv1.2: http://curso-sobre.berlios.de/gfdles/gfdles.txt

There are several other Spanish translations of GPLv2 available above, if you don't like this one. There's an HTML GFDLv2 as well as the text one linked here.

Let's get the Spanish versions into the release, and then somebody can make a management decision about what other languages to include, and where.

Note that the English versions must remain in the release as well. The translated ones are all unofficial: they are for ease of understanding, but they have no legal effect.

[gnu]

I recommend adding it at /usr/share/licenses/common-licenses/GPL-2.es and GPL-3.es . Then the Spanish translation of the Sugar notice in #6929 can point to the GPL-2.es version.

(The Spanish version shipped should also include a link back to the English version).

[gregorio]

SJ,

Last call to get this done. It has to be in by this week, preferably first half.

I can't hold the release for it so I'm removing blocker status but leaving it as important (keyword blocks-:8.2.0)

Thanks,

Greg S

[dsd]

mako, Seems easy enough to add GPL2.es to the olpc-licenses package. Was this content generated automatically? Any git repositories or anything like that?

Where can I find the source RPM? Does it come from koji?

[gnu]

The source and binary (noarch) RPM's appear to be here: http://dev.laptop.org/~mako/ I agree that they ought to be put somewhere where the package tools can find them, e.g. so the source package gets into the source release.

[gnu]

Oops, those are the olpc-LIBRARY rpms, not the olpc-LICENSE rpm's. Sorry, false alarm.

[dsd]

I found the SRPM in ~mako/public_rpms, that should be good enough to start from

[dsd]

OK, I imported it into git (users/dsd/olpc-licenses) and released version 2 through my public rpms. I also filed #8043 to follow up on shipping more translations, and #8044 for updating the license collection to reflect the software shipped in 8.2.0.

[mako]

Ah, thanks DSD!

The code I use to generate the SRPM is in a Bazaar repository here: http://projects.mako.cc/source/olpc_license_package

That said, it's basically static files so the SRPM is basically equivalent.

Thank you so much for your work on this. This is important, mostly thankless, work but it does a lot for OLPC and the users of its machine in terms of software freedom.

[dsd]

Thanks for your input! So, you created LICENSE_LIST by hand and then just copied the appropriate license files into place?