Collaborator Summit Vancouver 2018 - Call for Sessions and Agenda - October 12th and 13th 2018. #100
Comments
mcollina
changed the title
|
Issue #100! |
|
Would love to talk about diagnostics, tiers of support for tooling, HTTP/2 performance, and promises debugging. cc @misterdjules @hekike |
|
The security-wg will want a session, proposal will be built here: nodejs/security-wg#358 |
|
Would love to see a few sessions:
|
|
We should definitely have
And a few other suspect. |
|
For this collab summit I'd really love to see interactive sessions that are different from the previous discussions/talks format - the talks and discussions are great but sometimes we are more effective on GitHub and are just going to throw topics back to GitHub. A few ideas we have discussed in May:
|
|
From a logistical perspective, it would be amazing to have proposals in by the end of August, a month from now. That timeframe would be very helpful for scheduling. Here's a possible template. Title (as in, issue title)Summit Topic: topic – what will be covered Motivation/AbstractContext AgendaIt can be very helpful to have an agenda included in the proposal. The agenda can be just an empty placeholder to start; as the discussion progresses, items can be added, and finalized closer to the date of the Summit! Can't wait to see y'all in Vancouver! 🎉🎉🎉 Feel free to use the following past proposals as inspiration! Remix away. #71: Agenda for Diagnostics session at collaborator summit |
|
Okay here goes: Title: Release schedules and bisection Another one, if there is interest: |
|
Did the dates change? I recall that the summit was ending on the 12th and so I booked my flight out on the 13th :(. Can we schedule the sessions for promises debugging and diagnostics on the 12th? |
|
@yunong The summit is going to be on 12th (afternoon-only) and 13th, I think the JSI website lists the dates as 10th-12th because technically the programs for non-Node.js-collaborators ends on 12th (code-and-learn in the morning). They don't include the summits, because technically the summits are separate from JSI. |
|
I’ll do my best to schedule those two sessions on day 1. |
|
Thanks @mcollina ! |
Some of these could likely be lightning talks. I know I could cover e.g., timers in like 5-10min. |
|
If there's interest, i'd love to do: Title: The Embedder's POV |
|
In the N-API team meeting this week, we discussed and would like to have an N-API breakout. |
|
A lightening talk on trace events and diagnostics instrumentation would be worthwhile |
|
Would love to talk about Moderation Team and preparing potential new folks for moderating and/or nomination to the Nomination team. ~ 60-90 minutes should be enough. May not even need a room, just a table. nodejs/admin#208 |
|
I would be happy to talk about some of the academic work in the Node.js space if that would be interesting. Some examples:
|
|
👍👍👍👍👍 pls fill out form when you can! |
|
Oh yeah totes sorry planning too many things 🙃 |
|
I'd like to give a short 15 minutes talk about the debugging and performance profiling work we have been working on at Netflix. |
|
@mcollina I was thinking more of a smaller break out but I'll take what I can get 😄 edit 3:30 in main room works |
|
@MylesBorins would you mind opening an issue in the LTS repo, and adding that to the agenda? |
|
Hi Folks. If there is still room on the agenda, I would like a session on supporting WASM native modules. I can help lead it. |
|
@mcollina hmm.. I wouldn't want to miss the Governance session. Any chance of a third breakout room in one of the timeslots? |
|
@mcollina yes! That's great–we'll take the 11am spot on day 2 for i18n. Super stoked! 🙌 |
|
Collaborators - Please register for this party! Telus is sponsoring a party after Node + JS Interactive (@ahmadnassri has been the one helping facilitate a lot of this) and while it's open to the public, the main reason they wanted to sponsor was to throw a party for the Node.js collaborators. That being said, I highly recommend everyone RSVP asap as it it is limited to ~200 folks and will be mentioned in the general conference announcements! Would hate for anyone not to get in! https://www.eventbrite.ca/e/node-js-happy-hour-with-telus-digital-tickets-50099526031 The event will be Thursday October 11th at 6:30pm to celebrate the end of the conference and the start to an awesome Code & Learn + Collaborator's Summit. |
|
Can individual (non-collaborating) members get free access to all events? And also to clarify, sorry I am lost in the details, collaborators can attend JSI for free but need to register. |
|
The event is about a month away from now. I am thinking maybe we can put the agenda into a document in this repo and have people sending PRs (preferably adding links to slides before the event starts) instead of responding here? That way it's easier to track the progress before the event and to look up in the future. BTW we had a placeholder for the agenda in Berlin but never managed to fill it out https://github.com/nodejs/summit/blob/master/2018-05-Berlin/agenda.md |
Node.js foundation individual members can request tickets funded by the foundation by sending PRs to https://github.com/nodejs/admin/blob/master/TravelFunds/2018.md (the process is described in https://github.com/nodejs/admin/blob/master/MEMBER_TRAVEL_FUND.md) but I think the deadline for JSI has already passed? (I vaguely remember that we have set a one-month-ahead deadline somewhere...) The estimated number of tickets that needed funding that I gave to the events team based on the survey in #99 was 12, there may be some spare tickets left though. |
This PR simply contains the current contents of the original comment in #100. Reason: #100 (comment)
Good suggestion @joyeecheung. PTAL at #104. |
|
@joyeecheung I don't think there's a time limit other than the min 72 hours for review and the request having to be made prior to the event. I for one am extremely behind and have not submitted mine yet. (Will do tonight.) If we want to have a time limit then it should be explicit in our documentation. |
* 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
|
Update: Per suggestion and related #104, the agenda is being maintained here now. Please make a PR to it for changes 🙌🏽 |
|
The promises and diagnostics breakouts are happening at the same time on the same day. Since there is overlap in the topics that will be covered and in the people who may want to attend (e.g. those are the two breakouts I'd like to attend, and I think that @yunong, @hekike and @mmarchini may want to attend both of those as well), can we move one of them to another time slot? |
|
@misterdjules what would you change? |
|
I would selfishly suggest moving the diag breakout to the next day, as I'll be flying back from Dublin that morning and probably be very tired. 😅 |
|
@yunong is not planned to attend on Day 2. He asked for diag to be on Day 1. @misterdjules which session would you replace? |
@mcollina Can we move promises to day 2 then?
What do you mean? |
|
You will need to replace another slot with promises. Which one will you
replace?
Il giorno lun 1 ott 2018 alle 20:08 Julien Gilli <notifications@github.com>
ha scritto:
… @yunong <https://github.com/yunong> is not planned to attend on Day 2. He
asked for diag to be on Day 1.
@mcollina <https://github.com/mcollina> Can we move promises to day 2
then?
@misterdjules <https://github.com/misterdjules> which session would you
replace?
What do you mean?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#100 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADL48jbXnjzVBoT4lEPCdbpj4ezJb0Fks5ugloDgaJpZM4VgnZq>
.
|
and others
Update: Per suggestion and related #104, the agenda is being maintained here now. Please make a PR to it for changes 🙌🏽
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 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.
Agenda
The updated agenda is available at here. Send PRs for updates.
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.
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/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 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.
The text was updated successfully, but these errors were encountered: