You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Node.js Foundation Package Maintenance Team Meeting 2019-09-24 #259
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.
Not sure if this fits in with the package-maintenance team's goals/charter/whatever, but assistance getting things aligned in the ecosystem and Node.js 13.0.0 such that we minimize the pain of any Node.js breaking changes for end users would be 💯. Specifically, it would be great if we could get rid of as many CITGM issues there as possible.
@Trott Making this easier for maintainers in general is within this groups charter (even if specific upgrades might not be something we are equipped to handle yet). Are there specific things you think we could help with? Also, this might warrant a separate issue so we can discuss and then add to this meeting agenda if there is more to talk about.
Are there specific things you think we could help with?
I had contributing fixes in mind, but if that's not in scope, then maybe nothing much comes to mind. Perhaps just getting the word out to folks who might contribute fixes, but that can be some effort. Perhaps coordinating with @nodejs/mentorship to see if maybe this is something mentors/mentees can look at? Or @nodejs/code-and-learn?
Activity
Trott commentedon Sep 18, 2019
Not sure if this fits in with the package-maintenance team's goals/charter/whatever, but assistance getting things aligned in the ecosystem and Node.js 13.0.0 such that we minimize the pain of any Node.js breaking changes for end users would be 💯. Specifically, it would be great if we could get rid of as many CITGM issues there as possible.
wesleytodd commentedon Sep 18, 2019
@Trott Making this easier for maintainers in general is within this groups charter (even if specific upgrades might not be something we are equipped to handle yet). Are there specific things you think we could help with? Also, this might warrant a separate issue so we can discuss and then add to this meeting agenda if there is more to talk about.
Trott commentedon Sep 18, 2019
I had contributing fixes in mind, but if that's not in scope, then maybe nothing much comes to mind. Perhaps just getting the word out to folks who might contribute fixes, but that can be some effort. Perhaps coordinating with @nodejs/mentorship to see if maybe this is something mentors/mentees can look at? Or @nodejs/code-and-learn?
dominykas commentedon Sep 23, 2019
Added #244 to agenda, because its something I intend to look deeper into over the next month or so.
lholmquist commentedon Sep 24, 2019
looks like i'm going to miss this one, i'll catch up on the recording 👎
craftninja commentedon Sep 24, 2019
@mhdawson FWIW - I love the emoji respond section for attendance! I just noticed it now...
I will be missing this one but will catch up later today.
mhdawson commentedon Sep 24, 2019
PR for minutes: #262