Node.js Foundation Community Committee (CommComm) Meeting 2017-05-04

[hackygolucky]

Watch notes in real time! Ping us if you'd like us to broadcast from the Collab Summit.

• Minutes Google Doc:
  https://docs.google.com/document/d/1jR_dCInLb8_m-IScd0w57x-qUm3dvQxc2rYNNgPUGtU/edit?usp=sharing
• Previous Minutes Google Doc: https://docs.google.com/document/d/1YevHuA_csoTltDJ6mHr21fetZshNqWpsRbBRkSHhmYE/edit

Agenda

• What is a member?
• 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?
  Elect a Chairperson #30
  Collaborator's Summit agenda #28
  governance: who has voting rights? #21
• Add some scope (aka: stake your claim!) #13
• Central communication medium for chatting in Node.js #11

[bnb]

@hackygolucky I didn't have cycles to check this repo for issues yesterday, but would have loved to have expressed interest in a broadcast and participated if possible - if there would have been more lead time, I definitely would have caught the issue and asked 😄 Disappointed that two consecutive meetings haven't been broadcast.

Would a policy to create an issue for the next meeting at the end of when a meeting ends be appropriate? I think that allows it to be fresh in the members' minds and be a checkbox as a part of the meeting that will enable and allow growth and further participation in the next meeting.

[nebrius]

Disappointed that two consecutive meetings haven't been broadcast.

So, technically speaking the collaborator's summit wasn't a meeting and wouldn't have been recorded either way due to the structure of it. Also, I doubt you would have wanted to wake up at 10AM CEDT (4:00AM EDT) ;-)

Would a policy to create an issue for the next meeting at the end of when a meeting ends be appropriate?

There's already an entry in the shared Node.js calendar, but it would be easy enough to create a stub. The agenda wouldn't be accurate, but we could regenerate that closer to the meeting.

FYI the schedule is every other Thursday at 20:30 UTC, so the next one will be this Thursday. I'll get the issue filed for that one right now.

[nebrius]

Closing this, since collab summit is finished.