So I was brave and put up something at the CfP of 32c3, which to my own surprise was accepted. The talk started as an vague idea to tell something about open hardware (namely about the Pandora/Pyra) and how to make it happen. After a bit of conversation with the guys of 32c3, I ended up to make it a bit wider view and here is my rough idea so far: I will talk about 3 projects I am/was involved: - Mooltipass (which I basicly supported by crowdfunding and involved an artist from outside) - Senoko [Battery board of the Novena] (where I did a production run to supply some community guys with hardware) - Pandora/Pyra: Here I intent to make it more a perspective of the community than mine own (which are quite limited). And now to the tricky part: As I started with one topic and now somehow ended up with 3 and there is no way to get more time for the talk, I have 30min (Talk and Q&A). My rough "timetable" is this: 5 min Mooltipass 10 min Pyra/Pandora 10 min Senoko some sec concluding/ dos and don'ts comparison ("What you get back": something like really cool, spyfree, open devices/ nice feedback) 3-4min Q&A That is truly quite short amount of time, so I'd like to have some feedback what should be in the talk of 10 min with the main thought in mind: "How to make open hardware happen and what you can do about it without being a hardware/software designer" Aspects I was thinking about myself are: -Never give up (revive of the Pandora) -Learn and repeat (lessons learned made the Pyra development much better) -don't hide anything (people will accept communicated fails and accidents, but will be pissed, if someone trys to cover them up) -involve the community (make what the customer want and endure the very long discussions/ get a keymat designer) So for that part I need some inspirations and facts I might have not that correctly present. It's the basic concept so far and I might put some aspects from the projects in the conclusion part, but this is where I basicly start right now.