{"id":13528109,"url":"https://github.com/nodejs/package-maintenance","last_synced_at":"2025-10-08T21:02:31.607Z","repository":{"id":37561596,"uuid":"158296487","full_name":"nodejs/package-maintenance","owner":"nodejs","description":"Repository for work for discussion of helping with maintenance of key packages in the ecosystem.","archived":false,"fork":false,"pushed_at":"2025-04-15T13:25:55.000Z","size":581,"stargazers_count":415,"open_issues_count":63,"forks_count":143,"subscribers_count":59,"default_branch":"main","last_synced_at":"2025-05-08T10:28:14.406Z","etag":null,"topics":["nodejs"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/nodejs.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":null,"code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"docs/security-guidelines.md","support":null,"governance":"Governance.md","roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null},"funding":{"github":"nodejs","open_collective":"nodejs"}},"created_at":"2018-11-19T22:08:40.000Z","updated_at":"2025-04-15T13:25:59.000Z","dependencies_parsed_at":"2023-02-12T04:46:11.325Z","dependency_job_id":"71073503-c504-491f-84f5-3ec036792711","html_url":"https://github.com/nodejs/package-maintenance","commit_stats":{"total_commits":447,"total_committers":130,"mean_commits":"3.4384615384615387","dds":0.767337807606264,"last_synced_commit":"af94d21ab0d37d51dbf97b76587f90f387783241"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2Fpackage-maintenance","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2Fpackage-maintenance/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2Fpackage-maintenance/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/nodejs%2Fpackage-maintenance/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/nodejs","download_url":"https://codeload.github.com/nodejs/package-maintenance/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":253815942,"owners_count":21968728,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["nodejs"],"created_at":"2024-08-01T06:02:13.129Z","updated_at":"2025-10-08T21:02:31.547Z","avatar_url":"https://github.com/nodejs.png","language":null,"readme":"# package-maintenance team\n\nRepository for discussion on how to help ensure baseline\nmaintenance and ability to safely use key packages in the\necosystem with current Node.js versions. You can find more\nabout this initiative in the article:\n[Call to Action: Accelerating Node.js Growth](https://medium.com/@nodejs/call-to-action-accelerating-node-js-growth-e4862bee2919)\n\n## Goals\n\n* Define and document how to prioritize which packages are key to the\n  Node.js ecosystem, and how/what assistance can/should be provided.\n  One key aspect is understanding what communication\n  channels are needed in order to identify when specific\n  issues are slowing migration from one Node.js version to another,\n  or causing friction in the ecosystem.\n* Building and documenting guidance, tools and processes so\n  businesses can identify the packages they depend on.\n  Businesses can use the information to build a business\n  case which supports both the organization and developers helping to\n  maintain those packages.\n* Documenting a backlog and providing resources to help\n  businesses identify how their developers can contribute, and\n  get engaged. Developers can test and validate a workflow to help\n  with issues slowing migration to Node.js 10.x.\n* Building, documenting and evangelizing guidance, tools and\n  processes (for example LTS for modules)\n  can make it easier for maintainers to manage multiple\n  streams, and accept help from those who depend on their module.\n\n## For Maintainers\n\nAre you a maintainer of an open source project looking for help and resources maintaining your package and community?  To get you started,\n- Review [our growing set of documentation](https://github.com/nodejs/package-maintenance/blob/master/docs/README.md) around topics like CI / CD, testing, and governance\n\n### Feedback\n\nWant to provide feedback on your experiences as a maintainer?  Want to let us know what topic and tools you think would be helpful to pursue within this group?  Open a PR to fill out [this survey](https://github.com/nodejs/package-maintenance/blob/master/pilots/SURVEY.md) and the team will be sure to review and get in touch with you.\n\n## Joining\n\nWe encourage participation from members across the Node.js and JavaScript\necosystem. Feel free to join schedule meetings and participate\nin the issues within the repository.\n\n## How to Join\n\nThe package-maintenance team has two levels of membership. Administrative\nmembers and regular members.\n\nIf you'd like to be listed as regular team member, open a PR adding yourself\nto this [MEMBERS.md](MEMBERS.md) along with a few words on how you are planning\nto contribute to the team's efforts.\n\nAdministrative members take on additional levels of responsibility with\nrespect to managing the [pkgjs](https://github.com/pkgjs) organization\nand the other repositories managed by the working group. Administrative\nmembers should have a long standing involvement in the working group.\n\nIndividuals who have made significant contributions and who wish to be\nconsidered as an Administrative member may create an issue or\ncontact an Administrative WG member directly. It is not necessary\nto wait for an Administrative WG member to nominate the individual.\n\nFor more details refer to the WG Governance document.\n\n## Logistics\n\n### Meetings\n\nMeetings of the working group typically occur bi-weekly as shown on the\nthe node.js project [calendar](https://nodejs.org/calendar).\nA few days before each meeting, an\n[issue](https://github.com/nodejs/package-maintenance/issues)\nwill be created with the date and time of the meeting.\nThe issue will provide schedule logistics as well as\nan agenda, links to meeting minutes, and\ninformation about how to join as a participant or a viewer.\n\n### Communications\n\nThe working group can chat on the [OpenJS slack](https://slack-invite.openjsf.org/)\nin the channel `#nodejs-package-maintenance` in order to continue conversations beyond the meetings.\nAll the contributors are expected to follow the [Code of Conduct](https://github.com/nodejs/admin/blob/master/CODE_OF_CONDUCT.md)\nof the Node.js project.\n\n## Pull Request Merging Policy\n\nThe package maintenance team policy on landing a PR in the nodejs/package-maintenance\nrepository is for there to be:\n- At least 4 approvals from regular members\n- No blocking reviews\n- 7 day period from the 4th approval to merging\n\nAll PRs shall follow the [contributions policy](CONTRIBUTING.md)\n\n## Current Project Team Members\n\n* [See the list of Administrative Members](./ADMINISTRATIVE-MEMBERS.md)\n* [See the list of Members](./MEMBERS.md)\n\n## Emeritus Project Team Members\n\n[See the list of Emeritus](./EMERITUS.md)\n","funding_links":["https://github.com/sponsors/nodejs","https://opencollective.com/nodejs"],"categories":["Others"],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnodejs%2Fpackage-maintenance","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fnodejs%2Fpackage-maintenance","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fnodejs%2Fpackage-maintenance/lists"}