Community-committee: Node.js Foundation Community Committee (CommComm) Meeting 2018-01-11

[bnb]

Time

UTC Thu 11-Jan-2018 17:00 (05:00 PM):

| Timezone | Date/Time |
|---------------|-----------------------|
| US / Pacific | Thu 28-Dec-2017 09:00 (09:00 AM) |
| US / Mountain | Thu 28-Dec-2017 10:00 (10:00 AM) |
| US / Central | Thu 28-Dec-2017 11:00 (11:00 AM) |
| US / Eastern | Thu 28-Dec-2017 12:00 (12:00 PM) |
| Amsterdam | Thu 28-Dec-2017 18:00 (06:00 PM) |
| Moscow | Thu 28-Dec-2017 20:00 (08:00 PM) |
| Chennai | Thu 28-Dec-2017 22:30 (10:30 PM) |
| Hangzhou | Fri 29-Dec-2017 01:00 (01:00 AM) |
| Tokyo | Fri 29-Dec-2017 02:00 (02:00 AM) |
| Sydney | Fri 29-Dec-2017 04:00 (04:00 AM) |

Or in your local time:

• https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community+Committee+%28CommComm%29+Meeting+2017-12-28&iso=20180111T17&p1=1440

Links

• Minutes Google Doc: https://docs.google.com/document/d/1Ct96kVuGAxcA602ca0gfYN4vAM8G_6ypH4CtwBU38Yo/edit?usp=sharing
• Previous Minutes Google Doc: https://docs.google.com/document/d/1KjaFIdIwfTYUMPNp7LlQzpydp4gbTDZGDnlKUX78J3c/edit?usp=sharing

Agenda

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

• Charter, expectations and responsibilities enterprise-advisory-group/5
• doc: update GitHub Org Management Policy to reflect actual practice tsc/465
• Not all members of the GitHub org are members of the members team tsc/284
• add website redesign initiative #205
• Internationalization/Localization Working Groups #114
• Explain inclusivity better #117
• Mentorship Initiative #206
• Documentation Discussion during diagnostics WG meeting #163
• If someone submits a PR, should we invite them as an Observer? #143
• Issuing badges for contributors #212

Private session, per member request:

• Add @obensource as CommComm member #210
• Add @JemBijoux as CommComm member #209
• Add @chowdhurian as CommComm member #208
• Request to add dshaw as CommComm member #207

Invited Members and Observers

• @ashleygwilliams (Ashley Williams - CommComm)
• @emilyrose (Emily Rose - CommComm)
• @gr2m (Gregor Martynus - CommComm)
• @joesepi (Joe Sepi - CommComm)
• @jpwesselink (JP Wesselink - CommComm)
• @mhdawson (Michael Dawson - CommComm)
• @msmichellegar (Michelle Garrett - CommComm)
• @rachelnicole (Rachel White - CommComm)
• @bnb (Tierney Cyren - CommComm)
• @hackygolucky (Tracy Hinds - CommComm)
• @williamkapke (William Kapke - CommComm)
• @refack (Refael Ackermann - CommComm)
• @therebelrobot (Oz Haven - observer)
• @chowdhurian (Manil - observer)
• @ParidelPooya (Pooya Paridel - observer)
• @rykerrumsey (Ryker Rumsey - observer)
• @baez (Behzad Karim - observer)
• @BinarySo1o (Therese Stirling - observer)
• @JemBijoux (Jem Bezooyen - observer)
• @amiller-gh (Adam Miller - observer)
• @obensource (Ben Michel - observer)
• @yosuke-furukawa (Yosuke Furukawa - observer)
• @Maurice-Hayward (Maurice Hayward - observer)
• @dshaw (Dan Shaw - observer)
• @mikehostetler (Mike Hostetler - observer)
• @sarahkconway (Sarah Conway - observer)
• @Tiriel (Benjamin Zaslavsky - observer)
• @DiegoZoracKy (Diego ZoracKy - observer)
• @ZibbyKeaton (Zibby Keaton - observer)
• @tobyfarley (Toby Farley - observer)
• @Bamieh (Ahmad Bamieh - observer)
• @pchrysa (Chrysa - observer)
• @foadlab (observer)
• @jasnell (observer)

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

Zoom Meeting; a 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/channel/UCQPYJluYC_sn_Qz_XE-YbTQ/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.

[Tiriel]

Will be there!

[ghost]

might have to leave early since i have a nodeschool to organize, but i'll be there

[bnb]

Realized my first search for cc-agenda was scoped to Issues, going through and adding PRs labeled with cc-agenda now.

[ghost]

we should probably discuss the member things in private commcomm member scope, yeah?

[bnb]

@pup I don't have an issue with that 👍

[bnb]

@pup I have tried to front-load the agenda items you've been involved in since you may have to drop early.

[bnb]

Join link for today's meeting: https://zoom.us/j/209550902

[joesepi]

I’m so sorry I can’t join today. Important meeting. :(

On Thu, Jan 11, 2018 at 11:50 AM Tierney Cyren [e-mail]
wrote:

Join link for today's meeting: https://zoom.us/j/209550902

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/community-committee/issues/213#issuecomment-356989159,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIxNPOSUQMGww2kXIL-22hz4XX9aUOvks5tJjvMgaJpZM4Ra7bq
.

[jasnell]

I was going to join to discuss the Enterprise advisory group but I've had an urgent conflict come up and won't be able to make it

[dshaw]

Thanks @jasnell. I covered it. We had a very constructive discussion about how the CommComm can help land this. We will post invites to both CommComm and TSC to send representatives to the next meeting.

[bnb]

No worries @jasnell and @joesepi. Thanks for letting us know - hopefully everything's all good (for both of you). ❤️

[tobyfarley]

Can someone update the attendance spreadsheet? I first attended on 10-26-2017 and have only missed the 11-08-2017 meeting. I believe I may have been marked as missing on 11-30-2017 but I was there. It took a few minutes to find the zoom link and I was a bit late for that reason.

[bnb]

cc @williamkapke ☝️ talked about it with Toby before the meeting, don't think you were in yet. Just wanted to let you know.

[dshaw]

There's an attendance spreadsheet? That would be useful. I couldn't find it. If it's not public, could someone DM me?

[dshaw]

@bnb @rachelnicole Any news on the new member vote?

[williamkapke]

Here is a link to the attendance spreadsheet: https://docs.google.com/spreadsheets/d/1PbmX0kYsPekn2ZUI8Nef-UcjxlhwX9r7oHmNdjR4000/edit?usp=sharing

I made it a while back and It reflects the list of people listed in the "Present" section of the meeting minutes we have published. As such- there's nothing private to it. It was just an "unofficial" report I did to help get an overview... and I'm happy if ya'll find it helpful. I gave @bnb full access to it and invite any CommComm member to work on it. (He should be able to give access to other too)

I don't want to miss out on rewarding anyone for their efforts!

^{Note 1: It could be automated from the minutes PRs.
Note 2: We could make this a CSV file, check it in, and Github would provide a decent display of the data.}

@tobyfarley, This was done manually and there's no doubt I missed some or even added some. Or, people were not listed in the Minutes- which I encourage everyone to open PRs to correct any inaccuracies.

[bnb]

@dshaw I will be working with @hackygolucky to get the vote to members out shortly. Your patience is appreciated. 🙏

[obensource]

@bnb don't mean to pester–but excited to see the results of the new member vote when they're available. Any movement on that? :D

[bnb]

@obensource we gave the members 48 hours to vote. That 48 hours ended ~20 minutes ago. I'm super busy with some work things for the next few hours, but I'll try to go in and wrap the votes up tonight 👍

[obensource]

@bnb oh rad! I wasn't aware of the voting timeline (or I wouldn't have asked lol, sorry). No pressure at all, was just curious.

Thank you Tierney! 🎉

[bnb]

No worries! We intentionally didn't share the timeline so as not to set up expectations if something went wrong with the voting tooling. Never any harm in asking. <3

I'll note: One of the votes was slightly delayed (100% my fault, got busy with some work things), and will wrap up tomorrow at 10am ET. 

From: Ben Michel [e-mail]
Reply: nodejs/community-committee [e-mail]
Date: January 19, 2018 at 2:24:05 PM
To: nodejs/community-committee [e-mail]
Cc: Tierney Cyren [e-mail], Mention [e-mail]
Subject:  Re: [nodejs/community-committee] Node.js Foundation Community Committee (CommComm) Meeting 2018-01-11 (#213)

@bnb oh rad! I wasn't aware of the voting timeline (or I wouldn't have asked lol, sorry). No pressure at all, was just curious.

Thank you Tierney! 🎉

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[obensource]

@bnb that makes perfect sense. Awesome, thanks for sharing and being rad! ❤️

[ghost]

@bnb meeting notes!

[bnb]

Thanks @pup, PR: #219