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 2019-02-21 #452

Closed
mhdawson opened this issue Feb 18, 2019 · 14 comments
Closed

Node.js Foundation Community Committee Meeting 2019-02-21 #452

mhdawson opened this issue Feb 18, 2019 · 14 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Feb 18, 2019

Time

UTC Thu 21-Feb-2019 17:00 (05:00 PM):

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

  • Discuss Collab Summit Progress #448
  • Kicking Off “Working Group Update” Blog Series #435
  • Individual Membership Subgroup – Next Steps #423
  • Individual Membership: Current and Past Members Survey #375
  • Strategic Initiative for Broader Node.js Community #435

nodejs/outreach

  • Call for help #4

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

@mhdawson mhdawson self-assigned this Feb 18, 2019
@Tiriel
Copy link
Contributor

Tiriel commented Feb 19, 2019

Hey!

If it's ok for everyone, I'd like to discuss or at least mention the brand new Outreach call for help

Do you think there's a need for an issue here as well?
Any input would be welcome!

@keywordnew
Copy link
Contributor

@Tiriel multiple issues likely not needed at this stage but feel free to label the original issue cc-agenda :)

Side note, really stoked you're back! Welcome!

@keywordnew
Copy link
Contributor

I'm requesting a private session as part of the meeting.

@celyes
Copy link

celyes commented Feb 20, 2019

excited to watch it live
@Aissaoui-Ahmed we won't miss this meeting, right?

@Tiriel
Copy link
Contributor

Tiriel commented Feb 20, 2019

@keywordnew Thanks a lot, feels good to be back!

No new issue then, I don't think there's need yet, although it might come to it to get some advertising.

As for the label, funnily enough I'm only member of the outreach repo, so I can't label issues. If you have these permissions, I'll be glad to have it tagged for me! But I think @hackygolucky might be the only admin iirc (except org admins).

@codeekage
Copy link
Contributor

@nodejs/community-committee can I add a cc-agenda label for #453 ?

@amiller-gh
Copy link
Member

Hey all! Just a heads up that we’ll be starting this meeting with a private session for members only. We’ll kick off the public stream and conduct business as usual after the discussion if there is enough time 👍

@codeekage, @Tiriel, issues noted 🙂

@ahmadawais
Copy link
Member

ahmadawais commented Feb 21, 2019

👋 folks!

If you will be attending as a guest, please comment on this issue to let us know you'll be joining.

Looking forward to contributing more in the Community Committee team and will be joining this meeting as a guest viewer.

TO DO: Would also love to discuss the new formatting rules for the @nodejs/nodejs.dev repo nodejs/nodejs.dev#90 and would like to help format the entire code-base + review PRs for conflicts.

Peace! ✌️

@Tiriel
Copy link
Contributor

Tiriel commented Feb 21, 2019

Hey all, due to last minute private events, I may be late. I'll try to catch up asap!

@amiller-gh
Copy link
Member

Glad to have you following along with CommComm @ahmadawais! And very excited to have you contributing in @nodejs/nodejs.dev 🙂 Make sure you also follow along in @nodejs/website-redesign, the admin repo for nodejs.dev and other redesign efforts, and feel free to join in on those meetings every other week as well! As mentioned above, the first half of this week's meeting will be private, but – unless the private business takes the entire time – you should see the YouTube stream start halfway through, and a comment added here announcing the start of the public session 👍

@ahmadawais
Copy link
Member

Thank you for the welcome and explaining all that @amiller-gh 🙌

I'm already watching the repo and have started contributing to the current phase of @nodejs/website-redesign. Learning the ropes as I go about how you folks do it here. Every open source community is a bit different (at WordPress Core we do it via Slack). Bound to make some silly mistakes here and there (like joining in on the private meeting now hahaha! 🤣).

@celyes
Copy link

celyes commented Feb 21, 2019

Hey all! Just a heads up that we’ll be starting this meeting with a private session for members only. We’ll kick off the public stream and conduct business as usual after the discussion if there is enough time 👍

@codeekage, @Tiriel, issues noted 🙂

@Aissaoui-Ahmed

@amiller-gh
Copy link
Member

👋Private session is still on-going and looks like it may take the entire session time 🙏 This happens very rarely I swear! (You chose a good week to pop in for the first time 😜 ) We'll be back to normal process next meeting and are happy to have you 🎉

@Tiriel
Copy link
Contributor

Tiriel commented Feb 21, 2019

Sorry everyone, I just got home, will catch up privately :(

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

7 participants