Call for Sessions: Berlin Collab Summit

[jorydotcom]

We're experimenting with a Google Form for session submissions this year - we're hoping that this will help us reach more into the JS Foundation project communities and provide an easier view of all the potential sessions. As with previous years, you welcome and encouraged to use GH issues on this repo to organize your session, and you are able to view all submissions.

The summit will be May 30-31 at Courtyard by Marriot, Berlin City Center. The call will be open until at least April 20 (per #143) but we may extend that as needed. As @mcollina says, this is about collaboration so we are inclined to be flexible... "it’s time to book travel folks, let’s meet in Berlin!"

CFP Link
https://goo.gl/forms/am0v5njskQnABQMO2

Venue updated with confirmed info from #157

[mhdawson]

If we already opened a GH issue with a suggestion do we need to submit through the form as well?

[jorydotcom]

@mhdawson if you don't mind, otherwise I am happy to add it for you!

[mhdawson]

@jorydotcom thanks for the response. I think there may be more suggestion so I'll try to add it in the tool when I do those as well.

[Trott]

@keywordnew Is the tsc-agenda label on this for visibility (that is, to make sure the TSC knows about this) or is there something that TSC needs to do or decide?

[keywordnew]

@Trott thank you for pinging to clarify. It's for visibility. So people see it sooner then have plenty of time to submit and/or make travel fund requests in these 2 months leading up to the next Collab Summit.

[Fishrock123]

I'd like to be clear that if this is a collaborator summit there should not be conference-like workshops aimed at non-collaborators.

As such I would strongly object to running stuff like this at the event:

We have a ~3-4 hour workshop for how to get started with modern Dojo. We have a lot of users in Germany and it would be a great opportunity to get them to the event to learn more about the foundation and to get them up to speed with the new Dojo.

[Trott]

Mentioned at TSC meeting today, removing tsc-agenda label. Feel free to re-add it if there's more for the TSC to do, of course.

[keywordnew]

Removing this from the CommComm agenda. There is an existing Collab Summit update issue that remains open for regular discussion. Feel free to re-add if needed :)

[keywordnew]

Anyone who wants to can still submit a session proposal for the Collab Summit using this issue template.

[joyeecheung]

Where is the source of truth for a list of proposals? The issues here or the Google form? There seem to be some proposals that only live in one of them.

[jorydotcom]

@joyeecheung we are periodically moving proposals from GH into the response sheet here. It's the source of truth we'll use to make sure all the proposals are evaluated and added to the agenda!

[boneskull]

I wanted to lead a meeting for the tooling group and have submitted a proposal to that effect. Should I be worried about not getting a slot for this?

[benjamingr]

Should I be worried about not getting a slot for this?

In the past, slots were never a problem and we just split into more groups when we needed to do several things.

[obensource]

@mcollina awesome! I'd love to lead a breakout session for members of the i18n WG, to cover how we can continue to push forward efforts like:

• l10n: CommComm Initiatives for internationalizing the API docs, and the website redesign project.
• Intl in Node.js: How the i18n WG can focus on supporting current Intl development in node core, and get more folks to help out with the core WG.
• The i18n WG's role in ECMA 402: How we can scale the i18n WG's involvement and support for tc39 in ECMA 402, and what the current needs are that Node.js representatives can fulfill for pushing JavaScript's Intl specification forward.

cc @nodejs/i18n @nodejs/intl @zeke @vanessayuenn @srl295 @littledan @watilde @RichardLitt @TiagoDanin @JCMais @maddhruv @lukaszewczak – and anyone else that's interested! 🎉

👉 Correlated issue: #164

[evahowe]

Hello all! I work with Tracy and I am in the process of updating the agenda and pulling in the topics that I currently have. @joyeecheung and @boneskull I have both of your proposals on the draft agenda. @obensource what would you like to call yours and how much time would you like?

[obensource]

@evahowe I believe we've covered all the bases in our convo in #164. 🎉

Re amount of time: We'd love to have enough time to make headway on a few things, I'm guessing the typical amount of time allocated for other standard meetings would probably work for us? Thoughts? Thanks a million! 🙌

[keywordnew]

We'll do our utmost to get everyone a slot and as much time as possible.

There's also a room specifically allocated for unscheduled discussions, which if available could also be used for discussions that are overflowing their time.

[littledan]

Where can we find the draft agenda?

[mcollina]

@littledan our draft is in: https://docs.google.com/spreadsheets/d/14NvqXdtcQkh21U3mdqQuR24oQeUmGDWHer373swQGvg/edit#gid=674659463

---

The cfp will close on Monday 20th of May.

[hekike]

@mcollina the User journeys session and @mhdawson's session are at the same time, can we swap around to avoid conflict? Micheal is involved in the User journeys Initiative and Best Practices which are related to each other.

[gireeshpunathil]

@mcollina - also, my second session (30/05 4 PM main hall - Discuss pain points of Node.js users)
is redundant to first one (30/05 10 AM munich1 - insights from nodejs/help repo) - not sure how I ended up submitting twice! You may please retain the 10AM one and release the 4PM one for some other topics, thanks!

[keywordnew]

@hekike done. 👍🏽

@gireeshpunathil thank you for the specifics! Done.

[WaleedAshraf]

@keywordnew I think it'd be good to avoid as many conflicts as we can. And only squeeze when there are more sessions.

[hekike]

@keywordnew Thanks!