Skip to content
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 Package Maintenance Team Meeting 2020-08-11 #394

Closed
mhdawson opened this issue Aug 5, 2020 · 12 comments
Closed

Node.js Package Maintenance Team Meeting 2020-08-11 #394

mhdawson opened this issue Aug 5, 2020 · 12 comments
Assignees

Comments

@mhdawson
Copy link
Member

mhdawson commented Aug 5, 2020

Time

UTC Tue 11-Aug-2020 13:00 (01:00 PM):

Timezone Date/Time
US / Pacific Tue 11-Aug-2020 06:00 (06:00 AM)
US / Mountain Tue 11-Aug-2020 07:00 (07:00 AM)
US / Central Tue 11-Aug-2020 08:00 (08:00 AM)
US / Eastern Tue 11-Aug-2020 09:00 (09:00 AM)
London Tue 11-Aug-2020 14:00 (02:00 PM)
Amsterdam Tue 11-Aug-2020 15:00 (03:00 PM)
Moscow Tue 11-Aug-2020 16:00 (04:00 PM)
Chennai Tue 11-Aug-2020 18:30 (06:30 PM)
Hangzhou Tue 11-Aug-2020 21:00 (09:00 PM)
Tokyo Tue 11-Aug-2020 22:00 (10:00 PM)
Sydney Tue 11-Aug-2020 23:00 (11:00 PM)

Or in your local time:

Links

Agenda

Extracted from package-maintenance-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/package-maintenance

  • Communicating that only the latest version of a major release line is supported #393
  • Suggest ignoring a vulnerability by the package maintainer #386
  • PkgJS Org for WG supported tooling #271
  • Next steps on Support levels in Package.json #192

Invited

  • Package Maintenance team: @nodejs/package-maintenance

Observers/Guests

Notes

The agenda comes from issues labelled with package-maintenance-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 Aug 5, 2020
@thescientist13
Copy link
Contributor

Have some conflicts for work at this time, likely won't be able to join.

@rodion-arr
Copy link
Contributor

I won't be able to join also.. 😔

@mhdawson
Copy link
Member Author

I just found out that I won't be able to make it as there in an IBM internal meeting I have to make. I should be able to start the zoom in advance and then make somebody else the owner. Is there a volunteer to chair. @nodejs/package-maintenance

@dominykas
Copy link
Member

Looks like I'm unable to attend as well.

@dominykas
Copy link
Member

Scratch that, the conflicting meeting got cancelled, so I'll be there - not sure who else will be there?

@BethGriggs
Copy link
Member

I'm unable to make it too, I have an unavoidable clash.

@styfle
Copy link
Member

styfle commented Aug 11, 2020

I have a conflict as well 😬

@ghinks
Copy link
Contributor

ghinks commented Aug 11, 2020

Apologies conflicts at this time

@dominykas
Copy link
Member

dominykas commented Aug 11, 2020

I think we may as well skip this one?

Or I can sit there and talk to myself and broadcast that to Youtube 🤔

@mhdawson
Copy link
Member Author

We were going to talk about #386 with @lirantal and @darcyclarke but sounds like we should try to reschedule that to next week.

@wesleytodd
Copy link
Member

Yeah, if that many people cannot attend, I think a reschedule is in order. I also think we could consider just moving to the later time for today. Would that work better for anyone?

@wesleytodd
Copy link
Member

We are just recording our quick discussion so that Darcy has a chance to give some thoughts. If anyone does want to join.

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

No branches or pull requests

8 participants