Closed rvagg closed 8 years ago
/cc @nodejs/addon-api, @nodejs/benchmarking, @nodejs/build, @nodejs/collaborators, @nodejs/crypto, @nodejs/docker, @nodejs/evangelism, @nodejs/hardware, @nodejs/internationalization, @nodejs/post-mortem, @nodejs/streams, @nodejs/tracing, @nodejs/tsc, @nodejs/website, @nodejs/membership
Native addons / node-gyp probably needs to be a topic of some sort. (NAN and Hardware WGs will def be interested)
Constructive discussion
Sounds like a Diversity / Onboarding this as well, should be good!
TSC Meeting
Aren't we only like missing Ben and Brian? Sounds like we could have one in person.
Awww... I love to participate in this and I am missing it. :cry: Do we have live streaming or something?
cc @nodejs/diversity
Regarding hardware, @Fishrock123 beat me to it! Native modules/NAN are a big focus for us, along with getting the necessary support in libuv and node core so that node-serialport can be pure JS (see https://github.com/libuv/libuv/pull/379).
Awww... I love to participate in this and I am missing it. Do we have live streaming or something?
:+1:
We also have plenty of opportunity for social items so we should absolutely include ideas about that as well (SF locals?)
+1 for social items to get to known one another. I'm staying in SF until Sunday if someone wants to link up during and after the summit.
@rvagg I can't confirm we can still use it right now, but if y'all are ok with going offsite to record NodeUp, New Relic's SF office has a recording room. Maybe @groundwater could confirm that it is ok to use for NodeUp.
I think that @nodejs/build @nodejs/lts @nodejs/smoke-test all should get together to come up with a way to better test highly popular community modules and their compatibility with newer versions of node. Smoke Test is just starting to work on this but it would be very important to the LTS and Build groups.
An example of why this is important is that the memcache module was broken for a bit because the underlying hashring module it relied on stopped building after an io.js release. The common data stores drivers (mongo, redis, postgres, memcache, etc), most common frameworks (express, restify, hapi), and probably common util libraries (underscore/lodash, async, gulp, grunt, etc) should all at least receive a heads up when a new version of node is coming that will break them.
I understand that build infrastructure isn't free, people's time is very limited, etc. But, if we want node to continue getting adopted by businesses, then we need to be able to really assert our stability. This doesn't mean changes that break modules like express should be rejected, just that express should get a heads up and it should probably thought about more critically if it is going to break existing versions of express.
For people needing something to do on the Thursday night of the summit and terrified of the prospect of it being something that doesn't have to do with Node, there's this: http://www.meetup.com/sfnode/events/223133402/
+1 on @wraithan's get-everyone-on-the-same-page-about-smoke-testing-with-npm. I know there's been some progress/discussion over in smoke-test the last few days, but there are still some unanswered questions. A face-to-face meeting seems like a unique opportunity to do a point-in-time document of what we know, what we plan on trying, and what is still up in the air. I'm happy to be the note-taker.
I posted some ideas at https://github.com/nodejs/io.js/issues/2213#issuecomment-124273228 which I'll summarize below.
Relating to some of the a higher level themes which I think would overlap the scopes of the website/marketing/evangelism/translation groups I think it would be good to have discussions (big or small) on a few topics:
Obviously the Tracing WG would like to bring up the tracing situation, and I'd like to see some discussion on debugging/tooling support.
More discussion on how to open up internals knowledge would be good too. There's been a bit of progress from the Docs WG on that, but it'd be good to keep things moving there.
Ok, I'm going to try and distill some of the thoughts here in to sessions and goals that we can use in the other thread.
It would be nice if some board members could be around for getting to know the community and vice versa. Wouldn't have to be for the entire conference, just a few hours or a session maybe. @rvagg /@mikeal agree?
WaffleJS Wednesday Evening
Isn't that on the 5th, the day before?
Isn't that on the 5th, the day before?
What better way to kick off the summit? :grinning:
It would be nice if some board members could be around
We can invite them over for lunch one day or for one of the evenings. I'm not sure how many are local though, maybe only a few.
We can invite them over for lunch one day or for one of the evenings. I'm not sure how many are local though, maybe only a few.
People can be busy so it's probably best to check sooner than later. :)
Proposal for a split session (1/hr w/ another 1/hr back-to-back) for Session 4.
People can be busy so it's probably best to check sooner than later. :)
I'll let the board know that this is happening along with the dates in Monday's meeting.
Just a heads up, @zkat and I can only attend on Thursday, so can we schedule all the diversity related discussions for Thursday?
@mikeal ping about the above ^
Let's try and get some ideas of what we want to try and cover @ the summit and then we can begin to organise them into a proper agenda along with some proper planning along the lines of what @groundwater is suggesting in #6.
We only have 2 days and lots of potential for bikeshedding, rabbit holing and general rambling so we'd better keep it tight. We also have plenty of opportunity for social items so we should absolutely include ideas about that as well (SF locals?).
Here's some suggestions to get started: