-
Notifications
You must be signed in to change notification settings - Fork 1
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
July 2nd Dry Run at NPM Inc. #38
Comments
damn, I can't make it during the day, but will ping everyone later that day to see if you're still going. |
Heads-up from the NodeSource team: have had some long-planned team activities that are clashing with this meetup tomorrow, so many of us won't be able to attend. As this is a rare opportunity for us all to be physically together we've tried to squeeze maximum value out of it and the overlap wasn't intentional but the dry-run booking wasn't firm enough in any of our calendars to be an obvious conflict. Unfortunately we are going to be much closer to the NodeConf venue than to Oakland making logistics nearly impossible. Those of us who are taking primary responsibility for workshops will be ensuring that at least one other member of that workshop team is fully up to speed on the workshopper and able to represent it in whatever capacity is required. We can also make ourselves available via Hangouts at any time during the afternoon with a small amount of warning if required. We'll also be at Walker Creek Ranch close to the early bus arrival time if anyone wants to catch up. Sincere apologies from me and the team, be assured that we're putting in much blood, sweat and tears into making our workshoppers an unforgettable experience for NodeConf attendees! Good luck all! |
@rvagg the main purpose of the run-through was to have a few people who aren't running that workshop try it in order to test it a bit. Could you make sure that any people who won't make it post their materials here so that those attending can go through it and log bugs prior to NodeConf? |
Since this is tomorrow. Whats the lunch venue or do we all go to npm office at noon ? |
Let's meet at NPM and then head to lunch, we don't entirely know how many people will be there and that will effect where we can go :) |
i'll be there |
i leave NYC at 8am, so i'll be there around noon. What is the address of the npm office? |
We're at 200 Frank Ogawa Plaza, Oakland. If you're taking BART, you'll want either the Pittsburg/Bay Point or Richmond-direction train. Get off at 12th Street Station. Go out the exit that says "Frank Ogawa Plaza." Upon exiting the station, you'll see City Hall and a massive oak tree to your left. To the right of city hall is a brick building with a ground-floor food establishment that's called the Rotisserie Deli (I don't recommend eating there, though). That's our building; our door is just around the corner (towards City Hall). Please smile at the receptionist, as that's your first requirement to making it up to the 5th floor :-P |
Just hit town, I'll see you all tomm :)
|
Was hoping to make it to enjoy everyone's presentations, but alas final prep for SO tech-track and sick kids means I am staying closer to home. |
I'll bring the chrome books with me, i'm sure someone can hack em :) |
No problem, I'm happy to work on the chromebooks Lyle! Don't leave for lunch without me everyone!!
|
bah, running late. see everyone after lunch! |
Lyle - can you try getting some light cardstock or other thicker paper to On Wed, Jul 2, 2014 at 12:12 PM, Elijah Insua notifications@github.com
|
P.s everyone is invited to come hang out at Oakland.JS tonight On Wed, Jul 2, 2014 at 12:16 PM, Max Ogden max@maxogden.com wrote:
|
Hey everybody,
On July 2nd we're scheduled to get together and try to run through each others' workshoppers. @isaacs has been kind enough to let us host everyone at NPM Inc in Oakland, CA.
The plan is to get lunch at noon somewhere in Oakland and then head to the NPM offices. We should be there until 4 or 5 at least. Open to suggestions for a spot that can hold lots of people (cc @maxogden).
@dominictarr
@Raynos
@othiym23
@nvcexploder
@substack
@thlorenz
@feross
@tmpvar
@mikolalysenko
@chrisdickinson
@hughsk
@rvagg
@ceejbot
@tjfontaine
@olizilla
@alanshaw
@rockbot
@rwaldron
@maxogden
@jlord
@visnup
@isaacs
@timoxley
The text was updated successfully, but these errors were encountered: