Collaborator's Summit agenda

[nebrius]

The next collaborator's summit is coming soon! It will be held on May 4th and 5th in Berlin, right before JSConf EU. Details are at openjs-foundation/summit#41.

What would we like to discuss at the collaborator's summit for the CommComm?

[nebrius]

We discussed a few ideas in today's meeting for the agenda:

• Flesh out communication channels for the project:
  • Make an official, CoC compliant list of places we can send folks needing help!
  • Document what problems we are trying to solve
  • Update the cross-posted issue that we propose not to choose one over the other
  • Can we create a hook from /help into IRC and/or Slack for people to get smaller help in realtime
• Moderation training
• Create a meta collaboration sessions at the fall Node Interactive, 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.
• How do we go about bringing other communities into the Community Committee and Node.js Foundation?
• Is there such a thing as a roadmap for the Community Committee? What would that look like?

What does everyone think? Do you have any other ideas for things to put on the agenda?

[nebrius]

Cross posting from openjs-foundation/summit#41:

I grabbed the small room for CommComm during the first session on the first day. I figure we can use this to figure out goals/scope for CommComm during collab summit (and hopefully short to medium term goals for the group as a whole over the coming months).

[nebrius]

After chatting at lunch today with a few folks, I think we should also work on a "guide to the Foundation" document of some sort that describes all of the various groups and people in the project. The goal of such a document would be to guide people with questions to the right place, instead of "I know someone (usually Mikeal), I'll ask them."

[nebrius]

Somewhat related, I was chatting with someone about communication and location of content, in this case about the buffer constructor issue in specific. The specific issue here was that some parts of the discussion were in CTC meetings and that part of the discussion wasn't effectively relayed back to the GitHub issue, which made the conversation hard to follow for folks with a vested interest in the issue but weren't collaborators.

More generally, it's hard for people who aren't following the Node repos closely to follow along, and sometimes these are the people we want feedback from the most (e.g. popular module authors).

We should be able to find a way to surface info better and make it easier to get input from non-collaborators with an important point of view.

[nebrius]

Closing since collab summit is done.