-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Camp JS III Melbourne + NodeBots? #10
Comments
Should be doable. What facilities are available and the expected group size? The need for reliable internet to be able to install packages and not too big a group relative to the helpers is really the key. |
I'm sure there will be internet connection, but it's very hard to scale it properly. Last time we had local npm mirror on 70gb usb stick :) - see campjs/campjs-iii#3 campjs/campjs-iii#4 I'm not sure about group size - @timoxley can you give estimates for campjs iii? My guess total is around ~200 but hardware subgroup is smaller |
The workshops will be limited to 20 people this year and can run up to 90 minuts with a minimum of 2 tutors. See http://campjs.com/cfp.html |
90 minutes is not much time to get someone up, running and hacking on some hardware... especially given some of the related problems we've seen with getting running. We'd need to have pre-built environments or something maybe?? |
Hmm that's quite true. Perhaps browserbots might be a good way to get everyone going quicker ;) I'll try to get a demo video out sometime in the next week. |
I actually suggested this to Tim the other day and we thought it would be good. Your right about the setup time but hopefully most people at this event will already have dev tools installed and should be a much smoother process... Also the workshops repeat so maybe the initial aim is get the environment setup and the sample code working. From there there is going to be heaps of people around to help with how do I us this particular sensor, etc. What do you think the chance of getting the NICTA boards again would be? |
@AnnaGerber ping @ajfisher 90 minutes is just a guideline, understandably hardware will take longer. Also should try make sure there's enough units that people can take them back to their desks and work on things over the weekend; workshops are sort of supposed to be starting points/inspiration for the sunday night demos |
perhaps 90 mins is a good constraint though, pre-built environments might be a better place to start from |
we're estimating 150 total for the event, but it's hard to gauge ahead of time. |
also can we move this discussion over to https://github.com/campJS/campjs/issues? |
Would be cool to have mini nodebots session @ CampJS Melbourne. Is this something possible to organise by May 23?
The text was updated successfully, but these errors were encountered: