New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node.js Foundation Community Committee (CommComm) Meeting 2017-07-06 #87

Closed
nebrius opened this Issue Jul 5, 2017 · 11 comments

Comments

Projects
None yet
6 participants
@nebrius
Contributor

nebrius commented Jul 5, 2017

Node.js Foundation Community Committee (CommComm) Meeting 2017-07-06

Time

UTC Thu 06-Jul-2017 20:30 (08:30 PM):

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

  • Candidate "areas" for TSC and Community Committee #278
  • meta: moderation policy updates #276

nodejs/community-committee

  • Adding Jenn, Tierney, Michael, Olivia, and Richard as members #77

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 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.

@oe

This comment has been minimized.

Show comment
Hide comment
@oe

oe Jul 5, 2017

Contributor

got my name wrong again! 😉

Contributor

oe commented Jul 5, 2017

got my name wrong again! 😉

@bnb

This comment has been minimized.

Show comment
Hide comment
@bnb

bnb Jul 5, 2017

Member

Sorry to drive it further, but mine as well for the issue title (Adding Jenn, Tierny, Michael, Olivia, and Richard as members #77) 😅

Member

bnb commented Jul 5, 2017

Sorry to drive it further, but mine as well for the issue title (Adding Jenn, Tierny, Michael, Olivia, and Richard as members #77) 😅

@nebrius

This comment has been minimized.

Show comment
Hide comment
@nebrius

nebrius Jul 5, 2017

Contributor

Sorry about that everyone, names should be fixed now.

Contributor

nebrius commented Jul 5, 2017

Sorry about that everyone, names should be fixed now.

@bnb

This comment has been minimized.

Show comment
Hide comment
@bnb

bnb Jul 5, 2017

Member

Add this issue? I'd like to discuss what next steps are to get it moved + next steps in the CommComm are 😄

#86

Member

bnb commented Jul 5, 2017

Add this issue? I'd like to discuss what next steps are to get it moved + next steps in the CommComm are 😄

#86

@nebrius

This comment has been minimized.

Show comment
Hide comment
@nebrius

nebrius Jul 5, 2017

Contributor

Add this issue? I'd like to discuss what next steps are to get it moved + next steps in the CommComm are.

Let's wait on this. The next step is for the CTC to sign off on the move. We're effectively blocked until they sign off, but hopefully we'll have sign off by the 7/20 meeting, and we can put it on the agenda then.

Contributor

nebrius commented Jul 5, 2017

Add this issue? I'd like to discuss what next steps are to get it moved + next steps in the CommComm are.

Let's wait on this. The next step is for the CTC to sign off on the move. We're effectively blocked until they sign off, but hopefully we'll have sign off by the 7/20 meeting, and we can put it on the agenda then.

@nebrius

This comment has been minimized.

Show comment
Hide comment
@mhdawson

This comment has been minimized.

Show comment
Hide comment
@mhdawson

mhdawson Jul 20, 2017

Member

I'm getting a you are not authorized to start this video call. Is it just me ?

Member

mhdawson commented Jul 20, 2017

I'm getting a you are not authorized to start this video call. Is it just me ?

@renrutnnej

This comment has been minimized.

Show comment
Hide comment
@renrutnnej

renrutnnej Jul 20, 2017

Contributor

We decided to cancel re: #91 but we probably should have closed this issue too to notify. Oops!

Contributor

renrutnnej commented Jul 20, 2017

We decided to cancel re: #91 but we probably should have closed this issue too to notify. Oops!

@williamkapke

This comment has been minimized.

Show comment
Hide comment
@williamkapke

williamkapke Jul 20, 2017

Member

This is the 7-6 meeting 🤔

There doesn't seem to be one for this week?

Member

williamkapke commented Jul 20, 2017

This is the 7-6 meeting 🤔

There doesn't seem to be one for this week?

@bnb

This comment has been minimized.

Show comment
Hide comment
@bnb

bnb Jul 20, 2017

Member

@williamkapke See: #91 (which Jenn linked above)

Member

bnb commented Jul 20, 2017

@williamkapke See: #91 (which Jenn linked above)

@oe

This comment has been minimized.

Show comment
Hide comment
@oe

oe Jul 21, 2017

Contributor

this should be closed anyways since the meeting notes are merged in

Contributor

oe commented Jul 21, 2017

this should be closed anyways since the meeting notes are merged in

@oe oe closed this Jul 21, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment