-
Notifications
You must be signed in to change notification settings - Fork 70
Node.js Foundation Community Committee (CommComm) Meeting 2017-07-06 #87
Comments
got my name wrong again! 😉 |
Sorry to drive it further, but mine as well for the issue title ( |
Sorry about that everyone, names should be fixed now. |
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. |
I'm getting a you are not authorized to start this video call. Is it just me ? |
We decided to cancel re: #91 but we probably should have closed this issue too to notify. Oops! |
This is the 7-6 meeting 🤔 There doesn't seem to be one for this week? |
@williamkapke See: #91 (which Jenn linked above) |
this should be closed anyways since the meeting notes are merged in |
Node.js Foundation Community Committee (CommComm) Meeting 2017-07-06
Time
UTC Thu 06-Jul-2017 20:30 (08:30 PM):
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
nodejs/community-committee
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.
The text was updated successfully, but these errors were encountered: