Community-committee: Node.js Foundation Community Committee (CommComm) Meeting 2017-04-13

Created on 12 Apr 2017  路  11Comments  路  Source: nodejs/community-committee

Time

UTC Thu 13-Apr-2017 20:00 (08:00 PM):

| Timezone | Date/Time |
|---------------|-----------------------|
| US / Pacific | Thu 13-Apr-2017 13:00 (01:00 PM) |
| US / Mountain | Thu 13-Apr-2017 14:00 (02:00 PM) |
| US / Central | Thu 13-Apr-2017 15:00 (03:00 PM) |
| US / Eastern | Thu 13-Apr-2017 16:00 (04:00 PM) |
| Amsterdam | Thu 13-Apr-2017 22:00 (10:00 PM) |
| Moscow | Thu 13-Apr-2017 23:00 (11:00 PM) |
| Chennai | Fri 14-Apr-2017 01:30 (01:30 AM) |
| Tokyo | Fri 14-Apr-2017 05:00 (05:00 AM) |
| Sydney | Fri 14-Apr-2017 06:00 (06:00 AM) |

Or in your local time:

Links

Agenda

Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/community-committee

  • 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

Invited

  • Ashley Williams @ashleygwilliams (CommComm)
  • Bryan Hughes @nebrius (CommComm)
  • Emily Rose @emilyrose (CommComm)
  • Gregor Martynus @gr2m (CommComm)
  • James Snell @jasnell (CommComm)
  • Jenn Turner @renrutnnej (observer)
  • JP Wesselink @jpwesselink (CommComm)
  • Mikeal Rogers @mikeal (observer/Node.js Foundation)
  • Myles Borins @MylesBorins (CommComm)
  • Rachel White @rachelnicole (CommComm)
  • Rod Vagg @rvagg (CommComm)
  • Tracy Hinds @hackygolucky (CommComm)
  • William Kapke @williamkapke (CommComm)

Notes

The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

Google Hangouts; link will be posted here shortly before the meeting starts.

A standing invitation exists for all @nodejs/TSC members who are not also CommComm members to attend in observer capacity.

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.

Most helpful comment

Also note: I updated make-node-meeting to include a CommComm example at https://github.com/rvagg/make-node-meeting/pull/11. To those of you with write access, PTAL.

All 11 comments

I tagged a few initial issues with cc-agenda, but everyone feel free to tag more! I'll rerun the agenda generation right before the meeting

Also note: I updated make-node-meeting to include a CommComm example at https://github.com/rvagg/make-node-meeting/pull/11. To those of you with write access, PTAL.

@nebrius .... ur awesome. Thanks for doing all this/that!

what's the link for hangout?

edit: OH DRAT THIS IS THURSDAY

Awesome work!

I think I created the event correctly...it's changed a _lot_ since I last did this 馃槄.

Event link: https://www.youtube.com/watch?v=lLUr1AQ2Qk0

AFAICT, I won't have the Hangouts on Air link until I actually start it. I'll be sure to hop in about 15 minutes early to make sure everything goes smoothly, and I'll post the link here as soon as I have it.

Hangouts on Air link for participants: https://hangouts.google.com/hangouts/_/ytl/tnlgfsdE6mWNm9gZaCpIQymHSYhKgUnCFWSD0ntFWzw=

Let me know if you have any issues connecting.

I don't think I'm going to get to attend for the whole meeting, so during the ~ stake your claim ~ I'm interested in the following:

https://github.com/nodejs/code-and-learn
https://github.com/nodejs/education
https://github.com/nodejs/evangelism
https://github.com/nodejs/inclusivity

I'll x-post this to the other issue as well.

Hii! Mixed up my time zones but joining late 馃拑

@nebrius Can this issue be closed? Old Meeting. 馃槃

@bnb, yep!

The best practice is to leave this PR open until the notes have been merged, and then drop a link here to the notes PR.

Notes for this meeting have been merged at https://github.com/nodejs/community-committee/pull/32.

Was this page helpful?
0 / 5 - 0 ratings