Difference between revisions of "Broedplaatsen open dag 2013-09-21"
m |
m |
||
Line 35: | Line 35: | ||
=== Notes === | === Notes === | ||
− | My quadcopter is in a constant state of disrepair... say 7% fixed, 3% actual flying, 90% broken. [[User:Ultratux|Ultratux]] 12:13, 18 September 2013 (CEST) | + | * My quadcopter is in a constant state of disrepair... say 7% fixed, 3% actual flying, 90% broken. [[User:Ultratux|Ultratux]] 12:13, 18 September 2013 (CEST) |
− | I'm torn between having one huge thing 3D printed as a demo, or having it available for requests... I think the first is better, because requests -however small- still take up too much time to wait for it to finish. | + | * I'm torn between having one huge thing 3D printed as a demo, or having it available for requests... I think the first is better, because requests -however small- still take up too much time to wait for it to finish. |
Revision as of 11:25, 18 September 2013
Broedplaatsen open dag 2013-09-21 | |
---|---|
Date | 2013/09/21 |
Time | |
Location | h(ACTA) |
Type | Festival |
Contact | Contact |
Contents
Program
to be announced
Who will be there
Brainstorm about what we could do on that day
Workshops / demo's
- solder workshop (with techinc cards or something else?)
- learn how to design a simple thing which can be 3d-printed
- lockpicking (ask the people from Toool)
- make a phone/tablet/laptop sleeve (Narya)
- make bristlebots
- arcade demo
- quadcopter demo
- maybe overflow/integrate with our corridor (arcade or other 'installations' outside the space)
- ...
Talks
Short presentations (~5 min each), or max 15 min for more complicated subjects
- introduction to linux
- GNU30? - some instructions/showcase of GNU and OSS?
- Narya: bookcrossing and/or something about browser plugins like adblock plus, ghostery, https everywhere, etc
- ...
Notes
- My quadcopter is in a constant state of disrepair... say 7% fixed, 3% actual flying, 90% broken. Ultratux 12:13, 18 September 2013 (CEST)
- I'm torn between having one huge thing 3D printed as a demo, or having it available for requests... I think the first is better, because requests -however small- still take up too much time to wait for it to finish.