nodejs / nodejs/package-maintenance

Meeting: Whats next for PMWG?

Open
#641 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
423
Forks
147
PR merge metrics
No merged PRs in 30d

Description

Hey @nodejs/package-maintenance friends!

This group has evolved a lot since it was started. I think it is time we discuss how to restructure things for the future. I have lots of ideas, and will try to post some of them before the meeting, but wanted to get a poll out to see if folks are able to make an early December time.

https://calendly.com/d/cw5z-nxk-b9r/the-future-of-the-pmwg

Some initial ideas for topics:

  • Prune the team members to match our members document
  • Is the scope of the group still good?
  • How can we better enable progress in https://github.com/pkgjs?
  • Is there a more loose PR approval process we could use since we are generally less active?
  • Can we work better with folks publishing packages on the Node.js scope as a whole?
  • ...

In the interest of not pinging too many people, I just ping'd our team. BUT, I also think there are a lot of folks around the project who have popped in at one time or another, so feel free to ping in folks you think might be interested in helping get this group ready for whats next.


Meeting has been scheduled for next Wednesday Dec 10th 21:00 GMT. Link: https://zoom-lfx.platform.linuxfoundation.org/meeting/93676278959?password=21b3d698-46b9-45e6-af5f-78d63984a463

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the members document and the proposed discussion topics in the issue, including PMWG scope, pkgjs progress, PR approval, and Node.js package publishing. The issue does not name a code entry point; done would require an agreed restructuring plan and documented follow-up actions from the meeting.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.