Skip to content

Commit 87f3790

Browse files
committed
[meta] add CODE_OF_CONDUCT.md
1 parent 7f6c0c0 commit 87f3790

File tree

1 file changed

+106
-0
lines changed

1 file changed

+106
-0
lines changed

Diff for: CODE_OF_CONDUCT.md

+106
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
1+
# Code of Conduct
2+
3+
`nvm`, as a member project of the OpenJS Foundation, uses [Contributor Covenant v1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct) as their code of conduct. The full text is included [below](#contributor-covenant-code-of-conduct) in English, and translations are available from the Contributor Covenant organisation:
4+
5+
- [contributor-covenant.org/translations](https://www.contributor-covenant.org/translations)
6+
- [github.com/ContributorCovenant](https://github.com/ContributorCovenant/contributor_covenant/tree/release/content/version/1/4)
7+
8+
Refer to the sections on reporting and escalation in this document for the specific emails that can be used to report and escalate issues.
9+
10+
## Reporting
11+
12+
### Project Spaces
13+
14+
For reporting issues in spaces related to `nvm` please use the email `[email protected]`. `nvm` handles CoC issues related to the spaces that it maintains. Projects maintainers commit to:
15+
16+
- maintain the confidentiality with regard to the reporter of an incident
17+
- to participate in the path for escalation as outlined in
18+
the section on Escalation when required.
19+
20+
### Foundation Spaces
21+
22+
For reporting issues in spaces managed by the OpenJS Foundation, for example, repositories within the OpenJS organization, use the email `[email protected]`. The Cross Project Council (CPC) is responsible for managing these reports and commits to:
23+
24+
- maintain the confidentiality with regard to the reporter of an incident
25+
- to participate in the path for escalation as outlined in
26+
the section on Escalation when required.
27+
28+
## Escalation
29+
30+
The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a foundation-wide team established to manage escalation when a reporter believes that a report to a member project or the CPC has not been properly handled. In order to escalate to the CoCP send an email to `[email protected]`.
31+
32+
For more information, refer to the full [Code of Conduct governance document](https://github.com/openjs-foundation/cross-project-council/blob/master/CODE_OF_CONDUCT.md).
33+
34+
---
35+
36+
## Contributor Covenant Code of Conduct
37+
38+
### Our Pledge
39+
40+
In the interest of fostering an open and welcoming environment, we as
41+
contributors and maintainers pledge to making participation in our project and
42+
our community a harassment-free experience for everyone, regardless of age, body
43+
size, disability, ethnicity, gender identity and expression, level of experience,
44+
nationality, personal appearance, race, religion, or sexual identity and
45+
orientation.
46+
47+
### Our Standards
48+
49+
Examples of behavior that contributes to creating a positive environment include:
50+
51+
* Using welcoming and inclusive language
52+
* Being respectful of differing viewpoints and experiences
53+
* Gracefully accepting constructive criticism
54+
* Focusing on what is best for the community
55+
* Showing empathy towards other community members
56+
57+
Examples of unacceptable behavior by participants include:
58+
59+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
60+
* Trolling, insulting/derogatory comments, and personal or political attacks
61+
* Public or private harassment
62+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
63+
* Other conduct which could reasonably be considered inappropriate in a professional setting
64+
65+
### Our Responsibilities
66+
67+
Project maintainers are responsible for clarifying the standards of acceptable
68+
behavior and are expected to take appropriate and fair corrective action in
69+
response to any instances of unacceptable behavior.
70+
71+
Project maintainers have the right and responsibility to remove, edit, or
72+
reject comments, commits, code, wiki edits, issues, and other contributions
73+
that are not aligned to this Code of Conduct, or to ban temporarily or
74+
permanently any contributor for other behaviors that they deem inappropriate,
75+
threatening, offensive, or harmful.
76+
77+
### Scope
78+
79+
This Code of Conduct applies both within project spaces and in public spaces
80+
when an individual is representing the project or its community. Examples of
81+
representing a project or community include using an official project e-mail
82+
address, posting via an official social media account, or acting as an appointed
83+
representative at an online or offline event. Representation of a project may be
84+
further defined and clarified by project maintainers.
85+
86+
### Enforcement
87+
88+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
89+
reported by contacting the project team at the email addresses listed above in
90+
the [Reporting](#reporting) and [Escalation](#escalation) sections. All
91+
complaints will be reviewed and investigated and will result in a response that
92+
is deemed necessary and appropriate to the circumstances. The project team is
93+
obligated to maintain confidentiality with regard to the reporter of an
94+
incident. Further details of specific enforcement policies may be posted
95+
separately.
96+
97+
Project maintainers who do not follow or enforce the Code of Conduct in good
98+
faith may face temporary or permanent repercussions as determined by other
99+
members of the project's leadership.
100+
101+
## Attribution
102+
103+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
104+
available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct/](https://www.contributor-covenant.org/version/1/4/code-of-conduct/)
105+
106+
[homepage]: https://www.contributor-covenant.org

0 commit comments

Comments
 (0)