Skip to content

Questions

Jump to bottom
dapperAuteur edited this page Jan 2, 2018 · 3 revisions

Questions

  1. What costs are covered?
  1. As a host I need to judge about topics submitted to me. What are the criteria?
  • This really depends on the type of audience you are expecting. I know the Elixir community is pretty small globally right now, so it may be better to focus on elementary and intro topics to get people excited about Elixir and learn more about it. Like Gonto was saying in the meeting yesterday talks should be intriguing and not necessarily try to be a lecture, but rather fun and inspiring so that it makes people take action. This can be hard for intro based content since the basics have to be explained, but there are ways to make it fun. :)
  1. How could you motivate people to submit talks to your event? Since there not so many Elixir devs around. And it is quite challenging to find good talks.
  • This can be a challenge especially since the community is small. Generally, I think many developers would love to share their findings, but when you are just starting out it may just have to be you doing the talking for the first few meetups and setting the standard. When I worked with Chris from scotch.io to run CodeHearted in Las Vegas, the first 5 or so meetups it was just us two doing talks back to back, and at first we only had a few attendees because nobody really knew or cared - but after a little while the community embraced it and we had developers reaching out to us to organize talks.
  1. How to get feedback about talks? When? After the event or on the event itself? Should it be public or not?
  • Typically it's best to get feedback right after a talk. I really liked the feedback approach that Twilio implemented for their Signal conference, where they would give each attendee a card to fill out after the talk. I would keep these private, but would share a post mortem after with the community and address any concerns and also share the wins!
Clone this wiki locally