Collaborator Summit Berlin 2018 - May 31st, June 1st 2018

[mcollina]

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

AWS Berlin address Krausenstraße 38, 10117 Berlin, Germany 9am-6pm

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

Time	Place	Topic	Speakers/Champions	Issue
9:00 - 9:30	main space	Introduction and agenda bashing
9:30 - 10:00	main space	Talk: Holding on to your Performance Promises	@bmeurer, @MayaLekova	https://github.com/nodejs/summit/issues/86
10:00 - 10:30	main space	Talk: Web Assembly	@linclark, @lukewagner, @tschneidereit	https://github.com/nodejs/summit/issues/62
10:30 - 11:00		break
11:00 - 12:30	meeting room	Diagnostics	@mhdawson	https://github.com/nodejs/summit/issues/71
11:00 - 12:30	meeting room	Web Assembly	@linclark, @lukewagner, @tschneidereit	https://github.com/nodejs/summit/issues/62
11:00 - 12:30	meeting room	Docs: Integrating with All The Groups	@bnb	https://github.com/nodejs/summit/issues/79
11:00 - 12:30	meeting room	still open
12:30 - 13:30		lunch provided by AWS
13:30 - 15:00	meeting room	Promises	@MayaLekova, @bmeurer, @benjamingr	https://github.com/nodejs/summit/issues/86
13:30 - 15:00	meeting room	Diversity/Inclusivity	@Tiriel	https://github.com/nodejs/summit/issues/75
13:30 - 15:00	meeting room	Modules	@MylesBorins	https://github.com/nodejs/modules/issues/120
13:30 - 15:00	meeting room	still open
15:00 - 15:30		break
15:30 - 17:00	meeting room	Future of Streams	@mafintosh	https://github.com/nodejs/summit/issues/82
15:30 - 17:00	meeting room	Website Redesign: Content Creation	@amiller-gh @chowdhurian	https://github.com/nodejs/summit/issues/89
15:30 - 17:00	meeting room	i18n & l10n	@zeke	https://github.com/nodejs/summit/issues/61
15:30 - 17:00	meeting room	CommCom: Individual Membership program subgroup formation	@hackygolucky
17:00 - 18:00	main space	Presentations by breakout rooms

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

Mozilla Berlin address Schlesische Str. 27, 10997 Berlin, Germany 9am-6pm

Agenda

Time	Place	Topic	Speakers/Champions	Issue
9:00 - 9:30		Introduction and agenda bashing
9:30 - 10:30		The scope and status of a core collaborator & Growing Collaborators	@MylesBorins @joyeecheung @mcollina	https://github.com/nodejs/summit/issues/67
10:30 - 11:30		Project velocity	@benjamingr @Trott	https://github.com/nodejs/summit/issues/64
11:30 - 12:30		lunch provided by Mozilla
12:30 - 13:00		How to better collaborate on TC39	@littledan
13:00 - 13:30		Scoping modules	@joyeecheung	https://github.com/nodejs/summit/issues/84
13:30 - 15:00		Break out Sessions
15:00 - 15:30		break
15:30 - 17:00		Governance	@dshaw
17:00 - 17:30		Closing remarks

if you want to speak and present a topic, feel free to reply to this issue with a brief abstract.

Organizers

• Dan Shaw @dshaw
• Matteo Collina @mcollina
• Myles Borins @MylesBorins
• Olivia Hugger @oe
• Tracy Hinds @hackygolucky

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.

• Working group that will be at Collaboration Summit
  • Name of contact @github-handle
  • link to working group planning issue
  • Any extra requests(space during conf, av/sound, etc.)

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.

[benjamingr]

I'll be attending :) maybe @nodejs/modules ? would be great if some work could get done at Berlin

[jasnell]

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.

[mafintosh]

Sounds like a good time to talk about the future of streams, re: https://github.com/nodejs/node/issues/18640

[jasnell]

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.

[apapirovski]

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...)

[benjamingr]

@apapirovski

On that note, does JSConf.EU have any special ticket allocations or anything for Node.js collaborators?

As far as I know from last time we checked, no. You can contact organizers and ask though in https://2018.jsconf.eu/scholarships/.

[apapirovski]

@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.

[bmeurer]

I'll attend. I could present some of the recent Promise and async work in V8 if that's generally interesting in this context.

[yunong]

I’ll be attending. Would love to continue the momentum on the diagnostics front.

[benjamingr]

I'll attend. I could present some of the recent Promise and async work in V8 if that's generally interesting in this context.

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.

[bmeck]

I can attend remotely but not in person.

[devsnek]

there's about a 2% chance I can attend in person otherwise I can remote in

[addaleax]

I’ll be there, probably on Thursday and definitely on Friday.

[mmarchini]

I'll try to attend in person. If I can't make it I'll join remotely.

[bmeurer]

@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 👍

[bmeurer]

@mcollina That being said, my talk proposal is:

Holding on to your Performance Promises

The ES2015 revision of JavaScript introduced Promises as primitives for asynchronous operations and generators as primitives for concurrent programming. On top of that ES2017/18 added async functions and generators. This talk briefly explores these primitives, and look into the performance peculiarities of Promises-based programming paradigms. We’ll especially look into how these operations perform in V8, the JavaScript engine that powers Node.js.

[mcollina]

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.

[lirantal]

I would love to join remotely if this could happen. @nodejs/security-wg guys what do you say? would any of you be able to make it there?

[ghost]

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?

[vdeturckheim]

I should be able to make it (TBC). Let's have a security session!

[bmeurer]

@mcollina Sure, I can run the breakout session.

[bnb]

@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 ❤️

[MylesBorins]

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

[dshaw]

I would like to talk about everyone's favorite topic: Governance. 💖✨

[dshaw]

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.

[zeke]

I'll be there! Maybe just for day 2 tho.

I'd be interested in discussing internationalization and localization if there's enough interest in the topic. Opened an issue per @mcollina's recommendation above: https://github.com/nodejs/summit/issues/61

[maddhruv]

I would love to attend 😍

[bmeurer]

@dshaw would an introduction to JavaScript with V8 be a good topic for that? Explaining some of the unwritten rules of Node core?

[obensource]

I'd love to join @zeke and help facilitate a discussion around i18n & l10n if it garners enough interest! 🎉

[RichardLitt]

I'd like to be there again this year. Will schedule this in and see if I can make it.

[mhdawson]

I hope to be there as well.

[rachelnicole]

I might be able to attend, I'm not sure yet though

[hackygolucky]

Added the current links and info for requesting travel funds and joining as a member to receive them in the issue description!

[Tiriel]

I'll try to be there, but I'm not sure yet. Still need to work it out with my employer. I'd love to though

[vdeturckheim]

@Tiriel if we both go, let's sync up ;-)

[linclark]

I'll be there, and happy to talk about WebAssembly :) I've added an issue: https://github.com/nodejs/summit/issues/62

[inidaname]

I will be happy to attend, I want to use the opportunity to give a talk on the benefit of participation of African collaborators to NodeJs Development and how the NodeJs Foundation can effectively support that.

[tniessen]

I will try to attend.

[danbev]

I'm planning on attending as well.

[codeekage]

I'd love to attend and would definitely love to talk about community and diversity.

[mrkmarron]

I am interested in attending as well and am in the process of figuring out travel plans.

[hashseed]

I'll be there as well, but will arrive only in the afternoon on the first day.

[add1sun]

I'm pretty sure I'll be there. I'd be interested in getting together to work on reviving the education team. Since I'm new to the community and haven't been involved to date, I don't feel like I can lead something on that. If anyone else is interested in pulling something together, I'm more than willing to be a partner to get something going on this at the Collab Summit. (I'll post this note in the Education repo as well.)

[AvraamMavridis]

I would love to attend

[watson]

@Qard and I will be attending as well 🎉

[joyeecheung]

I plan to attend but cannot confirm just yet.

[Danese]

Me too!

D

On Thu 15 Mar 2018 at 22:08, Addison Berry notifications@github.com wrote:

I'm pretty sure I'll be there. I'd be interested in getting together to work on reviving the education team https://github.com/nodejs/education. Since I'm new to the community and haven't been involved to date, I don't feel like I can lead something on that. If anyone else is interested in pulling something together, I'm more than willing to be a partner to get something going on this at the Collab Summit. (I'll post this note in the Education repo as well.)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nodejs/summit/issues/60#issuecomment-373538541, or mute the thread https://github.com/notifications/unsubscribe-auth/ABuHlCjVDUXh4FqYdThso1zs16AZrwbsks5teuZdgaJpZM4SVGHH .

[ofrobots]

I'm planning to attend as well.

[maddhruv]

Is there any update with the itenary, address and other details? @mcollina

[zeke]

AWS Berlin address TBD

I'm starting to look for lodging. Would be handy to know roughly where the summit will be held.