[Dev] [libreplanet-discuss] Misleading information in EOMA68 news

Christopher Waid chris at thinkpenguin.com
Fri Aug 26 03:22:57 GMT 2016

On 2016-08-25 10:22 PM, Tiberiu-Cezar Tehnoetic wrote:
> On 26.08.2016 05:16, Christopher Waid wrote:
>> On 2016-08-25 06:26 PM, Tiberiu-Cezar Tehnoetic wrote:
>>> On 25.08.2016 15:47, Tiberiu-Cezar Tehnoetic wrote:
>>>> On 25.08.2016 15:25, Adonay Felipe Nogueira wrote:
>>>>> This issue of "you said it is 'libre' but I prove it's not", and 
>>>>> even
>>>>> the issue regarding the older publication on ThinkPenguin's site,
>>>>> can be
>>>>> easily solved by changing terms/words accordingly there. There's no
>>>>> need
>>>>> to make everyone mad at each other.
>>>> It's not just about terminology. It's about deliberately 
>>>> misinforming
>>>> the people to back your project because it's been libre hardware and
>>>> libre software "right from the beginning". And also misinforming 
>>>> people
>>>> to think it's OK for their freedom to buy laptops with proprietary 
>>>> BIOS
>>>> rather than with Libreboot.
>>> Richard Stallman has just confirmed me that FSF has not received the 
>>> PCB
>>> design sources along with the Libre Tea Computer Card.
>>> I hope that now everyone understands that this EOMA68 board is *not*
>>> libre hardware as claimed.
>> That doesn't make it "*not* libre hardware" as far as the FSF is
>> concerned. The FSF *DOES NOT* require the PCB designs for RYF.
> RYF doesn't certify free hardware design. But "libre hardware" means
> free-design hardware and that is explained in this essay you should 
> read
> sometimes:
> https://www.gnu.org/philosophy/free-hardware-designs.html
> Using the definition there, of course EOMA68 computer is *not* "libre
> hardware".

Actually it is libre. The hardware has not been shipped.  Everybody who 
has the devices has the schematics and rights thereof. You don't have to 
give the source code to random people, just those you give the binary 
to. In similar terms there is no reason this should not be true of libre 

More information about the Dev mailing list