Additional org owned by Node.js project for package maintenance team
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
In the context of https://github.com/nodejs/package-maintenance/issues/271
The package maintenance team is exploring how to host tools being developed.
The team does not want to use a repo in the nodejs or due to concerns that might make them look officially supported by the Node.js project and put other tools at a disadvantage.
At the same time the team would like to leverage existing governance, moderation that comes with a repo that is part of the Node.js org.
The ask is whether the TSC/CommComm would consider:
Can the Node.js Project can 'own' and additional repo, with the TSC delegating management of it to the Package-maintenance team and ask that things like moderation be extended to this new org.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading package-maintenance issue #271 and the governance context for the TSC and CommComm. Review the request for an additional Node.js-owned organization or repository and delegated management by the Package-maintenance team. Done means a recorded decision on whether the proposed ownership and moderation arrangement is acceptable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100