Community-committee: Node.js Foundation Community Committee Meeting 2018-05-17

[mhdawson]

Time

UTC Thu 17-May-2018 16:00 (04:00 PM):

| Timezone | Date/Time |
|---------------|-----------------------|
| US / Pacific | Thu 17-May-2018 09:00 (09:00 AM) |
| US / Mountain | Thu 17-May-2018 10:00 (10:00 AM) |
| US / Central | Thu 17-May-2018 11:00 (11:00 AM) |
| US / Eastern | Thu 17-May-2018 12:00 (12:00 PM) |
| London | Thu 17-May-2018 17:00 (05:00 PM) |
| Amsterdam | Thu 17-May-2018 18:00 (06:00 PM) |
| Moscow | Thu 17-May-2018 19:00 (07:00 PM) |
| Chennai | Thu 17-May-2018 21:30 (09:30 PM) |
| Hangzhou | Fri 18-May-2018 00:00 (12:00 AM) |
| Tokyo | Fri 18-May-2018 01:00 (01:00 AM) |
| Sydney | Fri 18-May-2018 02:00 (02:00 AM) |

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Community%20Committee+Meeting+2018-05-17&iso=20180517T16
• or http://www.wolframalpha.com/input/?i=04PM+UTC%2C+May+17%2C+2018+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1ynEM_MM9-K9EyWvC7avSplLHd7I73zNjSkXY7kwBySA/edit

Agenda

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

nodejs/mentorship

• "Priority Document" outlining areas of greatest need for Node.js ecosystem #38
• We need more active members of the WG #32
• Set a Code of Conduct for mentors and mentees #31
• Create a mentorship subgroup focused on to identify 6 month projects in Node.js #30

nodejs/node

• readme: add link to unofficial discord #20508

nodejs/community-committee

• Record and serve the meetings in audio format #232

nodejs/user-feedback

• 2018-04-27 Public User Feedback Meeting - Enterprise Use Case #52

nodejs/website-redesign

• Node.js Extended Color Palette #42

Invited

• CommComm Members: @nodejs/community-committee

Observers

• @DiegoZoracKy (Diego ZoracKy - observer)
• @ZibbyKeaton (Zibby Keaton - observer)
• @Bamieh (Ahmad Bamieh - observer)
• @pchrysa (Chrysa - observer)
• @foadlab (observer)
• @codeekage (Abraham Agiri - observer)
• @Voskan (Voskan Voskanyan - observer)
• @waleedashraf (Waleed Ashraf - observer)
• @maddhruv (Dhruv Jain - observer)
• @elainechan (Elaine Chan - 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

• link for participants: Will be added a few minutes before meeting starts
• For those who just want to watch:
• youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

[ZibbyKeaton]

@bnb and @mhdawson the Node.js Foundation will be releasing data from our 2018 survey on May 31, and we would like to present details on the survey findings and what we are doing with the CommComm team. I'll be OOO, but @SarahKConway and @gtewallace would like to present. Is there room to have us on the agenda for Thursday? Thanks in advance for your guidance here.

[mhdawson]

@ZibbyKeaton I'll let @bnb answer for the commcomm meeting but I'm wondering if you want to get on the TSC agenda as well. If so would it be possible this week on Wednesday? I'm guessing it might be in the private section as it will be covering data in advance?

[ZibbyKeaton]

@mhdawson checking in with Sarah and Greg to see if they will be available. I think private meeting for the TSC will be better given that we are wanting to keep the data under NDA until May 31 as we will be sharing this information with media. Is there a private meeting with CommComm as well - if not, we can go over some high level items and general plan, so folks are in the know and can ask questions.

[keywordnew]

@ZibbyKeaton if you have it, could be helpful to know how much time @SarahKConway and @gtewallace would like set aside for a presentation during the CommComm meeting 💛

Regarding private meetings, the bulk of the regular meeting is public; but, time permitting, the part at the end is typically set aside for the discussion of issues meant to be private.

Speaking for myself, I would def like to know the details on the survey findings.

[SarahKConway]

Want to make sure there is also plenty of time for feedback and questions from CommComm. Around 20-30 min. should work. Will that work?

[bnb]

As long as there are no objections to it being in the meeting, I don't see why not. It would be stellar if we could time box it to 20 minutes, as we do have something that we need to discuss in the private session anyway.

I'd like to also suggest that we prioritize nodejs/mentorship above all else in the public meeting, since we've tabled their agenda issues a few times now.

[keywordnew]

(Moving nodejs/mentorship items to the top of the agenda in original issue comment and minutes doc)

[keywordnew]

Happy to have you both join us for the meeting @SarahKConway and @gtewallace 🙂

[rachelnicole]

I can make it again finally!

[bnb]

Going to kick the meeting off in a second, there's another meeting and I don't want to cut them off early (@mhdawson is in it and is aware of the CommComm meeting).

[keywordnew]

Thursday is just chock full of meetings

[SarahKConway]

@bnb can you please share zoom link again? I am having trouble launching it.

[bnb]

https://zoom.us/j/193588946

[detrohutt]

I apologize for missing the meeting. I wasn't aware my document was on the agenda. :(