We are back with the date for the Node.js Collaborator Summit in Vancouver next to Node+JS Interactive (which is on October 10th and 11th, 2018). This is a live issue that will be constantly updated to match the proposed agenda.
Vancouver Convention Centre West Building 1055 Canada Place Vancouver, British Columbia V6C 0C3 Canada
1:00 PM - 5:00 PM
We have a big room and 2 breakout rooms available:
- 1 big room for 300 people. (Main)
- 2 rooms for 60 people each. (Breakout 1 (Room 118) and Breakout 2 (Room 121))
We are expecting 300 people to participate.
| Time | Place | Topic | Speakers/Champions | Issue | Slides |
|---|---|---|---|---|---|
| 1:00 | Main | Intro, Sponsor Talk, Code of Conduct | @mcollina @dshaw @chowdhurian | ||
| 1:10 | Main | V8 Release Schedule and Bisection | @hashseed | #100 (comment) | Slides |
| 1:25 | Main | The Embedder's POV | @codebytere | #100 (comment) | The Embedder's POV |
| 1:40 | Main | Automation of Node.js core workflows | @joyeecheung | #108 | automation-of-nodejs-workflows |
| 2:00 | Main | Merger presentation & open forum | @MylesBorins | ||
| 2:45 | Break | ||||
| 3:15 | Main | Session presentation, set up the Main room | @mcollina @dshaw @chowdhurian | ||
| 3:30 | Main | Moderation | @hackygolucky | ||
| 3:30 | Main | Mentorship | @Bamieh | ||
| 3:30 | Main | LTS + release | @MylesBorins | nodejs/Release#358 | |
| 3:30 | Main | Tooling | @boneskull | nodejs/tooling#4 | |
| 3:30 | Main | Embedding | @codebytere | #125 | |
| 3:30 | Breakout 1 (Room 118) | Diagnostics | @kjin , @yunong | nodejs/diagnostics#229 | Diagnostics |
| 3:30 | Breakout 2 (Room 121) | Free | |||
| 5:00 | Breakout 3 (Meet in Main BallRoom A at back) | Node Optimizations | @ssuresh , @uttampawar |
If you want to speak and present a topic in the main room, feel free to make a pull request to update this document with a title and abstract. If you want to propose a full session in a breakout room, add a link to an issue in this repo, similar to #86.
9:00 AM - 5:00 PM
We have 3 rooms available:
- 1 main room with 100 people capacity (Room 121).
- 2 rooms for 50 people each. (Breakout 1 (Room 118) and Breakout 2 (Room 119))
We are expecting 70-100 people to participate.
| Time | Place | Topic | Speakers/Champions | Issue | Slides |
|---|---|---|---|---|---|
| 8:00 | Breakfast and registration | ||||
| 9:00 | Main (Room 121) | Intro, Code of Conduct | @mcollina @dshaw @chowdhurian | ||
| 9:15 - 10:45 | Main (Room 121) | Modules | @MylesBorins | nodejs/modules#177 | |
| 9:15 - 10:45 | Breakout 1 (Room 118) | Website Redesign | @amiller-gh | nodejs/website-redesign#88 | Slides |
| 9:15 - 10:45 | Breakout 2 (Room 119) | Security WG | @mhdawson | nodejs/security-wg#358 | |
| 10:45 | Coffee Break | ||||
| 11:00 - 12:30 | Main (Room 121) | Promises | @BridgeAR | Code examples | |
| 11:00 - 12:30 | Breakout 1 (Room 118) | Governance | @amiller-gh | nodejs/admin#228 | |
| 11:00 - 12:30 | Breakout 2 (Room 119) | Free | |||
| 12:30 - 1:30 | Lunch | ||||
| 1:30 - 2:45 | Main (Room 121) | Open standards & Web compatibility | @joyeecheung | #106 | |
| 1:30 - 2:45 | Breakout 2 (Room 119) | N-API | @mhdawson | nodejs/abi-stable-node#339 | |
| 1:30 - 2:45 | Breakout 1 (Room 118) | Governance | |||
| 2:45 - 3:45 | Main (Room 121) | Streams | @mcollina @Fishrock123 @mafintosh | #110 | node-whatwg-streams-proposal |
| 2:45 - 3:45 | Breakout 1 (Room 118) | Governance | |||
| 2:45 - 3:45 | Breakout 2 (Room 119) | Benchmarking | @davisjam | #120 | Benchmarking and Performance WG |
| 3:45 | Break | ||||
| 4:00 | Main (Room 121) | Lightning talks | |||
| Deep dive on Timers | @apapirovski | ||||
| Diagnostics at Netflix | @hekike | Diagnostics at Netflix | |||
| Academic perspectives on Node.js | @davisjam | Academic perspectives on Node.js | |||
| Navigating Node.js C++ code | @addaleax | node-cpp-vancouver | |||
| 4:30 | Main (Room 121) | Session presentations, group photo, and thanks! |
If you want to propose a full session in a breakout room, add a link to an issue in this repo, similar to #86.
- Dan Shaw @dshaw
- Manil Chowdhurian @chowdhurian
- Matteo Collina @mcollina
- Tracy Lee @ladyleet
Anyone can come, but we will not be explicitly onboarding at Collab Summit Vancouver. Conversations can move fast as working groups have a lot of context. Unlike the Spring instance of the Collab Summit, this Fall instance includes a morning of Code + Learn. The Code + Learn session guides people through contributing to the project, prior to congregating for the Summit.
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.
Atteneeds must register at: https://www.regonline.com/?eventID=2152653&rTypeID=511098 Access code: COLLABSUMMITONLY
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.)
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.
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 first day, and then breakout rooms in the second day. 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.