nodejs / nodejs/package-maintenance
[docs] code of conduct (new)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
In #333 a Table of Contents was added for helping readers and maintainers with organizing content within the docs/ folder.
In that ToC was added a new section for documenting guidelines for effectively creating a good Code of Conduct for a project, as well as including references and examples to showcase, like for NodeJS or this repository itself.
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 reviewing issue #333 and the Table of Contents for the docs/ folder to locate the new section. Add guidance for creating an effective Code of Conduct, including the references and examples described in this issue; done means the section is present and organized in the documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100