https://drive.google.com/file/d/0Bx2OM4n1QsxTQWJnMGhlNUJGZk0/view?usp=sharing

For inclusion in the weekly update, or perhaps as a post on its own to publish elsewhere, it might be good to publish a summary of the summit for the wider community.

At minimum, for the update, we could along some stats (# attendance, parts of the world, etc.) along with the topics discussed - easy to pull from the agenda and notes - and some of the outcomes.

relates to nodejs/evangelism#133

• Promises(two issues)
• Governance discussion
• TC39
• Fall Collab Summit, Oct. 6-7: Is second day open to newly onboarded contributors from Day 1?
  • meta contribution session

Please propose Agenda topics that we can consider.

Proposed Subjects

Core

• First Converged Release Schedule
• LTS
  • Roadmap to Second converged LTS
  • Discussion of the key internal changes that still need to be made (e.g. improved abstraction layer, multiple isolates, refactoring internal dependencies -- e.g. the pure js http parser and dns work, etc)
• Debugging and Discussing what we're going to do about domains
• FFI
• tracing_event.h
• API
• Making StreamBase public.

Project / WG

• project goal setting
• timelines
• best practices for issues/meetings

We need to have a followup VM summit during the Collaboration Summit in Amsterdam.

Who wants to step up to lead this?

We ( @bnoordhuis, @piscisaureus, @indutny and myself) will gather and plan a rough sketch for libvu v2.

Finally, another Collaboration Summit!

Collaboration Summit is an un-conference for contributors to Node.js to get together and discuss Node.js :)

We have space for a few hundred people in the same venue as Node.js Interactive the two days following all the talks.

http://events.linuxfoundation.org/events/node-interactive-europe

Node.js Interactive attendees can join for no additional cost. If you are a committer and are not attending interactive we can register you just for the collaboration summit.

/cc @nodejs/members

Content

The content is provided by the participants! Please use this issue to discuss any topics you might want to put on the agenda so that we can flush a few things out before the event.

Travel Assistance

We have some budget to cover travel stipends but it is limited. Any contributors who can't make it without a stiped should comment on this issue and the TSC will give out the stipends where possible based on the budget restrictions.

I would also recommend that contributors in Europe only apply to the event in the EU and US contributors to the one in the US so that we can spread out the funds we have. If you do not live in either the EU or the US, please apply to whichever one you prefer. Also, anyone speaking at the event is already eligible for the same stipend so no need to apply here.

Have a Benchmarking summit during the Collaboration Summit in Amsterdam.

If interested comment here so that we see if there is enough interest to include it.

If we have enough interest I'm happy to lead it.

It was agreed that there is a desire to have WG-of-WGs, which I've been referring to as the "Collaboration WG" the last few days.

As a reminder some of the possible scope discussed included:

• Having the WG act as a switchboard for connecting people or groups together who might not otherwise know where to go
• Acting as a hub for the collection and dissemination of best practices among WGs. This could both be proactive research on how various WGs are operating and also a general dumping ground for ideas when members see things are working well within their groups.
• Networking among some reps from any interested WGs (ideally all WGs) to occasionally met or async. discuss what is working well (or not so well) for them
• Identifying shared needs or tooling among groups to try and reduce overlapping efforts. Relevant successful tooling could be shared; new tooling could be built in coordination with other groups like Website, Build, etc.

Regardless of the name, it would be great to get a repo spun up. I'm happy to get the ball rolling on the "paperwork" (initial repo files, proper proposal on scope, recruiting, etc.)

Edit: I would have just spun up the repo but I do not have access ;)

being discussed at nodejs/readable-stream#275, contact would be either me or or @mcollina and I don't think we have any special needs beyond someplace to physically be.

The last collaborator's summit in Berlin was really productive, and I think most folks are on board with holding them twice a year. I think it makes sense to hold the next one at Node Interactive in Vancouver. Node Interactive itself is on Wednesday October 4th through Friday October 6th.

Here's a few early questions to be answered:

• Do we know if the V8 team has any plans to be in town either before or after, like they were for the Berlin summit? cc @fhinkel @MylesBorins
• Do we want to try and integrate Code + Learn into the summit? There has been discussion about incorporating a Code + Learn into the beginning of the summit, and then help connect the attendees to working groups they are interested in contributing too.
  • I seem to recall we had an issue about this topic somewhere @hackygolucky, but I can't seem to find it. Do you remember if there is an actual issue filed?

UPDATE: Please vote using emoji reactions for which days work best for you:

🎉 - Monday the 2nd and Tuesday the 3rd
❤️ - Saturday the 7th and Sunday the 8th

UPDATE: the Node Interactive venue has been booked for Friday October 6th and Saturday October 7th for the collaborator's summit!

We'd like to put together a Collaborator Summit this August in San Francisco.

We've chosen San Francisco mostly for cost reasons (a good percentage of contributors are on the west coast and we have a lot of offers for free space to host it in) and for ease of organizing since myself and some of the other people who will be helping to organize it live here.

Any active contributor to node.js core or a Working Group is invited. There is no ticket cost but you must be an active contributor.

There will not be any speakers, this is not a conference, this is essentially two days of meetings about technical and project issues.

If you can attend please comment on this thread so we can get an accurate count. If you need travel assistance please note it. The foundation will set a budget for travel assistance and the TSC will prioritize the list of people who need assistance based on the available budget.

Attending

@mikeal
@jasnell
@othiym23
@ofrobots
@piscisaureus
@sam-github
@evanlucas
@wraithan
@cjihrig
@groundwater
@shigeki
@indexzero
@Trott
@TooTallNate
@Qard
@indutny
@nebrius
@emilyrose
@trevnorris
@rauchg
@jedireza
@srl295
@yunong
@Fishrock123
@Starefossen
@snostorm
@yosuke-furukawa
@joaocgreis
@rvagg
@dshaw
@orangemocha
@chrisdickinson
@bengl
@rmg
@matthewloring
@zkat
@csaintamant
@yunong
@distracteddev
@jclulow

So, the initial venue we were looking at fell through and we're currently looking and waiting on several options:

• Mozilla SF
  • My preferred venue as it is quite large and well located for us to leave and go out to lunch/dinner and Mozilla may be willing to provide lunch.
• New Relic SF
  • Large, well located.
  • Waiting to hear from @groundwater if we can book it.
• IBM BlueMix Garage
  • A little tight for 40 people.
  • Waiting to hear from @jasnell if we can book it.
• Famous Downstairs
  • Small for 40 people and somewhat awkwardly arranged for that many people (big pillar in the middle).
  • According to @thealphanerd we have it if we want it.

One of the constraints we're operating under is that we can't actually pay any money, or commit to paying money, for a venue until the Foundations budget is approved on the 27th in the next board meeting, so we're trying for places that don't cost anything.

Would love any other suggestions that are free, in downtown SF, and spacious :)

The days together in Austin, both at the conference and in the Summit afterwards, were IMO great at helping us reach consensus on some issues, review current and recent work, and make some short-term plans; not to mention strengthen our personal relationships! 🍻 Although we communicate informally in many ways, I think it may be good for us to hold "official" Collaboration Summits more than once per year. @nodejs/collaborators what do you think?

When and where might we hold the next Collaboration Summit? Perhaps alongside a conference in the spring or summer?

EDIT:
Confirmed! May 4-5 2017, Berlin
^-Wm
Location: http://co-up.de/ (google maps).

/cc @mikeal @nodejs/tsc

@Trott @addaleax @bengl @rachelnicole @bnb @mhdawson @MylesBorins @jasnell @bnb

This will be a meta collaboration session during Collab Summit, designed to get people new to the project who participated in, say, Code + Learn and then onboarding them into the various working groups participating in the collaborator summit.

I see this going as:

1. We welcome everyone interested in participating.
2. We split people off into buckets according to interests and where they'd like to get started.
3. We show them the relevant repos, collaboration and contributing guidelines(if they exist), and after they feel comfortable...
4. We as leaders walk them over to the working group or folks we know involved and introduce them. 4a. If there is no one present, we do an online intro.

This is super helpful and breaks the 'oh gah I am terrified to say hi to these people but I want to help' barrier. Some of this content already exists in the Getting Started repo, but it's always better to walk through things with folks to make it more personal.

It would be a good idea for us to get together and discuss the release process.

• What is working?
• What isn't working?
• How can we set up a more reliable cadence

/cc @nodejs/release

Follow up to https://github.com/jasnell/vm-summit held in April this year.

Let's try and get some ideas of what we want to try and cover @ the summit and then we can begin to organise them into a proper agenda along with some proper planning along the lines of what @groundwater is suggesting in #6.

We only have 2 days and lots of potential for bikeshedding, rabbit holing and general rambling so we'd better keep it tight. We also have plenty of opportunity for social items so we should absolutely include ideas about that as well (SF locals?).

Here's some suggestions to get started:

• Working group standup / State of the WG: I think we should have representatives from all of the main working groups present so perhaps we can have someone give a quick talk on (a) what the group does, (b) who is involved and (c) any interesting progress or state that can be reported. This is separate to specific agenda items that any group wants to put in.
  • Addon API
  • Benchmarking
  • Build
  • Diversity
  • Evangelism
  • Intl
  • API
  • Docker
  • Hardware
  • LTS
  • Membership (is this a WG?)
  • Post mortem
  • Smoke test (perhaps falls under Build?)
  • Streams
  • Tracing
  • Website
  • TSC (can much be said about this?)
• Introduction to the Foundation: what it is, how it works, who are the people involved, what it means for us
• The path to convergence: we are unlikely to have a converged release out so a discussion / presentation on how that's rolling out and will be handled wrt releases, branches, versioning, LTS, etc. would be helpful.
• Core community: Discussion about how we manage & expand the collaborator group, how we perform onboarding and how we expand the TSC, could also cover mentoring and other means of helping people up-skill.
• Next-Gen: What would a Node-from-scratch look like? The kind of stuff in https://github.com/nodejs/ng/issues - I wouldn't suggest we spend too much time on this rabbit hole as it's more about using the discussion to help inform our shared ideals about the platform, not necessarily about doing anything about the bluesky items.
• Constructive discussion: It's often been pointed out that we have a culture of heavy discussion, mainly in core, it's become how we get things done (and sometimes not done, and that's not necessarily a negative). But this has many drawbacks, including the way it marginalises those who are not as comfortable diving in to robust discussion (likely those on the fringes who won't be well represented at the summit) and those who simply don't have time to read so much text (most of us!). This should be something we could at least have a discussion (oh the irony!) about, to get a shared understanding of the pros and cons of what we do and perhaps find a path to improving.
• V8: Perhaps a discussion about how what happens in V8 upstream impacts us and how we can shield ourselves from the problems it causes while also benefiting from the work they do (a vague topic, but an interesting one for some perhaps?).
• TSC Meeting: We could punt the TSC meeting from the Wednesday to the Thursday and have a quick one, expanded to include anyone that wants to be involved in the discussion (would need to be careful to keep it within a reasonable time limit, also not suggesting that everyone who's there gets a vote).
• NodeUp Live: Assemble a panel towards the end of our time of people that have been most engaged and discuss what we've done (would need to coordinate on sound gear for this, I often take my own when doing this kind of thing domestic--could I get a contact at the venue to talk about what's available there?)

This is a good opportunity to discuss postmortem debugging with the broader group. cc: @lucamaraschi, @davidmarkclements, @mhdawson, @mcollina

Let's plan a Collaboration Summit!

Looking at how we can improve for November from the Amsterdam event. It would be great to do lots of outreach to the various working groups to make sure they know this is happening, that there's lots of space/time for working groups to discuss things, and that each one should represent!

Please edit these things! This is a draft.

Organizers

• William Kapke @williamkapke
• James Snell @jasnell
• Myles Borins @thealphanerd
• ? Your name here ?
• Tracy Hinds @hackygolucky

Working groups in attendance

Things to cover:

• Make plan for contributor meeting
• Share sign up schedule for people to sign up tomorrow
• All presentations should be at the beginning
• Unconf planning time to figure out who wants to work on what and then breakout

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'd like to be able to post times for this on the conf agenda so people are aware of when WG meet and can maybe get a break, if needed. We'll be looking at issues filed in this repo titled "Austin: 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.)
• Evangelism WG
  • @bnb
  • help plan the Evangelism session
• Version Management
  • @ljharb
  • help plan the Version Management session
• Diagnostics WG
  • @joshgav joshgav
  • help plan the Diagnostics session
• VM Summit
  • @jasnell
  • help plan the VM Summit
• Inclusivity WG
  • @hackygolucky and @nebrius
  • help plan the Inclusivity session
  • meeting in "Outside Griffin #1" on Dec. 2, 11am-12pm
• (NEW) Security WG
  • @rvagg and @evilpacket (?)
  • help plan the security session

Day-of Agenda

Dec. 1, 2016
12:00-13:00 Lunch
13:00-14:00 Introduction and presentations pertinent to majority of audience
14:00 - 17:00 Working group breakouts

There are no signups for this day with room breakouts. Wander and find an open room after presentations occur.

Dec. 2, 2016
08:00-09:00 Breakfast
09:00-12:00 Collaborator gathering
12:00-13:00 Lunch break(is lunch provided?)
13:00-17:00 Working group breakouts
Sign up for breakout rooms HERE

AV Setup

• Big projector/screen with HDMI(do we need something else?) and audio output
• Microphone on podium
• A wireless microphone to pass around
• Power outlets for tables
• WiFi

Space Setup(proposed due to venue space available)

The events team shared this image of what they thought should work for Code & Learn and Day one of the Collaboration Summit. They also asked if a crescent table setup would be more helpful, but my suggestion was that it is more important for attendees to be able to sit at tables with each other/mentors and get help for Code & Learn, so chairs on both sides isn't a bad thing because looking at the projector only happens towards the beginning. Does this sound right?

Day One Collaboration Summit:

Day Two Collaboration Summit:
There will be breakout spaces available after the general space meeting occurs(if that's still a thing). This map represents the general space meeting

Outreach

A description of what Collaboration Summit will be a great way for us to spread the word so people will register and attend in Austin. Anyone who would like to attempt a bit of copy for this gets brownie points! PR and Marketing at the Node.js Foundation will happily share this and post the full agenda on the conference website

• outreach to the various working groups to make sure they know this is happening, that there's lots of space/time for working groups to discuss things, and that each one should represent!
• share on Twitter, GitHub, other social media

Logistics to prep

• Figure out a way for any open spaces available for working groups to meet during the conf/collaboration summit to be schedulable online and in-person(large poster or whiteboard because things change last minute and not everyone likes looking at their phones)

Question(s):

• Do we still want to call this Collaboration Summit? I think a slightly more atomic preliminary agenda(understanding the importance of some unconf-ing happening) helps communicate that portions of this program are contributors-only will be helpful, but is there another name that communicates this better?

UPDATE 11/16

• 257 registrants. Attrition expected at %50, but we're needing to close registration now because we will run into space issues if more people show/signup.

UPDATE 11/30
SIGN UP WORKING GROUP SLOTS HERE

Anyone want to talk about WebAssembly?

By late May, the work to make WebAssembly modules just plain ES modules will be underway, possibly with prototypes in JS engines (including V8).

There has also been some discussion around using WASM for "native" modules, so we could hash out what the requirements are and what would need to be added to the spec. @lukewagner from the WASM WG will likely be able to join for this if we have any questions about what changes to the spec are possible.

What is the schedule for the summit? What time on Thursday are we expecting to get started? 8:00am or 9:00am?

See https://tiny.cc/2015-node-summit (editable)

Collaborator Summit is happening next week–October 6-7. We would love to have you suggest what you'd like to see happen by filing issues in this repo. Check out the starter schedule HERE. A recommendation for working groups is to file an issue in your own repo about potential agenda for your working session and link to it on the schedule.

A reminder that you can file for travel fund here.

Could y'all help spread the word and encourage?
@MylesBorins @mhdawson @bnb @rachelnicole @jasnell @dshaw
@nodejs/tsc @nodejs/community-committee

During the last collaboration summit we briefly discussed running a more structured event for next year (Spring 2018), to drive collaborator show-ups.

The best way to run an event, is to empower someone to organize it. Does anyone object?
@dshaw and myself volunteered, is there anybody else that wants to join the team?

Since I'm not sure core's CoC formally applies to this, we should state that this will be under that CoC. (Presumably.)

Go here to add your topic:
https://docs.google.com/spreadsheets/d/1gJoyiq0z6rjS7jEoHkRe6jte8Dd7ZBkwD3WjOh6djvQ

Collab Summit Berlin

May 4-5, 2017
co.up Coworking
Adalbertstraße 8
10999 Berlin, Germany

To get in, go through the big metal gate to the left of Adalbertstr. 7, straight to the far end of the courtyard, and in the first tunnel to your right. Ring the doorbell marked "co.up Coworking UG"

View the Collab Summit Berlin Project Board to schedule your working group and register yourself to attend!

Organizers

• Anna Henningsen @addaleax
• James Snell @jasnell
• Myles Borins @MylesBorins
• Bryan Hughes @nebrius
• Ashley Williams @ashleygwilliams
• Tracy Hinds @hackygolucky

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. This Spring instance of Collab Summit will not include
a morning Code + Learn to learn how to contribute prior to congregating
for the summit. Please look to the Fall Collab Summit in Vancouver, BC 
for this pairing.  

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.

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.)

Day-of Agenda

May. 4, 2017

• 09:00-10:00 Introduction and presentations pertinent to majority of audience
• 10:00 - 12:00 Working group breakouts
• 12:00-13:00 Lunch break (not provided)
• 13:00-17:00 Working group breakouts

Sign up for breakout tables or room HERE.

May 5, 2017

• 09:00-12:00 Collaborator gathering
• 12:00-13:00 Lunch break (not provided)
• 13:00-17:00 Working group breakouts

Sign up for breakout tables or room HERE.

AV Setup

TBD(asked the venue, waiting to hear back)

The venue

The venue

• Seven tables in the big room (±155sqm) that can seat 6-8 people each, with 20 office chairs, 50 wooden chairs, a corner with a couch & a few soft chairs.
• Smaller meeting room(15sqm) seats 6-8 people.
• Welcome to move around the furniture according to your needs!

Day One Collaboration Summit:

• intro setup: chairs for everyone
• afternoon setup: tables pulled out for working groups to meet

Day Two Collaboration Summit:(TBD)
Tables pulled out for working groups to discuss work.

@nodejs/collaborators @nodejs/v8 @nodejs/ctc @nodejs/tsc @nodejs/community-committee We should figure out what topics we want to cover.

Things that were mentioned in #39:

• Spend time working on our issue/PR backlog (#39 (comment))
• Maybe do a small Code & Learn session (also #39 (comment))
• Website issues (#39 (comment)) @nodejs/website
• Streams WG meeting? (more or less implicitly in nodejs/TSC#235) @nodejs/streams
• HTTP/2
• N-API

… what else? No doubt there’s enough ground to cover here.

Node+JS Interactive - Oct. 10-12, 2018

f.k.a. Node.js Interactive

@ Vancouver, BC

https://events.linuxfoundation.org/events/js-interactive-2018/

Collaboration Summit

Dates: Oct. 12-13, 2018

Organizers

• Dan Shaw @dshaw
• Matteo Collina @mcollina
• Manil Chowdhury @chowdhurian (in Vancouver)

Let's talk about internationalization and localization!

From https://github.com/orgs/nodejs/teams/i18n:

The recent Node.js i18n proposal has met consensus, and there’s going to be a lot to talk about and do.

The work will probably already be underway by the time May/June rolls around. If there's enough interest at the summit, I'd love to lead and/or participate in a discussion about this effort.

As per #1 (comment) Mikeal and I talked about using a facilitator for all summit meetings.

Facilitating a meeting can be difficult, and even just a few hours can wear someone out. Given that there are 3 sessions a day, I'm recommending at least 3 people to spread out the load.

Given the multiplicative effect a good/bad facilitator can have on a discussion, I would like to run a introductory workshop for anyone interested in learning to facilitate. I would prefer to select the summit volunteers from attendees of the workshop, but volunteering is not a requirement of the workshop. No commitments need to be made to volunteer before the workshop.

Ideally, the workshop would be 1-2 weeks prior to the summit. I realize this may exclude people who are travelling specifically to attend the summit. If there are a lot of people interested who are travelling, I may re-visit this choice.

About Facilitating

A facilitator is a non-participant in the meeting they are guiding. Their role is to combat cognitive biases, and direct the meeting according to the best needs of the group.

The most important part of being a facilitator is trust. The group must trust you.

If you have a strong stake in the topics you're facilitating, the group may choose not to trust your objectivity. This does not exclude you from participating. It just means maintaining trust comes first.

Workshop

The workshop will be interactive. We will practice facilitating discussions, with each person having a chance to practice.

You can (and are encouraged to) attend even as an audience member only. This will help participants practice against larger groups.

Call to Action

• Please comment here if you are interested in attending (keep in mind the time window) as either a facilitator or passive-participant.
• Optional you may indicate if you wish to volunteer to facilitate for the summit. You can opt-in/out later. This is just straw poll.

I can probably lead this, see https://github.com/nodejs/api#js-api

What has been the most obvious and lasting effects of the last summit?

What are we lacking and would want to see from a future summit?

I would like to lead a talk about Collaboration on GitHub. As part of it, I would like to go over some of the great ideas that have been suggested- and see what else surfaces!

/cc some bot folks: @nodejs/build

Typically talks requires a bit of prep!
I think we should open an issue on each WG repo to ping them, so that we know who is going to speak.

Agenda

• 9:00 – 12:00 Morning Session
  • 9:00 – 9:30 Breakfast / Meet & Greet
  • 9:30 – 10:30 FFI Presentation / Status Update
  • 10:30 – 10:45 Break
  • 10:45 – 11:45 N-API Presentation / Status Update
  • 11:45 – 12:00 Logistics for Landing into Core
• 12:00 – 1:00 Lunch
• 1:00 – 4:00 Open Agenda
  • Spill over from morning discussions
  • N-API Roadmap (evangelism, documentation, support, repository and distribution, etc)
  • Node-VM Compliance
  • Inspector Protocol
  • Gyp/gn
  • Others (Put other topics here)
    • ?
    • ?

Would be great to get an Evangelism WG group together at the Summit.

Some topics we could talk about:

• Ramping up the Evangelism WG into full-swing again
  • Define an Evangelism WG master-plan for 2017, with some broad, overarching goals that we can dig deeper into and iterate on (#37 (comment)).
• Engaging the community further
• Building more blog content
  • Enabling the blog to be "better" (metadata for sharing)
• What tasks can the WG take on at this point?
• What can we do to get the boll rolling (faster) on current tasks?
  • Weekly Updates - How can we improve?
  • Issue Summaries (nodejs/evangelism#243)
  • Updating the Node.js Wikipedia (YIKES! nodejs/evangelism#102)
• Which old tasks can we/should we work on?
  • The Enterprise Case for Node.js (nodejs/evangelism#239)
  • Cadence for StackOverflow Open-source Ads (nodejs/evangelism#214)
  • Official Node.js Podcast (nodejs/evangelism#204)

If anyone has questions or suggestions on topics, happy to add them!

I would like to (if possible) go into each meeting with a list of prioritized goals. I think @mikeal has volunteered to help drive an online consensus of those goals. There are six total meetings, but I think our final meeting should be "future goals".

So @mikeal I wonder if you can drive a process here, or in another thread to come up with five meeting plans. This process is free to change as it needs to, but I would like each plan to contain the following:

1. A general or specific list of prioritized goals. Shorter descriptions are better.
2. A description of documents the meeting intends to produce. Remember given the time constraints, this document will likely not exceed one page. If you want to produce multiple documents, please prioritize them.
3. A list of topics off-limits for that meeting, this includes topics to be discussed in other meetings.

Given the above, the facilitators will try their best to drive each meeting towards the outcomes listed in the plans. Keep in mind, the group is free to alter course as they see fit. The facilitators role is not to forbid discussion, but to coordinate discussion. A meeting plan is just the starting point for any meeting, but without a plan it would likely take the entire time to just agree on meeting goals.

For awareness -> nodejs/diagnostics#121

I'm sure this is a question for @mikeal. You said in #16:

We have space for a few hundred people in the same venue as Node.js Interactive the two days following all the talks.

Will there be any AV setup for people to display their screen if they want?
"A few hundred" is a lot... so microphone(s)?
Will there be multiple topics at a time?

I think this is important to know so people can come better prepared to share their thoughts. (like bring a HDMI adapter for your USB-C only laptop!)

A bunch of us have gpg keys. It would be a good idea to use this as an opportunity to sign each others keys in person.

The network of trust is very important

Heya, I'd like to resurrect the Collaborator Summit to run either before or after Node.js Interactive in Amsterdam and Austin.

This was an un-conference for Node.js Contributors that I think we should try to run again.

We'll need to figure out how we are structuring this and what the criteria for admission because what we did last time won't scale the size the collaborator base is now.

We also have some budget for sending people if you need it. We'll want to figure out how many people need it and then design a criteria for accepting. We also need to figure out how many rooms and what size for budgetting as well.

Really quick task: Can someone with access to this repo close the issues that are no longer relevant?

...and then go ahead an close this one too!

Collaborator Summit Berlin 2018

We are back with the date for the Node.js Collaborator Summit in Berlin next to JSConf.Eu (which is on June 2-3, 2018).
This is a live issue that will be constantly updated to match the proposed agenda.

Collaborator Summit Day One: May 31st, 2018

AWS Berlin
address Krausenstraße 38, 10117 Berlin, Germany
9am-6pm

Facilities

Main space: 80 in theatre seating, projector, kitchen restroom can be rearranged(can be split into two smaller rooms as well as just moving chairs around)
Other spaces:
3 meeting rooms, each 12-14 people
1 larger 20 people. theatre seating for 30-40 and also had a large screen
tons of white board space throughout

Agenda

if you want to speak and present a topic, feel free to reply to this issue with a brief abstract.

Collaborator Summit Day Two: June 1st, 2018

Mozilla Berlin
address Schlesische Str. 27, 10997 Berlin, Germany
9am-6pm

Agenda

if you want to speak and present a topic, feel free to reply to this issue with a brief abstract.

Organizers

• Dan Shaw @dshaw
• Matteo Collina @mcollina
• Myles Borins @MylesBorins
• Olivia Hugger @oe
• Tracy Hinds @hackygolucky

Attendance

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. This Spring instance of Collab Summit will not include
a morning Code + Learn to learn how to contribute prior to congregating
for the summit. Please look to the Fall Collab Summit in Vancouver, BC
for this pairing.

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.

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.

PLEASE follow the instructions for application to receive travel funds HERE.

@nodejs/collaborators @nodejs/v8 @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 morning, and breakout rooms in the afternoon. 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.

I would like to have an informal session on "how streams works" internally, discussing the code, and seeing if we could see ways for improving it.

cc @nodejs/streams who is coming and can help?

Official version management has become a significant topic. Seems like a good candidate for Collaborator Summit!

/cc @ljharb

Post your ideas here:
http://www.ideaboardz.com/for/Collaboration%20Summit/2490012

Transferring from nodejs/diagnostics#58

Some topics from that thread:

• tracing: controller, protocol, format
• async_hooks
• es6 module patching
• inspector protocol and tools

/cc @nodejs/diagnostics @watson

cc @bnb @rachelnicole @nodejs/community-committee

Ideas for CommComm in-person session:

• What does a community roadmap for 2018 look like?