Collaborator Summit 2019 - Berlin Edition - 30th and 31st of May

[mcollina]

The Vancouver 2018 Collab Summit is just finished, and it's time we start planning for next year first event.

Who is up for helping with the organization?

I would like to propose we do it again in Berlin before JSConf.eu on the 30th and 31st of May. I would kindly ask @MylesBorins and @hackygolucky to ask the Board if they could fund a venue for the 2-day event.

cc @nodejs/tsc @nodejs/community-committee @ladyleet

Registration: https://www.eventbrite.com/e/openjs-collaborator-summit-tickets-55985971548
CFP: https://docs.google.com/forms/d/e/1FAIpQLScneYhY4iqm8x2C2AO9EEzJ5smkOKhLqfxEMQcfNvP5rvXfHg/viewform

[trivikr]

Hi @mcollina, I attended Vancouver 2018 Collab Summit and had a great time.
I would like to help organize Berlin summit, is there a wiki/notes on responsibilities of the organizers?

[jasnell]

One bit of feedback I heard yesterday was that saving all the lightening talks to the end of day 2 so we're prioritizing the working sessions.

[thefourtheye]

I also would like to help with organizing.

[mmarchini]

I would like to help to organize as well :)

[benjamingr]

I would love to help with this and attend!

[mcollina]

I would like to help organize Berlin summit, is there a wiki/notes on responsibilities of the organizers?

Overall, ensuring that the event run smoothly. These includes:

1. Ensure adeguate space is reserved for the summit, number of rooms, "hallway track", and so on.
2. Determine the agenda before hand, and make sure everything is in place. This is typically a time sync and it includes a lot of guessing and back-and-forth to minimize the chance that a collaborator would like to attend two session at the same time as multiple people are involved in multiple discussions. @joyeecheung defined it as "playing Jenga" :D.
3. MC the event, this typically includes a moment for agenda-bashing at the beginning and presenting the closing event.
4. Deal with problems when they arises, including during the summit. This also include broadcasting our contacts for potential CoC violations during the summit.

[ryzokuken]

I would love to help out in any way I can.

[hackygolucky]

Noted! We are waiting to have budget conversations and talk 2019(the Budget/Finance subcommittee was not able to meet during Interactive), but we'll make sure to mention this as part of conversations re: to community support/events budgets.

…

On Tue, Oct 16, 2018 at 10:41 AM Ujjwal Sharma ***@***.***> wrote: I would love to help out in any way I can. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#135 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB46oMWmQabayF-xk_5iYMfWCyTA9oTsks5ulfAVgaJpZM4XbYbP> .

[sagirk]

I would love to attend and make myself useful in any way I can! ❤️

[mhdawson]

+1 to limiting the "talks" to the end and making them short (~ the length we had for lightning talks this time). I think its best if most of the time should be for discussions for the WGs/teams or other specific topics.

[Trott]

I'd also be OK with leaving a very large chunk of the agenda open until the day of, and then bash the agenda for 20 minutes at the start, unconference style. (I'm also OK if the organizers don't want to do it that way. Just a suggestion.)

[mcollina]

Considering my experience of the last two, my impression is that we need the core of the work already done. On Sunday moving 3 slots took me a couple of hours of work to make (almost) everybody happy.

[WaleedAshraf]

✋ for all kind of help in organizing next in Berlin.
I think we should be clear how much time a session would take. For example, Governance went for the whole day (and a half) and that wasn't still enough.

[MylesBorins]

If moving three slots took hours, that may be a reason to not overly lock the agenda in advance. Having more flexibility on the day can allow us to lock in the agenda based on who is there

…

On Tue, Oct 16, 2018, 7:30 PM Waleed Ashraf ***@***.*** wrote: ✋ for all kind of help in organizing next in Berlin. I think we should be clear how much time a session would take. For example, Governance went for the whole day (and a half) and that wasn't still enough. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#135 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAecV5lTlHOMYkI-nGmEFaewEX38nxWeks5ulmwvgaJpZM4XbYbP> .

[mcollina]

I would note that without a predetermined draft + the survey that Joyee set up we would not be able to be as productive. The overall feedback from Vancouver 2017 and Berlin 2018 has been that more structure is needed. I think that Vancouver 2018 was a good balance. If we swift towards a more unconference style, it’s likely that meeting agendas and presentations will not be prepared. One problem that I note is that we lacked several members in a lot of discussions (modules for example). We should be checking in advance if members will be there when proposing/scheduling a session. Maybe we should upvote them in advance? Il giorno mer 17 ott 2018 alle 16:31 Myles Borins <notifications@github.com> ha scritto:

…

If moving three slots took hours, that may be a reason to not overly lock the agenda in advance. Having more flexibility on the day can allow us to lock in the agenda based on who is there On Tue, Oct 16, 2018, 7:30 PM Waleed Ashraf ***@***.*** wrote: > ✋ for all kind of help in organizing next in Berlin. > I think we should be clear how much time a session would take. For > example, Governance went for the whole day (and a half) and that wasn't > still enough. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#135 (comment)>, or mute > the thread > < https://github.com/notifications/unsubscribe-auth/AAecV5lTlHOMYkI-nGmEFaewEX38nxWeks5ulmwvgaJpZM4XbYbP > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#135 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADL4w-uGozcZVG_e_LG3S331vsG3Q2Aks5ulz84gaJpZM4XbYbP> .