fsuk-manchester
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fsuk-manchester] Follow-up: MFS Meeting. Tue, 21 June. Talk: "TTIP


From: Bob Mottram
Subject: Re: [Fsuk-manchester] Follow-up: MFS Meeting. Tue, 21 June. Talk: "TTIP and software freedom"
Date: Wed, 6 Jul 2016 09:12:10 +0100
User-agent: Mutt/1.5.23 (2014-03-12)

On Wed, Jul 06, 2016 at 08:21:57AM +0100, Michael Dorrington wrote:
On 26/06/16 13:49, Michael Dorrington wrote:

course, it must all be software freedom related.  We could break the day
into 30 minute chunks and delegate those out to people.  We could have
items such as Arduino, coding workshop, software demos, talks on the
social, legal, philosophical side of software freedom and so on.  These
items should be aimed at the general public who might be interested in
software freedom but might not even know about it yet.

We'll discuss this at July's meeting, on the 19th, and also on this list.

Ideas for possible talk this month, let me know what you think.

Free Hardware talk:
* Libre Tea Computer Card:
** https://www.crowdsupply.com/eoma68/micro-desktop
* Respect Your Freedom:
** http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
* Intel Management Engine:
**
https://www.fsf.org/blogs/licensing/intel-me-and-why-we-should-get-rid-of-me

Vim talk:
* http://www.vim.org/

Rockbox talk:
* http://www.rockbox.org/
* Some who has used Rockbox would have to volunteer to do this talk.

Beagleboards talk:
* http://beagleboard.org/

Or something else.



Free hardware is topical. There has been a lot of chatter about the
eoma68.

I think we're still in the very early period of free hardware
designs. Some people are saying that we also need the designs of
individual chips to also be free, and for circuit boards to be
verifiable against some known design, but I think if that happens it's
at least five years into the future. For now it's a mixed picture with
possibly bad firmware (not just ME) lurking in the background on
practically all systems.

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]