-
Notifications
You must be signed in to change notification settings - Fork 59
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
Collaborator Summit Berlin 2018 - May 31st, June 1st 2018 #60
Comments
I'll be attending :) maybe @nodejs/modules ? would be great if some work could get done at Berlin |
Great to see this coming together. Thank you for driving this forward. While it looks like I won't actually be able to make this one due to my 18 year old being scheduled to graduate from high school on May 31st, it would be excellent to have both @nodejs/diagnostics and @nodejs/security-wg sessions scheduled for this. |
Sounds like a good time to talk about the future of streams, re: nodejs/node#18640 |
If I may ask, let's please plan on having better remote participation options this time around. I may not be able to be there in person, but I'd definitely join in remotely. |
I'll definitely be attending. (On that note, does JSConf.EU have any special ticket allocations or anything for Node.js collaborators? Trying to figure out their ticket selling system is quite the pain...) |
As far as I know from last time we checked, no. You can contact organizers and ask though in https://2018.jsconf.eu/scholarships/. |
@benjamingr Thanks. I don't even want a discount or anything. I just don't want to have to think about their deadlines and release schedules... 😆Oh well, will have to manage I guess. |
I'll attend. I could present some of the recent |
I’ll be attending. Would love to continue the momentum on the diagnostics
front.
|
That would be amazing, I would love to discuss problems I believe users will have in Node in the future (async iterator performance, common promise patterns and other optimization targets) as well as understand better how things work from the v8 front. Let me know if there is anything I can do to help prepare. |
I can attend remotely but not in person. |
there's about a 2% chance I can attend in person otherwise I can remote in |
I’ll be there, probably on Thursday and definitely on Friday. |
I'll try to attend in person. If I can't make it I'll join remotely. |
@benjamingr I'd like to understand the reason for the current microtask integration with Node better, I do think we loose some performance there. So that's definitely something we could look into together in Berlin. Besides that, concrete examples for performance problems you're talking about would be super helpful 👍 |
@mcollina That being said, my talk proposal is:
|
I think having a breakout about promises in the afternoon would be fantastic as well. It would be fantastic if each one of those is facilitated by someone who will be responsible to "run" the breakout and do a quick presentation at the end. This person would also set some outcomes from the breakout so we leverage our time. |
I would love to join remotely if this could happen. |
I think it'd be nice if we had at least one presentation from the community side of things too. Would anyone be interested in something about the current initiatives of the CommComm or something like that? |
I should be able to make it (TBC). Let's have a security session! |
@mcollina Sure, I can run the breakout session. |
@oe I will be attending. Would love to see a high-level report on the @nodejs/community-committee and reports on @nodejs/i18n, @nodejs/website-redesign, and @nodejs/user-feedback if there's enough representation ❤️ |
I will be attending, definitely want to talk modules. Can also discuss board related matters and governance. Would love to see sessions on build + release |
I would like to talk about everyone's favorite topic: Governance. 💖✨ |
We have a lot of topics like Diagnostics, Promises and Governance that are really heavy and require a lot of context around both the Node.js project and our community. I'd love to see us come up with some ideas (tracks?) for new collaborators too. Unfortunately, I don't have any proposals that I could come up with, but I thought I'd share this so others can draw inspiration. |
I would love to attend 😍 |
@dshaw would an introduction to JavaScript with V8 be a good topic for that? Explaining some of the unwritten rules of Node core? |
I'd love to join @zeke and help facilitate a discussion around i18n & l10n if it garners enough interest! 🎉 |
@joyeecheung, added the issue for the |
Hi all, just sorting out tomorrow morning transportation and I noticed that the under the location information on both days it states that times are from "10am-6pm" but the Agenda starts at 9am. What time should we show up in the morning? :-) |
@add1sun Based on the tabular agenda I believe it's 9am (the summary probably wasn't updated along with the agenda). |
Hey, probably a silly question - will there be coffee/snacks in the morning at 9 or is 9 the start of “important work” and I should come after coffee/breakfast? |
@benjamingr I'm reasonably certain you're not the only one wondering, so definitely not a silly question. |
We don't have a person responsible for making sure the remote attendance stuff happens, do we? I fear the remote attendance thing may not go well if we don't have a plan at this point... |
How do I join the remote attendance??? |
Me and @mafintosh wager we’ll probably want to talk more about streams on day 2 too, we’ll see after today’s discussion |
@codeekage Current plenary session is streaming at https://www.youtube.com/watch?v=iATMSpH4yBE |
@codeekage Joining breakout sessions: Information will be posted to the individual issues, so go to the issue you are interested in. I believe it will all be done over Amazon Chime today. Tomorrow will likely be different. Whee! |
We couldn't make... someone should please get all swags and stickers for the remote team! 😆 |
Note: Diversity and Inclusivity has moved to 1:30, swapped with the website redesign, which is now at 3:30. |
Can we have different youtube channels to join, for the different sessions, if they will be happening at the same time? |
There will be different URLs for the different sessions. |
Dinner tonight: https://github.com/nodejs/summit/blob/master/2018-05-Berlin/attendee-rsvp.md#node-collaborators-dinner---2018-05-31-7pm 7pm BRAUHAUS LEMKE |
Wrapup of the day: https://www.youtube.com/watch?v=dCP_qmhhybg |
Day 2 livestream: http://www.youtube.com/watch?v=vZFE3WeMyAw |
Day 2 afternoon livestream: https://www.youtube.com/watch?v=Vv2djkibpZA |
Audio seems to be on the wrong mic right now on the live stream just posted. |
Day 2 closing livestream: http://www.youtube.com/watch?v=cko9FevFyVg |
@mgalexander Thanks for the feedback. We had to hack things together today. Sorry if the quality was suboptimal. |
Hi, thank you for streaming this, that's very awesome. For next time I think it would be worth to use a better hardware and/or setup, because some parts were very hard to understand, audio as well as video. |
I'm closing this and all the linked issues in this repository as the event has passed. |
Big shout out and thanks to all the organizers and people involved in organizing this event! @mcollina @MylesBorins @dshaw @oe @hackygolucky - I think we had a very productive event. |
Collaborator Summit Berlin 2018
We are back with the date for the Node.js Collaborator Summit in Berlin next to JSConf.Eu (which is on June 2-3, 2018).
This is a live issue that will be constantly updated to match the proposed agenda.
Collaborator Summit Day One: May 31st, 2018
Facilities
Main space: 80 in theatre seating, projector, kitchen restroom can be rearranged(can be split into two smaller rooms as well as just moving chairs around)
Other spaces:
3 meeting rooms, each 12-14 people
1 larger 20 people. theatre seating for 30-40 and also had a large screen
tons of white board space throughout
Agenda
if you want to speak and present a topic, feel free to reply to this issue with a brief abstract.
Collaborator Summit Day Two: June 1st, 2018
Agenda
if you want to speak and present a topic, feel free to reply to this issue with a brief abstract.
Organizers
Attendance
Anyone can come, but we will not be explicitly onboarding at Collab
Summit Berlin. Conversations can move fast as working groups have
a lot of context. This Spring instance of Collab Summit will not include
a morning Code + Learn to learn how to contribute prior to congregating
for the summit. Please look to the Fall Collab Summit in Vancouver, BC
for this pairing.
Working groups will put together a brief schedule so that people can
familiarize themselves before folks get onsite, having the general collaborator
discussions, and then dive into breakout sessions.
Working groups in attendance
We'd love to know ahead who will be represented. Filing issues in this repo is helpful for discussion particular to a working group and how they'd like to manage their time. Linking to that here would be great! We're working on creating a Projects Board to post times for this on the conf agenda so people are aware of when a WG meets and can maybe get a break, if needed. We'll be looking at issues filed in this repo titled "Berlin: working group something something" to add these below as well.
Travel Fund
There are funds available for any Individual Member of the Node.js Foundation to receive travel funds to Collab Summit. Membership is free for active collaborators. Sign up HERE.
PLEASE follow the instructions for application to receive travel funds HERE.
@nodejs/collaborators @nodejs/v8 @nodejs/tsc @nodejs/community-committee We should figure out what topics we want to cover.
We think we will be best served with some monotrack presentations and discussions in the morning, and breakout rooms in the afternoon. We can change everything, so if you think a better structure will suit us better, let us know!
It would be fantastic if each one of the breakouts is facilitated by someone who will be responsible to "run" the breakout and do a quick presentation at the end. This person would also set some outcomes from the breakout so we leverage our time together in the best possible ways.
The text was updated successfully, but these errors were encountered: