Skip to content

Latest commit

 

History

History
67 lines (44 loc) · 4.31 KB

Organizers.md

File metadata and controls

67 lines (44 loc) · 4.31 KB
Raw

International NodeBots Day Organizers

Want to organize a NodeBots Day near you? You should. This is a community event and it will be largely what you make it. A few of us have organized similar events and here we'll share some of the things you'll probably want to pull together and what's worked for us.

Follow @nodebotsday for details and join the NodeBots Day Google Group for updates.

NOTE: Organizer G+ Hangout on Sunday 7/21 at 6:30pm US Pacific Time.

The Basics

  • Get a space.

    • There will probably be some people who are going to be soldering. Make sure there's an area that's well ventilated for this.
    • Make sure there are enough tables and power outlets/strips for everyone - you'll need enough hookups for computers and robots.

  • Food, snacks and beverages

    • Warning: this can eat up a lot of your money. This is a great contribution/sponsorship oportunity.

  • Signup form

    • If you don't need to collect money from anyone, I'd be happy to add a Tito event page for you. Create an issue or mention it in the pull request for your event and I'll add you. https://tito.io/nodebotsday/

Hardware

  • Another area where you can sink some money into this event.
  • Note that you could potentially run this totally BYOH (Bring Your Own Hardware).
  • Bringing in a diverse spectrum of Arduino, Raspberry Pi, sensors, copters, robotic arms, etc makes things fun. Get creative, but above all elicit contributions!
  • Not hardware necessarily, but cheap and immensely useful:
    • popsicle sticks of different sizes
    • glue gun(s) and glue sticks
    • spare cardboard
    • exacto knives/box cutters
  • Starter kits that may be useful:

Discounts

* Sparkfun Educational discount for NodeBots Day (valid for organizers and participants)

  > 20% off orders of $50 or more at sparkfun.com
  >
  > code: D2BBA6813A10
  >
  > expires: 7/20

Recent email that went out to organizers:

Hello Organizers!!

  1. NodeBots Day is coming up! 7/27 is the day, hardware hacking is the game. Please be sure to keep up with the repo at https://github.com/nodebots/nodebotsday. Star it, watch it, whatever. Just try to keep up with the changes so we're all on the same page.

  2. The NYC group is hosting an organizer hangout on G+ tomorrow (Sunday, June 22) at 6:30PM US Pacific Time. (I'm sure @buritica will send out the link on Twitter, and a bunch of us will RT it.) Please join us if you can!

  3. There have been many questions about signups/tito.io/etc. Due to a slight misunderstanding of the current state of tito.io, we've got a couple of options:

    • We will give one representative from each location access to the global nodebotsday tito account - we will trust you via the Honor System to not futz with any other city's event page.
    • We will get you an invite to your own tito.io account.

    Whichever you choose is totally up to you. We have already created event pages for some cities, wherein people have started registering their interest. You'll want to create actual tickets of your own, similar to what the Tri-Cities have done: https://tito.io/nodebots-tricities/2013. For SF, we'll be having multiple type of tickets, i.e. BYOHardware, BYOBeverage, BYOFood. If you decide you want your attendees to pay, you'll have to go with option B.

    Please let @rockbot know if you'll be going with option A or B. If I don't hear from you by Wednesday, I will assume you're just going to do your own thing ;-)

  4. At the end of the day, this is your show. @dshaw has lovingly referred to the entire event as "collaborative anarchy." You can do whatever you like, so please do! We'll share our collective experiences in a post-mortem of some sort (so remember to take notes) :-)

  5. Thank you, thank you, thank you for taking charge for your community. This is going to be an incredible event - more details to come!

By all means, if you have any questions, collaborate with the rest of the group via the issues in this GitHub repo.