Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Node.js Foundation Community Committee (CommComm) Meeting 2017-04-27 #36

Closed
nebrius opened this issue Apr 25, 2017 · 20 comments
Closed

Comments

@nebrius
Copy link
Contributor

nebrius commented Apr 25, 2017

Meeting 2017-04-27Community Committee (CommComm)

Time

UTC Thu 27-Apr-2017 20:30 (08:30 PM):

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

  • Clarify By-Laws WRT Community Committee #57

nodejs/community-committee

  • Moderation shortage #33
  • 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
  • Adding folks as members #38

Invited

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

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.

@nebrius
Copy link
Contributor Author

nebrius commented Apr 25, 2017

Note: I don't think we've updating any labels since the last meeting. Everyone please review the agenda and update cc-agenda labels as appropriate.

@hackygolucky
Copy link
Contributor

@nebrius as stated in #25, can we move this 30 minutes later? We didn't get any objections to this and the Node.js Foundation has a weekly meeting that conflicts with this.

@nebrius
Copy link
Contributor Author

nebrius commented Apr 25, 2017

Whoops, sorry, I forgot to update it (meeting times are embedded in the creation tool). Done!

@hackygolucky
Copy link
Contributor

hackygolucky commented Apr 25, 2017 via email

@MylesBorins
Copy link
Contributor

MylesBorins commented Apr 25, 2017 via email

@rachelnicole
Copy link
Contributor

commenting to remind myself not to forget -_-

@williamkapke
Copy link
Contributor

Hm. I remember objections to NOT matching the TSC time. @hackygolucky you said you see if they could move the Foundation meeting.

@williamkapke
Copy link
Contributor

I unfortunately cannot make it today. I will listen to the recording later (please record it!)

PS: @rachelnicole Here's another reminder for you. 😆

@williamkapke
Copy link
Contributor

Also- it looks like there this meeting now overlaps the @nodejs/diagnostics meeting. You may be blocking the YouTube live stream.

@addaleax
Copy link
Member

@williamkapke just fyi, looking at nodejs/diagnostics#94 it doesn’t seem like that is going to be a problem today

@jasnell
Copy link
Member

jasnell commented Apr 27, 2017

is there a participation link? :-)

@hackygolucky
Copy link
Contributor

here! sorry was just getting it @jasnell https://hangouts.google.com/hangouts/_/6sctyenduffjhkqgcgfd6pd4nee

@rachelnicole
Copy link
Contributor

My flight is super delayed and I don't think I'm going to be able to make the call :(

@hackygolucky
Copy link
Contributor

hackygolucky commented Apr 27, 2017

We did not broadcast the meeting due to a lack of quorum, but we did take discussion notes. A few issues will be filed and we'll revisit this week's agenda at the next meeting! We had a lot of folks up in the air(literally).

@msmichellegar
Copy link

Sorry to miss it! I'll catch up with the notes.

@hackygolucky
Copy link
Contributor

@msmichellegar no worries! We're going to try and adjust the time to be a little friendlier to y'all in the EU.

@Fishrock123
Copy link

Note: CTC and TSC meetings often do not have quorum, was there an actual meeting? It should still be broadcast-able then unless there was no public agenda items?

@hackygolucky
Copy link
Contributor

@Fishrock123 There were 4 people who showed, and we discussed whether we should record because no decisions could be made and we didn't think 4 people was representative enough to have proper feedback. We took the discussion notes but did not record, thinking it would not be helpful to do so. Thanks for this input! Good to know for the future.

@Fishrock123
Copy link

It's ok. Sometimes it's hard to know if it is "meeting-worthy" when just a few people show up. This kinda thing has come up many times for the TSC/CTC in the past too.

My general measure would be: if we were taking or were going to be taking any significant notes I'd want to broadcast, at least for TSC/CTC meetings.

@nebrius
Copy link
Contributor Author

nebrius commented May 10, 2017

This meeting has been held, so closing

@nebrius nebrius closed this as completed May 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants