Skip to content

Commit 1aa10eb

Browse files
anonriganonrig
committed
test: add more fixtures
1 parent b5984a0 commit 1aa10eb

File tree

4 files changed

+459
-0
lines changed

4 files changed

+459
-0
lines changed

‎test/openjsf/expected.md

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

‎test/openjsf/original-expected.md

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

0 commit comments

Comments
 (0)