-
Notifications
You must be signed in to change notification settings - Fork 70
Node.js Foundation Community Committee Meeting 2020-02-06 #578
Comments
I have to leave a bit early tomorrow. I'll be thankful if we can discuss "nodejs/nodejs-collection - Update readme with new process nodejs/nodejs-collection#37" issue in start of the meeting. |
I'll be away; traveling during the meeting so I won't be able to make it this time. |
I'll be there! Currently in recovery (so no video sorry b/c I look terrible atm), but I'm stoked to hang with y'all! 🙌 |
Quick update on the Social Media agenda item: per @mhdawson's suggestion of having a POC, I'm working with Electron to set up twitter-together for their twitter account. I will be following up on the PR we discussed last time once I have that set up :) |
Starting the meeting. Correction: I'm not able to, when signing in with the Zoom account to which I have access. |
Im trying to start the meeting..... |
Thanks @joesepi |
I dont know why it is a different url than meeting notes |
old meeting expired |
I went in to update it but the one I copy/pasted was the same so I didn't change it at all because I thought it was updated at the source 😬 |
Time
UTC Thu 06-Feb-2020 17:00 (05:00 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/admin
nodejs/community-committee
nodejs/nodejs-collection
nodejs/mentorship
Invited
Observers/Guests
Feel free to follow along on the YouTube live stream, or attend meeting as a guest
by calling in to Zoom, using the links below. If you will be attending as a guest,
please comment on this issue to let us know you'll be joining.
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
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: