-
Notifications
You must be signed in to change notification settings - Fork 58
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
* Seed the agenda with the contents of #100 This PR simply contains the current contents of the original comment in #100. Reason: #100 (comment) * Use new updates and address PR suggestions
- Loading branch information
1 parent
b4aa692
commit 9c5acf3
Showing
1 changed file
with
130 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,130 @@ | ||
# Collaborator Summit Vancouver 2018 - October 12th and 13th 2018 | ||
|
||
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 | ||
|
||
|
||
## Collaborator Summit Day One: October 12th, 2018 | ||
|
||
1:00 PM - 5:00 PM | ||
|
||
### Agenda | ||
|
||
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 and Breakout 2) | ||
|
||
_We are expecting 300 people to participate_. | ||
|
||
<br> | ||
|
||
|
||
| Time | Place | Topic | Speakers/Champions | Issue | | ||
|---------------|--------------|-----------------------------------------------|----------------------------------------|--------------------------------------------| | ||
| 1:00 | Main | Intro, Sponsor Talk, Code of Conduct | @mcollina @dshaw @chowdhurian | | | ||
| 1:15 | Main | V8 Release Schedule and Bisection | @hashseed | https://github.com/nodejs/summit/issues/100#issuecomment-409152001 | | ||
| 1:45 | Main | The Embedder's POV | @codebytere | https://github.com/nodejs/summit/issues/100#issuecomment-409629177 | | ||
| 2:15 | Main | Automation of Node.js core workflows | @joyeecheung | https://github.com/nodejs/summit/issues/100#issuecomment-416011657 | | ||
| 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 | https://github.com/nodejs/Release/issues/358 | | ||
| 3:30 | Main | Free | | | | ||
| 3:30 | Main | Free | | | | ||
| 3:30 | Breakout 1 | Diagnostics | @kjin , @yunong | https://github.com/nodejs/diagnostics/issues/229 | | ||
| 3:30 | Breakout 2 | Promises | @BridgeAR | | | ||
|
||
|
||
_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 https://github.com/nodejs/summit/issues/86_. | ||
|
||
|
||
## Collaborator Summit Day Two: October 13th, 2018 | ||
|
||
9:00 AM - 5:00 PM | ||
|
||
### Agenda | ||
|
||
We have 3 rooms available: | ||
|
||
- 1 main room with 100 people capacity. | ||
- 2 rooms for 50 people each. (Breakout 1 and Breakout 2) | ||
|
||
_We are expecting 70-100 people to partecipate__. | ||
|
||
<br> | ||
|
||
|
||
| Time | Place | Topic | Speakers/Champions | Issue | | ||
|---------------|--------------|---------------------------------------------------------------------|-------------------------------|--------------------------------------------| | ||
| 8:00 | | Breakfast and registration | | | | ||
| 9:00 | Main | Intro, Code of Conduct | @mcollina @dshaw @chowdhurian | | | ||
| 9:15 | Main | Modules | @MylesBorins | https://github.com/nodejs/modules/issues/177 | | ||
| 9:15 | Breakout 1 | Website Redesign | @amiller-gh | https://github.com/nodejs/website-redesign/issues/88 | | ||
| 9:15 | Breakout 2 | Security WG | @mhdawson | https://github.com/nodejs/security-wg/issues/358 | | ||
| 10:45 | | __Coffee Break__ | | | | ||
| 11:00 | Main | Streams (tentative) | @mcollina | | ||
| 11:00 | Breakout 1 | i18n (tentative) | ? | ? | | ||
| 11:00 | Breakout 2 | N-API | @mhdawson | https://github.com/nodejs/abi-stable-node/issues/339 | | | ||
| 12:30 | | __Lunch__ | | | | ||
| 1:30 | Main | Governance | @amiller-gh | https://github.com/nodejs/admin/issues/228 | | ||
| 1:30 | Breakout 1 | Free / Hacking Room / Fixathon | | | | ||
| 1:30 | Breakout 2 | Free / Hacking Room / Fixathon | | | | ||
| 3:00 | | __Break__ | | | | ||
| 3:15 | Main | __Lighting talks__ | | | | ||
| | | Deep dive on Timers | @apapirovski | | | ||
| | | Diagnostics at Netflix | @hekike | | | ||
| | | Academic perspectives on Node.js | @davisjam | | ||
| 4:00 | Main | __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 https://github.com/nodejs/summit/issues/86._ | ||
|
||
## Organizers | ||
|
||
- Dan Shaw @dshaw | ||
- Manil Chowdhurian @chowdhurian | ||
- Matteo Collina @mcollina | ||
- Tracy Lee @ladyleet | ||
|
||
## Attendance | ||
|
||
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 | ||
|
||
## 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](https://github.com/nodejs/members#members). | ||
|
||
PLEASE follow the instructions for application to receive travel funds [HERE](https://github.com/nodejs/admin/blob/master/MEMBER_TRAVEL_FUND.md#process). | ||
|
||
|
||
------------------------ | ||
|
||
|
||
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. |