1 | # Code of Conduct
|
2 |
|
3 | LoopBack, as member project of the OpenJS Foundation, use
|
4 | [Contributor Covenant v2.0](https://contributor-covenant.org/version/2/0/code_of_conduct)
|
5 | as their code of conduct. The full text is included
|
6 | [below](#contributor-covenant-code-of-conduct-v2.0) in English, and translations
|
7 | are available from the Contributor Covenant organisation:
|
8 |
|
9 | - [contributor-covenant.org/translations](https://www.contributor-covenant.org/translations)
|
10 | - [github.com/ContributorCovenant](https://github.com/ContributorCovenant/contributor_covenant/tree/release/content/version/2/0)
|
11 |
|
12 | Refer to the sections on reporting and escalation in this document for the
|
13 | specific emails that can be used to report and escalate issues.
|
14 |
|
15 | ## Reporting
|
16 |
|
17 | ### Project Spaces
|
18 |
|
19 | For reporting issues in spaces related to LoopBack, please use the email
|
20 | `tsc@loopback.io`. The LoopBack Technical Steering Committee (TSC) handles CoC issues related to the spaces that it
|
21 | maintains. The project TSC commits to:
|
22 |
|
23 | - maintain the confidentiality with regard to the reporter of an incident
|
24 | - to participate in the path for escalation as outlined in the section on
|
25 | Escalation when required.
|
26 |
|
27 | ### Foundation Spaces
|
28 |
|
29 | For reporting issues in spaces managed by the OpenJS Foundation, for example,
|
30 | repositories within the OpenJS organization, use the email
|
31 | `report@lists.openjsf.org`. The Cross Project Council (CPC) is responsible for
|
32 | managing these reports and commits to:
|
33 |
|
34 | - maintain the confidentiality with regard to the reporter of an incident
|
35 | - to participate in the path for escalation as outlined in the section on
|
36 | Escalation when required.
|
37 |
|
38 | ## Escalation
|
39 |
|
40 | The OpenJS Foundation maintains a Code of Conduct Panel (CoCP). This is a
|
41 | foundation-wide team established to manage escalation when a reporter believes
|
42 | that a report to a member project or the CPC has not been properly handled. In
|
43 | order to escalate to the CoCP send an email to
|
44 | `coc-escalation@lists.openjsf.org`.
|
45 |
|
46 | For more information, refer to the full
|
47 | [Code of Conduct governance document](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md).
|
48 |
|
49 | ---
|
50 |
|
51 | ## Contributor Covenant Code of Conduct v2.0
|
52 |
|
53 | ## Our Pledge
|
54 |
|
55 | We as members, contributors, and leaders pledge to make participation in our
|
56 | community a harassment-free experience for everyone, regardless of age, body
|
57 | size, visible or invisible disability, ethnicity, sex characteristics, gender
|
58 | identity and expression, level of experience, education, socio-economic status,
|
59 | nationality, personal appearance, race, religion, or sexual identity and
|
60 | orientation.
|
61 |
|
62 | We pledge to act and interact in ways that contribute to an open, welcoming,
|
63 | diverse, inclusive, and healthy community.
|
64 |
|
65 | ## Our Standards
|
66 |
|
67 | Examples of behavior that contributes to a positive environment for our
|
68 | community include:
|
69 |
|
70 | - Demonstrating empathy and kindness toward other people
|
71 | - Being respectful of differing opinions, viewpoints, and experiences
|
72 | - Giving and gracefully accepting constructive feedback
|
73 | - Accepting responsibility and apologizing to those affected by our mistakes,
|
74 | and learning from the experience
|
75 | - Focusing on what is best not just for us as individuals, but for the overall
|
76 | community
|
77 |
|
78 | Examples of unacceptable behavior include:
|
79 |
|
80 | - The use of sexualized language or imagery, and sexual attention or advances of
|
81 | any kind
|
82 | - Trolling, insulting or derogatory comments, and personal or political attacks
|
83 | - Public or private harassment
|
84 | - Publishing others' private information, such as a physical or email address,
|
85 | without their explicit permission
|
86 | - Other conduct which could reasonably be considered inappropriate in a
|
87 | professional setting
|
88 |
|
89 | ## Enforcement Responsibilities
|
90 |
|
91 | Community leaders are responsible for clarifying and enforcing our standards of
|
92 | acceptable behavior and will take appropriate and fair corrective action in
|
93 | response to any behavior that they deem inappropriate, threatening, offensive,
|
94 | or harmful.
|
95 |
|
96 | Community leaders have the right and responsibility to remove, edit, or reject
|
97 | comments, commits, code, wiki edits, issues, and other contributions that are
|
98 | not aligned to this Code of Conduct, and will communicate reasons for moderation
|
99 | decisions when appropriate.
|
100 |
|
101 | ## Scope
|
102 |
|
103 | This Code of Conduct applies within all community spaces, and also applies when
|
104 | an individual is officially representing the community in public spaces.
|
105 | Examples of representing our community include using an official e-mail address,
|
106 | posting via an official social media account, or acting as an appointed
|
107 | representative at an online or offline event.
|
108 |
|
109 | ## Enforcement
|
110 |
|
111 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
112 | reported to the community leaders responsible for enforcement at
|
113 | [tsc@loopback.io](mailto:tsc@loopback.io). All complaints will be reviewed and
|
114 | investigated promptly and fairly.
|
115 |
|
116 | All community leaders are obligated to respect the privacy and security of the
|
117 | reporter of any incident.
|
118 |
|
119 | ## Enforcement Guidelines
|
120 |
|
121 | Community leaders will follow these Community Impact Guidelines in determining
|
122 | the consequences for any action they deem in violation of this Code of Conduct:
|
123 |
|
124 | ### 1. Correction
|
125 |
|
126 | **Community Impact**: Use of inappropriate language or other behavior deemed
|
127 | unprofessional or unwelcome in the community.
|
128 |
|
129 | **Consequence**: A private, written warning from community leaders, providing
|
130 | clarity around the nature of the violation and an explanation of why the
|
131 | behavior was inappropriate. A public apology may be requested.
|
132 |
|
133 | ### 2. Warning
|
134 |
|
135 | **Community Impact**: A violation through a single incident or series of
|
136 | actions.
|
137 |
|
138 | **Consequence**: A warning with consequences for continued behavior. No
|
139 | interaction with the people involved, including unsolicited interaction with
|
140 | those enforcing the Code of Conduct, for a specified period of time. This
|
141 | includes avoiding interactions in community spaces as well as external channels
|
142 | like social media. Violating these terms may lead to a temporary or permanent
|
143 | ban.
|
144 |
|
145 | ### 3. Temporary Ban
|
146 |
|
147 | **Community Impact**: A serious violation of community standards, including
|
148 | sustained inappropriate behavior.
|
149 |
|
150 | **Consequence**: A temporary ban from any sort of interaction or public
|
151 | communication with the community for a specified period of time. No public or
|
152 | private interaction with the people involved, including unsolicited interaction
|
153 | with those enforcing the Code of Conduct, is allowed during this period.
|
154 | Violating these terms may lead to a permanent ban.
|
155 |
|
156 | ### 4. Permanent Ban
|
157 |
|
158 | **Community Impact**: Demonstrating a pattern of violation of community
|
159 | standards, including sustained inappropriate behavior, harassment of an
|
160 | individual, or aggression toward or disparagement of classes of individuals.
|
161 |
|
162 | **Consequence**: A permanent ban from any sort of public interaction within the
|
163 | community.
|
164 |
|
165 | ## Attribution
|
166 |
|
167 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
168 | version 2.0, available at
|
169 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
|
170 |
|
171 | Community Impact Guidelines were inspired by
|
172 | [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
|
173 |
|
174 | [homepage]: https://www.contributor-covenant.org
|
175 |
|
176 | For answers to common questions about this code of conduct, see the FAQ at
|
177 | https://www.contributor-covenant.org/faq. Translations are available at
|
178 | https://www.contributor-covenant.org/translations.
|