forked from railsbridge/docs
-
Notifications
You must be signed in to change notification settings - Fork 0
Installfest Tasks
lilliealbert edited this page Aug 7, 2012
·
18 revisions
- Depending on the space you are in, it's easy to let people slip by without checking in. Don't let them! People will show up early. Sometimes 30 minutes early. Be ready. It helps to have signage stating that everyone, including volunteers, needs to check in and make a name tag.
- Tip: set up the welcome desk (with clear signage) before setting up the rest of the Installfest. People will make themselves at home, so if you need to bail on that setup to check people in, do it!
- Use the pre-workshop survey results spreadsheet to check people in. If someone didn't take it, ask them to get out their laptop and take the damn thing right there.
- For those who did take the survey, tell them their class level and a brief description of what it means. People tend to horribly underestimate their skill levels, so encourage upward shifts. They can always change classes during the workshop.
- When volunteers check in, have them mark their name tags in some way (star stickers or a drawn star have worked). Make sure the students know they should not be shy about asking anyone with a star (or your chosen signifier) for help.
- Having one person checking people in works well at first, but around start time, there will be a crush of people. If you're using Google docs for the survey form, share the survey results spreadsheet with the second welcomer so you can have two lines.
To Do: further questions to get people to admit their actual skill level
- Power outlets will guide how the Installfest space is set up, but Railsbridge's rolling chest of power cords should help with that quite a bit. The Installfest should be one big room with different tables, ideally marked with OSs so that folks with similar issues can help each other. (This usually means getting more granular than just Mac/Linux/PC and breaking out older Mac OSs into their own pods.)
- Post the wireless SSID & password often and visibly.
One (or two) people should own the updates. If you have someone around who has commit rights, they can merge your pull requests live. If not, fork the Installfest and use your own app like so:
- Fork the installfest app somewhere in here: https://github.com/railsbridge/installfest
- Create a heroku app named like: http://installfest-railsbridge46.heroku.com, push to that app
- Make changes and every time a change is made, push and tell the organizer or announce the change
- Submit a pull request (Even if a pull request is not accepted as is, it still helps prompt a solution, so don't worry if your requests don't get accepted verbatim.)
- At the end of the evening, delete the Heroku app, and tell students the canonical URL is http://installfest.railsbridge.org
To Do: More detailed instructions on doing this, for people new to Github.
- Wireless bandwidth is always difficult at workshops. Preparing for this and communicating it repeatedly to your students is the best bet, but people will still show up at the Installfest not having downloaded gargantuan necessary files. Having said files on flash drives will help dramatically, so make sure to have those. And don't lose them!
- As an organizer, people will expect you to solve their problems. Help them if you can, but if someone asks you about something outside of your expertise, delegate swiftly and without guilt. If it's 7pm and it looks like it's going to be 6 hours for a student to download a necessary file, this probably isn't the weekend that the workshop will work for them. Since we do this regularly, telling people that they can't do the workshop this time isn't the worst thing in the world. It sucks, but it's better than having someone sitting in the workshop on Saturday unable to do anything or derailing their section because of their incomplete install.