Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Summit Planning: Draft Agenda #166

Closed
jorydotcom opened this issue May 21, 2019 · 22 comments · Fixed by #178
Closed

Summit Planning: Draft Agenda #166

jorydotcom opened this issue May 21, 2019 · 22 comments · Fixed by #178
Labels
Berlin 2019 Collaborator Summit

Comments

@jorydotcom
Copy link
Collaborator

jorydotcom commented May 21, 2019 •
edited by WaleedAshraf
Loading

Final Agenda: https://github.com/nodejs/summit/blob/master/2019-05-Berlin/agenda.md

Google Sheet: sheet
Sheet Name: All Rooms

Please let us know, via issue comment or cell comment in the spreadsheet, whether:

  • You are hosting a session and request attendance of specific individuals
  • You are hosting a session and want to attend a session that conflicts with yours
  • You want to attend two sessions happening concurrently

Please be mindful not to accidentally edit the spreadsheet. Time permitting, @joyeecheung has offered to do the scheduling survey to minimize the number of conflicts we might have. We're just hoping to get as much info as we can upfront, so we can help those who want to attend remotely plan accordingly.

I'll reiterate that this is not final and that unfortunately we probably won't be able to resolve all conflicts. But we'll try our best!

We plan to collect comments on this document, then move the schedule into the repo when we finalize it next week.

Agenda Questions to: @jorydotcom, @mcollina, @keywordnew, @evahowe
AV Questions to: @evahowe, @LaRuaNa, @christian_bromann
@joyeecheung
Copy link
Collaborator

joyeecheung commented May 22, 2019 •
edited
Loading

I have created the form in https://forms.gle/tES95r4qQfxx7GKs7 and added a few collaborators. Please request the collaborator permission of this if you want it.

A few tweaks:

  1. I merged modules with Security, modules and Node.js (champion overlap and the first one lacks description, it looks like the latter covers the first one already)
  2. I merged Promises in Node core and Promises and the unhandled rejection default (I cannot see who the champion of the first one is from the spreadsheet but the two topics overlap significantly)
  3. I changed Package Maintenance to Module Ecosystem and Package Maintenance (@mhdawson) (the first one looks like the result of the CFP form not working correctly)

@guybedford
Copy link

Please can we not merge the modules discussion with Security, modules and Node.js topic. The security discussion is its own topic, which will require some background and enough time for discussion while the modules discussion will be a more general discussion around wider modules concerns. If more information is needed for the modules session perhaps @MylesBorins can provide it.

@joyeecheung
Copy link
Collaborator

joyeecheung commented May 22, 2019 •
edited
Loading

@guybedford Sure, I added the modules discussion back in the form. I don't think we need to recollect data in this case - these two sessions should scheduled together (it does not really make sense to do them e.g. on separate days in separate places), so we can just take the one with the highest attendance as reference when picking the slot/room and leave an extended slot for them.

@guybedford
Copy link

@joyeecheung many thanks. That sounds preferable, although if they can't be scheduled together that wouldn't be a problem either.

@jasnell
Copy link
Contributor

jasnell commented May 23, 2019

Is there a social/dinner event being planned as part of the agenda?

@evahowe
Copy link
Contributor

evahowe commented May 23, 2019 via email

@keywordnew
Copy link
Member

@evahowe can confirm I've received the above email, and another, subjects:

  • Excited for Collab Summit 2019?? (includes links mentioned)
  • OpenJS Collaborator Summit Attendance Survey

Both are helpful :)

@evahowe
Copy link
Contributor

evahowe commented May 24, 2019 via email

@mhdawson
Copy link
Member

I got the email as well.

@evahowe
Copy link
Contributor

evahowe commented May 24, 2019 via email

@WaleedAshraf
Copy link
Member

@keywordnew @joyeecheung
Do you guys know who and why changed the timing for "Node.js Collection & Social Media" from 16:00 to 13:00?

I requested it to be 16:00, and it is communicated with @RRomoff also because she would be joining remotely.

In the sheet history, I see it was updated anonymously by someone yesterday.

@keywordnew
Copy link
Member

keywordnew commented May 29, 2019 via email

@WaleedAshraf
Copy link
Member

@keywordnew
moved it back. thanks for all the efforts.👍 🍇

@joyeecheung
Copy link
Collaborator

joyeecheung commented May 29, 2019 •
edited
Loading

From a glance of the draft agenda, I don't think we are doing a good job at grouping them into tracks. Looking at the survey results, it would make more sense if we have at least three rough tracks:

  • Node.js core & working groups
  • Documentation, ecosystem & community
  • non-Node.js sessions

and leave one room for each, so that people interested in a certain topic don't have to move around so often and will have less conflicts - I suspect there will be quite a lot of conflicts in particular for the 14:00 session on the first day when we have Security, modules and Node.js, Inspector protocol in production and i18n: Moving forward with the i18n WG, Node.js Intl, and ECMA 402 happening at the same time.

We could also leave one room open for just hacking and conversation.

@mcollina
Copy link
Member

How would you resolve that conflict?

I’m not super concerned about tracks, mainly to create a bit of dynamics in people moving through rooms to create some more conversations in the hallway.

I guess we’ll hack some bits of the agenda tomorrow morning as usual?

@joyeecheung
Copy link
Collaborator

joyeecheung commented May 29, 2019 •
edited
Loading

@mcollina I thought the coffee breaks and the lunches are where we have the hallway tracks? Also the slots are probably longer than necessary for many sessions so we will have plenty of time to move around. For people who don't really know each other in person, it seems odd to just start a conversation with strangers in the hallway while there is an agenda happening. For people who already know each other in person...they may just make use of an empty room to chat.

Can we shift the Munchen 4 sessions to Muchen 1 if possible? It is a bit confusing that sometimes Munchen 4 is empty while sometimes Munchen 1 is empty. If there are just two rooms used for sessions, people can just go in and check out instead of wandering around.

There seems to be some slots with only one session going on on the second day, maybe we could move one of those 14:00 sessions there. It's slightly better if there are only two sessions happening at the same time.

@mcollina
Copy link
Member

Can we shift the Munchen 4 sessions to Muchen 1 if possible? It is a bit confusing that sometimes Munchen 4 is empty while sometimes Munchen 1 is empty. If there are just two rooms used for sessions, people can just go in and check out instead of wandering around.

I think so. Which sessions/slots specifically (from -> to)?

There seems to be some slots with only one session going on on the second day, maybe we could move one of those 14:00 sessions there. It's slightly better if there are only two sessions happening at the same time.

+1!

@joyeecheung
Copy link
Collaborator

joyeecheung commented May 29, 2019 •
edited
Loading

How about the following changes for Muchen 4 sessions:

Website Redesign:
    Muchen 4, 9:30 Day 1 -> Muchen 1, 9:30 Day 2
    (in parallel with Open Standards, instead of MDN + modules)
Bootstrap of Node.js Core:
    Muchen 4, 10:30 Day 1 -> Muchen 1, 10:30 Day 1
    (just change the room)
i18n: Moving forward with the i18n WG, Node.js Intl, and ECMA 402:
    Muchen 4, 14:00 Day 1 -> Muchen 1, 15:30 Day 2
    (in parallel with Module Ecosystem, instead of Release + fetch)
Node.js Collection & Social Media:
    Muchen 4, 15:30 Day 1 -> Muchen 1, 15:30 Day 1
    (just change the room)
Node.js Release Working Group:
    Muchen 1, 15:30 Day 1 -> Muchen 1, 15:00 Day 2
    (in parallel with Building Node.js with GN, instead of Node.js Collection & Social Media + fetch)

Then we will not have sessions in Muchen 4 and will only have them in either the main room or Muchen 1

@mcollina
Copy link
Member

I’m +1 to those changes apart from the last one. I highly suspect that the audience of Building Node with GN is going to overlap with the release working group participants.

@joyeecheung
Copy link
Collaborator

joyeecheung commented May 29, 2019 •
edited
Loading

@mcollina Maybe swap the release WG with i18n then? Then we will have

  • Building Node.js with GN + i18n
  • Module Ecosystem + Release

@WaleedAshraf WaleedAshraf pinned this issue May 30, 2019
@mcollina
Copy link
Member

+1!

@keywordnew
Copy link
Member

Finalized agenda here: https://github.com/nodejs/summit/blob/master/2019-05-Berlin/agenda.md

Feel free to PR any requests to change!

keywordnew added a commit that referenced this issue Jun 5, 2019
@keywordnew
Add next Collab Summit, move Berlin to past
671b165 
Closes #166, #171, #152, #149, #135.
@keywordnew keywordnew mentioned this issue Jun 5, 2019
Merged
joyeecheung pushed a commit that referenced this issue Jun 6, 2019
@keywordnew @joyeecheung
Add next Collab Summit, move Berlin to past (#178)
2f045a2 
Closes #166, #171, #152, #149, #135.
@keywordnew keywordnew unpinned this issue Jun 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Berlin 2019 Collaborator Summit
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add next Collab Summit, move Berlin to past openjs-foundation/summit
9 participants
@mcollina @jasnell @guybedford @jorydotcom @joyeecheung @WaleedAshraf @mhdawson @keywordnew @evahowe