[Olpc-uruguay] Violación de GPL (era Re: Uso de XO en Secundaria)
Santiago Ferreira
santiago.ferreira en gmail.com
Jue Ene 19 03:50:33 EST 2012
A no perder la fe Flavio, por ahi hacemos un poco de palanca con la
mano de Sebastian y llegamos a buen puerto.
saludos
Santiago
2012/1/19 Flavio Danesse <fdanesse en gmail.com>:
> Lo que pasa es que este tema es recurrente en esta lista desde 2008.
> Ya todo el mundo está al tanto de este tema y cada uno tiene su posición al
> respecto.
> Es decir, de vez en cuando alguno nuevo en la lista se entera de estas
> cosas, comprende la situación, y patalea, pero para la mayoría de nosotros
> esto no es un tema nuevo. Si nada pasó en casi 4 años, no hay motivos para
> pensar que pase algo ahora.
>
>
>
>
> El 19 de enero de 2012 00:07, Sebastian Silva <sebastian en somosazucar.org>
> escribió:
>
>> Hola,
>> Perdón que meta la cuchara:
>> Interesante que este email, amablemente retransmitido por Guillermo, no
>> haya
>> pasado moderación en sugar-devel...
>> Lo he remitido a la lista de SLOBs para insistir en que sí hay una
>> violación
>> (la posición de Walter ha sido que no la hay en tanto que Sugar puede
>> ejecutarse
>> dentro del directorio del usuario).
>> Quiero tratar de ayudar a que se de un diálogo útil y se tomen medidas
>> para
>> subsanar esta situación.
>> Desde la perspectiva de la comunidad Sugar uruguaya,
>> qué puede hacer Sugar Labs central con respecto de esta situación?
>> Un comunicado / declaración oficial sería lo que yo veo más viable.
>> Saludos,
>> Sebastian
>> Oversight Board Member (SLOBs)
>> Sugar Labs
>>
>> El -10/01/37 14:59, John Gilmore escribió:
>>>>
>>>> Here in uruguay xo`s are distributed with no permission to install rpm
>>>> or
>>>> modify udev rules, so is very important to have this rules added to work
>>>> with buti=E1 2.0 and nxt in a near future.
>>>> Regards
>>>> Andr=E9s
>>>> we can add it, but clearly it would be best if deployments or even
>>>> local classrooms could add new device capabilities on their own.
>>>> because as soon as we say "great, we're done", someone will create
>>>> a new USB device that kids and teachers everywhere will want to use.
>>>
>>> Paul, that's a great "open source" reason to ship software that users
>>> can revise and control. But there's a better "free software" reason:
>>> the license requires it. See:
>>>
>>> http://www.softwarefreedom.org/resources/2008/compliance-guide.html
>>>
>>> Every laptop that OLPC sells to Uruguay produces a violation of the
>>> GPL, i.e. a copyright infringement. Copyright infringement is a
>>> serious crime and tort, with serious penalties for intentional
>>> infringement. Even the sympathetic grandmas who infringe the
>>> copyright on a few songs are getting hit with multi-hundred-thousand
>>> dollar penalties, in jury trials, besides having the expense of
>>> defending themselves in federal court. OLPC would be bankrupt if
>>> found guilty of selling hundreds of thousands of infringing copies. I
>>> have never understood why OLPC sees this as a prudent risk to take,
>>> when the cure is simple: stop infringing; give the end-user kids
>>> control of the software on their laptops. But if you insist on going
>>> down the lawsuit path, I'll help to make it happen.
>>>
>>> 2012 is likely to be the year that either that OLPC laptops stop going
>>> to Uruguay -- or the year that OLPC and the local Uruguay team change
>>> their systems to follow the copyright terms on the software they ship.
>>>
>>> I wrote some of the code in that laptop. I donated it on the basis
>>> that it would always remain free software. I am sick of seeing it
>>> turned into proprietary binaries to trick innocent kids with. The
>>> OLPC organization and community has been on notice about this since at
>>> least 2007. Enough is enough.
>>>
>>> John
>>>
>>> PS: udev is only under GPLv2, as far as I know, so this particular
>>> issue about plugging in USB devices is not a copyright issue, merely
>>> an issue of stupidity on the part of those who lock down the software
>>> distribution against end-user modification. But plenty of software in
>>> the OLPC is under GPLv3, which *does* require that the keys and/or
>>> passwords needed to modify or reinstall that software be given to the
>>> end users of consumer goods like the OLPC.
>>>
>>
>>
>> _______________________________________________
>> Olpc-uruguay mailing list
>> Olpc-uruguay en lists.laptop.org
>> http://lists.laptop.org/listinfo/olpc-uruguay
>
>
>
> _______________________________________________
> Olpc-uruguay mailing list
> Olpc-uruguay en lists.laptop.org
> http://lists.laptop.org/listinfo/olpc-uruguay
>
More information about the Olpc-uruguay
mailing list