-
Notifications
You must be signed in to change notification settings - Fork 363
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Diana Lau <[email protected]>
- Loading branch information
Showing
1 changed file
with
52 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,54 @@ | ||
# Contributor Covenant Code of Conduct | ||
# Code of Conduct | ||
|
||
LoopBack, as member project of the OpenJS Foundation, use | ||
[Contributor Covenant v2.0](https://contributor-covenant.org/version/2/0/code_of_conduct) | ||
as their code of conduct. The full text is included | ||
[below](#contributor-covenant-code-of-conduct-v2.0) in English, and translations | ||
are available from the Contributor Covenant organisation: | ||
|
||
- [contributor-covenant.org/translations](https://www.contributor-covenant.org/translations) | ||
- [github.com/ContributorCovenant](https://github.com/ContributorCovenant/contributor_covenant/tree/release/content/version/2/0) | ||
|
||
Refer to the sections on reporting and escalation in this document for the | ||
specific emails that can be used to report and escalate issues. | ||
|
||
## Reporting | ||
|
||
### Project Spaces | ||
|
||
For reporting issues in spaces related to LoopBack, please use the email | ||
`[email protected]`. The LoopBack Technical Steering Committee (TSC) handles CoC issues related to the spaces that it | ||
maintains. The project TSC commits to: | ||
|
||
- maintain the confidentiality with regard to the reporter of an incident | ||
- to participate in the path for escalation as outlined in the section on | ||
Escalation when required. | ||
|
||
### Foundation Spaces | ||
|
||
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: | ||
|
||
- maintain the confidentiality with regard to the reporter of an incident | ||
- to participate in the path for escalation as outlined in the section on | ||
Escalation when required. | ||
|
||
## Escalation | ||
|
||
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]`. | ||
|
||
For more information, refer to the full | ||
[Code of Conduct governance document](https://github.com/openjs-foundation/cross-project-council/blob/HEAD/CODE_OF_CONDUCT.md). | ||
|
||
--- | ||
|
||
## Contributor Covenant Code of Conduct v2.0 | ||
|
||
## Our Pledge | ||
|
||
|
@@ -125,4 +175,4 @@ Community Impact Guidelines were inspired by | |
|
||
For answers to common questions about this code of conduct, see the FAQ at | ||
https://www.contributor-covenant.org/faq. Translations are available at | ||
https://www.contributor-covenant.org/translations. | ||
https://www.contributor-covenant.org/translations. |