Skip to content

Instantly share code, notes, and snippets.

@SunboX
Last active November 10, 2015 17:33
Show Gist options
  • Save SunboX/6b04afa5b18466923b5c to your computer and use it in GitHub Desktop.
Save SunboX/6b04afa5b18466923b5c to your computer and use it in GitHub Desktop.
meeting.md

• Your topic

Transforming a Firefox OS Phone into a SMS Gateway Server

• Where you're planning to present it

at the OpenTech Summit '16 in Berlin

• Size of audience

50 to 150 people (depends on the room I get)

• How long the talk will be

45 to 60 minutes (TBD)

• Who they are, eg conference attendees, students in a speech class, etc

conference attendees, mainly hackers, tinkerers, creatives, developer, …

• Your call to action- what you want them to do, how you want them to feel

I want them to feel inspired, incited, enthusiastic, empowered

I want to show them how easy it is to get something done using Firefox OS, that's otherwise a lot more difficult to do using other tools.

My call to action is: Try to hack on Firefox OS yourself. Not only like "hacking apps" or add-ons, but also hacking Firefox OS itself. It's open, free and it's easy to start building great things with it. There's even cheap hardware all around, with sensors, cameras, bluetooth, wifi, gps … things you can't get this easy and cheap with your famous hacker board.

• Share any slides you have for the talk, if relevant

http://andrefiedler.de/slides/sms-gateway-server/
use arrow keys to change page, slides are not finished yet, needs some more polish

• And finally, what do you most want to get out of the coaching?

Some tipps and tricks how to better react to people's "mood" while speaking. How to speak more freely. How to better organize my slides.

I'm always feeling like I did fuck it up while speaking. But afterwards some poeple come to me and tell me that it was great. How can I better reflect this while speaking?

I already learned, that (normally) every talk should have a call to action. Are there more general "things, good to know"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment