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 Meeting 2020-02-06 #578

Closed
mhdawson opened this issue Feb 3, 2020 · 13 comments · Fixed by #580
Closed

Node.js Foundation Community Committee Meeting 2020-02-06 #578

mhdawson opened this issue Feb 3, 2020 · 13 comments · Fixed by #580
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Feb 3, 2020

Time

UTC Thu 06-Feb-2020 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Thu 06-Feb-2020 09:00 (09:00 AM)
US / Mountain Thu 06-Feb-2020 10:00 (10:00 AM)
US / Central Thu 06-Feb-2020 11:00 (11:00 AM)
US / Eastern Thu 06-Feb-2020 12:00 (12:00 PM)
London Thu 06-Feb-2020 17:00 (05:00 PM)
Amsterdam Thu 06-Feb-2020 18:00 (06:00 PM)
Moscow Thu 06-Feb-2020 20:00 (08:00 PM)
Chennai Thu 06-Feb-2020 22:30 (10:30 PM)
Hangzhou Fri 07-Feb-2020 01:00 (01:00 AM)
Tokyo Fri 07-Feb-2020 02:00 (02:00 AM)
Sydney Fri 07-Feb-2020 04:00 (04:00 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/admin

  • Node.js Social Media Accounts #454

nodejs/community-committee

nodejs/nodejs-collection

  • Update readme with new process #37

nodejs/mentorship

  • Mentorship Program - Add License #183

Invited

  • CommComm Members: @nodejs/community-committee

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.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure yet
@mhdawson mhdawson self-assigned this Feb 3, 2020
@WaleedAshraf
Copy link
Contributor

WaleedAshraf commented Feb 5, 2020

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

@ahmadawais
Copy link
Member

ahmadawais commented Feb 5, 2020

I'll be away; traveling during the meeting so I won't be able to make it this time.

@obensource
Copy link
Member

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! 🙌

@bnb
Copy link
Contributor

bnb commented Feb 6, 2020

I am not going to be able to make it today. Giving a presentation and it was moved up into the middle of the CommComm Meeting. @mhdawson or @joesepi would one of you be able to run the meeting?

@bnb
Copy link
Contributor

bnb commented Feb 6, 2020

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 :)

@keywordnew
Copy link
Contributor

keywordnew commented Feb 6, 2020

Starting the meeting.

Correction: I'm not able to, when signing in with the Zoom account to which I have access.

@joesepi
Copy link
Member

joesepi commented Feb 6, 2020

Im trying to start the meeting.....

@obensource
Copy link
Member

Thanks @joesepi

@joesepi
Copy link
Member

joesepi commented Feb 6, 2020

https://zoom.us/s/193588946

@joesepi
Copy link
Member

joesepi commented Feb 6, 2020

I dont know why it is a different url than meeting notes

@bnb
Copy link
Contributor

bnb commented Feb 6, 2020

old meeting expired

@bnb
Copy link
Contributor

bnb commented Feb 6, 2020

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 😬

@WaleedAshraf
Copy link
Contributor

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants