-
Notifications
You must be signed in to change notification settings - Fork 70
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
Tesselcamp New York September 1-3 2016 #179
Comments
This sounds amazing. Do you have probable dates yet ? Would love to attend if possible. |
Most likely August 25-27 or September 1-3. Hope you can join us @tikurahul! EDIT: Confirmed September 1-3. |
I can make it if its Sept 1-3. I have another event on Aug 25-27 😢 |
I think I can make Sept 1-3, too :) (and practically the only reason I'm stating this in a lengthy comment is to subscribe to e-mails on this issue 😁) |
Interested. Will look into getting there. |
Update:
|
Update for everybody: I added some logistics to the top :) |
Agenda items transfered from SC meeting https://github.com/tessel/project/blob/master/meetings/2016-08-23.md @tcr SC: Reach and new hardware |
It's worth noting that @rwaldron's request is likely resolved via tessel/t2-firmware#204. |
When & where?
New York City, September 1-3
Sept 1&2: 61 Local in Brooklyn (Thurs/Fri)
Sept 3: Saturday at WeWork Times Square – please RSVP!
What is it?
Time & space for people to contribute to the Tessel Project. The basic objectives:
What isn't it?
A conference, party, or actual camping trip (this time). It's simple, it's small, it's not something we're planning to sell tickets to or broadly advertise. There might not be any food, drinks, swag, or budget, because that's not the point.
How big is it?
Small. Attendance cap ~20 people probably. Includes all Steering Committee members, any Team Members who can make it, and then anyone who's interested in getting involved (assuming there is still space).
What specifically are we going to do?
Good question. Submit ideas to this issue!
cc @rwaldron @HipsterBrown @tcr @johnnyman727
The text was updated successfully, but these errors were encountered: