Skip to content

Commit 7f8dd00

Browse files
authored
Merge pull request #212 from loopbackio/coc2
docs: update coc
2 parents c4f0e27 + f989c2f commit 7f8dd00

File tree

1 file changed

+52
-2
lines changed

1 file changed

+52
-2
lines changed

CODE_OF_CONDUCT.md

+52-2
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,54 @@
1-
# Contributor Covenant Code of Conduct
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+
`[email protected]`. 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+
`[email protected]`. 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+
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
252

353
## Our Pledge
454

@@ -125,4 +175,4 @@ Community Impact Guidelines were inspired by
125175

126176
For answers to common questions about this code of conduct, see the FAQ at
127177
https://www.contributor-covenant.org/faq. Translations are available at
128-
https://www.contributor-covenant.org/translations.
178+
https://www.contributor-covenant.org/translations.

0 commit comments

Comments
 (0)