-
Notifications
You must be signed in to change notification settings - Fork 0
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
KnodeCamp? #23
Comments
Let's do it. I'll brainstorm with the crew, but definitely cc'ing March 6th. What time? /me puts on her rally cap. On Thu, Jan 16, 2014 at 4:02 PM, Mikeal Rogers [email protected]:
|
i'm struggling with text for the website :) suggestions? |
"A Kuh-node.io Rodeo": KNODE.IO, 'a resource for all things Node.js', is hosting a **open for editing. We're goons. And maybe something about the format: lightning talk on a small event like On Thu, Jan 16, 2014 at 4:21 PM, Mikeal Rogers [email protected]:
|
I was thinking of explaining a little about knode and then describing what will be covered in the session. the space we have is pretty well suited to collaborative unconf sessions. I have an idea of doing unconf sessions along with impromptu lightning talks if people get inspired. |
Sounds good to me. Time of day this will happen? Just let me know what
|
daytime: 10am start, 2 hour break for lunch at noon, done before 6. |
Time to see who'll be down there to help me out :D On Fri, Jan 17, 2014 at 10:28 AM, Mikeal Rogers [email protected]:
|
So do we just come up with a plan for the event and then get back to you with it? |
Just reach out to the people you want to make sure are there, and we can create a discount code to get them in for free, so that the right stake holders are there that are in town. I'm going to try and get the tickets and website updates up today. |
Excellent. Will let them know. Thanks! On Mon, Jan 20, 2014 at 9:57 AM, Mikeal Rogers [email protected]:
|
Now that CouchCamp is cancelled I have a small space open for an un-conference at Joyent.
Interested in an in-person knode meetup?
@hackygolucky
The text was updated successfully, but these errors were encountered: