-
Notifications
You must be signed in to change notification settings - Fork 12
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
FAQ Page #10
Comments
So.. I propose.
Every single nodebots event from last year (That @acingraham, @rwaldron and I ran) included a 5-10 person circle that did a blinking lights example. (Usually had about 15 - 20 people.) So I think this might be a good split. People who don't need the intro get to share and hack, people who do get to learn together. There are plenty of cons however. Alternatives might be doing the beginner workshop a few times with 15 people. I'd like to have a conversation about what people think of the two track proposal. |
I'm more interested in Track 1 (getting time to show off + feedback and tips) but I took advantage of a Track 2-style workshop in 2015 and that was so invaluable and eye-opening! I can't offer up a space but if its a matter of human resources I'd be happy to volunteer to help run a larger event. |
I like both track. Maybe we can split a night into having a hack and tell type format and then On Friday, January 8, 2016, Byron Hulcher [email protected] wrote:
|
The splitting of events is mainly due to bocoup only sitting 15 people with tables and power. |
I'm an organizer for the NY JavaScript Meetup and we've had a lot of Additionally, at NYJS we rely heavily on trial-and-error to figure out what |
Yeah, it's working out so far, we should probably make this page now |
Before attending a Nodebots event, there might be some frequently asked questions we can address up front. Some that come to mind:
We can create a separate page to cover any questions constantly come up at events or about the events. If a question isn't covered, we can link to the repo's issues page for people to ask there. AND/OR link to the BoroJS #nodebots Slack channel.
The text was updated successfully, but these errors were encountered: