sunset/remove the documentation team?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
I haven't encountered anyone from the Documentation team or interacted with any of them. The current API Docs are basically managed by the Website Team and the Next-10 WG. (And the contents actually by the Node.js core-collaborators).
The documentation team also doesn't own any specific repository that is active. Hence, it probably can be archived? (https://github.com/orgs/nodejs/teams/documentation/)
cc @nodejs/tsc
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 with the Documentation team page linked in the issue and review the API Docs ownership described in the issue, including the Website Team, Next-10 WG, and core-collaborators. Confirm the current team status and any TSC follow-up; done means the team’s future is decided and the relevant organization change is completed or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100