-
Notifications
You must be signed in to change notification settings - Fork 231
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
Streams Summit #203
Comments
We also have a repo for organizing Collaborator Summits, https://github.com/nodejs/summit, and have some budget to help put them together alongside the Node.js Interactive events. |
@mikeal ... the VM summit folks were also talking about having a part 2. Perhaps it would make sense to simply make this a normal part of the Collaborator summit? Dedicate some time for each of the subsystem teams or working groups to meet up? |
@jasnell great idea! :) |
I agree with @jasnell. However I'm not sure that a couple of hours will be enough for digging deeper in the streams internal. How about we try to sketch:
and then we can plan it better (it will possibly be an iterative process). I would like every member of @nodejs/collaborators that has an interest in streams but he fears touching them to join this discussion and possibly the summit. |
@thealphanerd yes :) |
Is this summit in-person or online? |
The intention is to run this in-person. |
there is no reason the summit could not be streamed though. A number of people were streaming the VM summit and having their questions proxied |
I don't know how successful the VM Summit streaming was, I was there for a bit and actually had no idea anyone was participating that way. The whole point of these things is to work through stuff in person, we spend literally the rest of the year working through stuff online so it seems silly to go through so much effort to stream the very few things we do in-person. |
I watched the VM summit stream. It kind of worked, but definitely was hard to engage remotely. |
I think its good to try and broadcast but at the same time we need to set the expectation that it will be hard to follow/interact. For full interaction you'll really need to be there in person. |
After what we discussed on #252, we would really like to plan one. I might throw some possibilities around conferences for which their dates for 2017 are public:
|
+1 for jsconfeu |
Can do any of those dates. Node foundation should be able to cover expenses
for folks that need to fly over right?
…On Fri, Jan 13, 2017 at 9:23 AM Myles Borins ***@***.***> wrote:
+1 for jsconfeu
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#203 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWlesgjxKn6exQPA7W_qMkTTu3sYzNlks5rRzSJgaJpZM4ILy85>
.
|
Some of us will meet at the collaborator summit on the 4-5 of May in Berlin. |
How about we do a Streams Summit to improve/document streams? It would also help onboarding new collaborators into the wg.
So it came out the idea in nodejs/node#6178.
Is this something it might interest us to do?
The text was updated successfully, but these errors were encountered: