Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

Collaborator Summit Berlin 2019 - May 30th and 31th 🇩🇪

This is a live document that will be constantly updated to match the proposed agenda.

A collaborator summit is a mix of presentations and interactive sessions lead by the Teams, Working Groups, and Projects that participate in the summit. For interactive sessions, our time is best served if a the team/working groups/project participate in good numbers (quorum etc).

We can change everything, so if you think a better structure will suit us better, let us know in #135, or just send a PR!

It would be fantastic if each one of the breakouts is facilitated by a person who will be responsible to "run" the breakout and do a quick presentation at the end. This person would also set outcomes from the breakout to optimally leverage our time together. There is a facilitator guide available here.

We're excited for Node.js' 5th round of collaboration IRL! Even better, we're excited that folks from the JSF will be joining us for the first time!

Courtyard by Marriot, Berlin City Center

Axel-Springer-Str. 55 10117 Berlin, Germany


09:00 - 18:00

Room Setup - both days

  • Munchen 1/2, 4 - breakout rooms
    • setup - pre-set rounds for 35 people
    • AV - projector, screen and a flip chart (working on getting more AV set up)
  • Munchen 3 - breakout room
    • theater style, 25 people
  • Berlin - main room
    • 100 people, blocks of 6 table blocks
    • projector, screen, sound system and 4 speakers, mixing table, 1 microphone

40 responses to the survey.

Collaborator Summit Day One: 30th May, 2019


Time Main Munich 1/2 Munich 3 Munich 4 Issue Slides
0900 Intro to the Conference (Day 1) - organizers
0930 Modules - Myles, Guy
1000 previous session continues MDN Web Docs and frameworks content — what makes sense in 2019? - Chris Mills
1030 ☕️ coffee break
1100 AMA on (former) JSF projects - Jory - Google Slides
1130 AMA on Node.js Core Subsystems - Manil - 154 Inspector protocol in production - @ak239
1200 OpenJS Foundation CPC Session - Jory, Myles, &/or Tracy Hinds, or new CPC Director or Chairperson - openjs/cpc/123 slides Deprecations future - Ruben Bridgewater, Anna Henningsen - 153
1230 previous session continues previous session continues
1300 🍍 Lunch
1330 🍍 Lunch
1400 Security, modules and Node.js - Guy Bedford - 155 Insights from nodejs/help repo - Gireesh Punathil i18n: Moving forward with the i18n WG, Node.js Intl, and ECMA 402 - 164 - @obensource, @amiller-gh, @littledan
1430 previous session continues previous session continues previous session continues
1500 Fetch in Node.js - 165 - @MylesBorins @mcollina Build open source capacity with Getting Started in Open Source workshops - Manil @keywordnew
1530 ☕️ coffee break
1600 previous session continues Node.js Release Working Group - Beth Griggs (@BethGriggs)
1630 previous session continues previous session continues
1700 Rethinking Transpilation in JavaScript Package Distribution - Amal Hussein / Val Young Node.js Collection & Social Media - 161 - @waleedashraf, @RRomoff
1730 previous session continues previous session continues
1800 🧀 Dinner with Sauce Labs

To speak/present a topic/do a sesssion, make a pull request to update this document with a title, abstract, and a link to an issue with more detail in this repo, similar to

Collaborator Summit Day Two: 31st May, 2019


Time Main Munich 1 Munich 3 Munich 4 Issue Slides
0900 Intro to the Conference (Day 2) - organizers
0930 Open Standards Working Group @ OpenJSF - Jory Website Redesign: Past, Present, and Future - @amiller-gh
1000 previous session continues previous session continues
1030 ☕️ coffee break
1100 TC39 Proposals <3 Feedback from Node & OpenJSF - littledan
1130 previous session continues
1200 🍍 Lunch
1230 🍍 Lunch
1300 Promises in Node core - @MylesBorins, @BridgeAR Rethinking CommComm - Tierney
1330 previous session continues
1400 Proposal to drive Node.js diagnostics initiatives through user journeys - Peter Marton (@hekike), @mhdawson NodeJS Tooling Group Meeting - Christopher Hiller
1430 previous session continues previous session continues
1500 Building Node.js with GN - Yang Workers - 141 - @benjamingr & @addaleax
1530 ☕️ coffee break
1600 Module Ecosystem and Package Maintenance - @mhdawson Bootstrap of Node.js Core: Recent Refactor and the Missing Pieces - Joyee Cheung 147
1630 previous session continues previous session continues
1700 "Bob" Streams in Node.js - @jasnell & @Fishrock123
1730 previous session continues

To speak/present a topic/do a sesssion, make a pull request to update this document with a topic, contact @github-handle. Include a link to an issue in this repo with more detail, similar to that contains at least an abstract, a link to the planning issue in the working group repo, and any extra requests (minimum space during conf, av/sound, etc.).



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. Unlike the Fall instance of the Collab Summit, this Spring instance does not include a morning of Code + Learn, the session that guides people through contributing to the project.

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.

Attendees must register at Eventbrite with the password "collabsummit"

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.

Contributor Covenant Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Focusing on what is best for the community
  • Showing empathy towards other community members.

Examples of unacceptable behavior by participants include:

  • The use of sexualized language or imagery and unwelcome sexual attention or advances
  • Trolling, insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others' private information, such as a physical or electronic address, without explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to block temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.


This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.


Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

To learn more about the process of how moderators enforce the Code of Conduct, review the Moderation Policy and Requesting Moderation.


This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available HERE

Appendix A: The Alias

Note: At the current time, all email sent to the email alias is copied to all members of the Node.js Moderation Team.

Super stoked to see everyone in May!