Skip to content

Commit 2788d8a

Browse files
ktaborssnowystingerdannify
authored
chore: updating the code of conduct to newer version (#7693)
* updating the code of conduct to newer version * Update CONTRIBUTING.md --------- Co-authored-by: Robert Snow <[email protected]> Co-authored-by: Danni <[email protected]>
1 parent 939205c commit 2788d8a

File tree

2 files changed

+59
-50
lines changed

2 files changed

+59
-50
lines changed

CODE_OF_CONDUCT.md

Lines changed: 53 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -2,73 +2,78 @@
22

33
## Our Pledge
44

5-
In the interest of fostering an open and welcoming environment, we as
6-
contributors and maintainers pledge to making participation in our project and
7-
our community a harassment-free experience for everyone, regardless of age, body
8-
size, disability, ethnicity, gender identity and expression, level of experience,
9-
nationality, personal appearance, race, religion, or sexual identity and
10-
orientation.
5+
We as members, contributors, and leaders pledge to make participation in our project and community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
6+
7+
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
118

129
## Our Standards
1310

14-
Examples of behavior that contributes to creating a positive environment
15-
include:
11+
Examples of behavior that contribute to a positive environment for our project and community include:
1612

17-
* Using welcoming and inclusive language.
18-
* Being respectful of differing viewpoints and experiences.
19-
* Gracefully accepting constructive criticism.
20-
* Focusing on what is best for the community.
21-
* Showing empathy towards other community members.
13+
* Demonstrating empathy and kindness toward other people
14+
* Being respectful of differing opinions, viewpoints, and experiences
15+
* Giving and gracefully accepting constructive feedback
16+
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17+
* Focusing on what is best, not just for us as individuals but for the overall community
2218

23-
Examples of unacceptable behavior by participants include:
19+
Examples of unacceptable behavior include:
2420

25-
* The use of sexualized language or imagery and unwelcome sexual attention or
26-
advances.
27-
* Trolling, insulting/derogatory comments, and personal or political attacks.
28-
* Public or private harassment.
29-
* Publishing others' private information, such as a physical or electronic
30-
address, without explicit permission.
31-
* Other conduct which could reasonably be considered inappropriate in a
32-
professional setting.
21+
* The use of sexualized language or imagery, and sexual attention or advances of any kind
22+
* Trolling, insulting or derogatory comments, and personal or political attacks
23+
* Public or private harassment
24+
* Publishing others’ private information, such as a physical or email address, without their explicit permission
25+
* Other conduct which could reasonably be considered inappropriate in a professional setting
3326

3427
## Our Responsibilities
3528

36-
Project maintainers are responsible for clarifying the standards of acceptable
37-
behavior and are expected to take appropriate and fair corrective action in
38-
response to any instances of unacceptable behavior.
29+
Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any instances of unacceptable behavior.
3930

40-
Project maintainers have the right and responsibility to remove, edit, or
41-
reject comments, commits, code, wiki edits, issues, and other contributions
42-
that are not aligned to this Code of Conduct, or to ban temporarily or
43-
permanently any contributor for other behaviors that they deem inappropriate,
44-
threatening, offensive, or harmful.
31+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for behaviors that they deem inappropriate, threatening, offensive, or harmful.
4532

4633
## Scope
4734

48-
This Code of Conduct applies both within project spaces and in public spaces
49-
when an individual is representing the project or its community. Examples of
50-
representing a project or community include using an official project e-mail
51-
address, posting via an official social media account, or acting as an appointed
52-
representative at an online or offline event. Representation of a project may be
53-
further defined and clarified by project maintainers.
35+
This Code of Conduct applies when an individual is representing the project or its community both within project spaces and in public spaces. Examples of representing a project or community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
5436

5537
## Enforcement
5638

57-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58-
reported by contacting the project team at [email protected]. All
59-
complaints will be reviewed and investigated and will result in a response that
60-
is deemed necessary and appropriate to the circumstances. The project team is
61-
obligated to maintain confidentiality with regard to the reporter of an incident.
62-
Further details of specific enforcement policies may be posted separately.
39+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by first contacting the project team. Oversight of Adobe projects is handled by the Adobe Open Source Office, which has final say in any violations and enforcement of this Code of Conduct and can be reached at [email protected]. All complaints will be reviewed and investigated promptly and fairly.
40+
41+
The project team must respect the privacy and security of the reporter of any incident.
42+
43+
Project maintainers who do not follow or enforce the Code of Conduct may face temporary or permanent repercussions as determined by other members of the project's leadership or the Adobe Open Source Office.
44+
45+
## Enforcement Guidelines
46+
47+
Project maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem to be in violation of this Code of Conduct:
48+
49+
**1. Correction**
50+
51+
Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
52+
53+
Consequence: A private, written warning from project maintainers describing the violation and why the behavior was unacceptable. A public apology may be requested from the violator before any further involvement in the project by violator.
54+
55+
**2. Warning**
56+
57+
Community Impact: A relatively minor violation through a single incident or series of actions.
58+
59+
Consequence: A written warning from project maintainers that includes stated consequences for continued unacceptable behavior. Violator must refrain from interacting with the people involved for a specified period of time as determined by the project maintainers, including, but not limited to, unsolicited interaction with those enforcing the Code of Conduct through channels such as community spaces and social media. Continued violations may lead to a temporary or permanent ban.
60+
61+
**3. Temporary Ban**
62+
63+
Community Impact: A more serious violation of community standards, including sustained unacceptable behavior.
64+
65+
Consequence: A temporary ban from any interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Failure to comply with the temporary ban may lead to a permanent ban.
66+
67+
**4. Permanent Ban**
68+
69+
Community Impact: Demonstrating a consistent pattern of violation of community standards or an egregious violation of community standards, including, but not limited to, sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
6370

64-
Project maintainers who do not follow or enforce the Code of Conduct in good
65-
faith may face temporary or permanent repercussions as determined by other
66-
members of the project's leadership.
71+
Consequence: A permanent ban from any interaction with the community.
6772

6873
## Attribution
6974

70-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71-
available at [https://contributor-covenant.org/version/1/4][version].
75+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1,
76+
available at [https://contributor-covenant.org/version/2/1][version]
7277

7378
[homepage]: https://contributor-covenant.org
74-
[version]: https://contributor-covenant.org/version/1/4/
79+
[version]: https://contributor-covenant.org/version/2/1

CONTRIBUTING.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -216,6 +216,10 @@ You may have run `yarn build` before. Please run `make clean_all && yarn` to cle
216216

217217
It may also just be a stale cache, you can try deleting the `.parcel-cache`
218218

219-
## Contributor to committer
219+
## From Contributor To Committer
220220

221-
We love contributions from our community! If you'd like to go a step beyond contributor and become a committer with full write access and a say in the project, you must be invited. The existing committers employ an internal nomination process that must reach lazy consensus (silence is approval) before invitations are issued. If you feel you are qualified and want to get more deeply involved, feel free to reach out to existing committers to have a conversation.
221+
We love contributions from our community! At this time, we are not accepting new committers. We thank you for your understanding.
222+
223+
## Security Issues
224+
225+
Security issues shouldn't be reported on this issue tracker. Instead, [file an issue to our security experts](https://helpx.adobe.com/security/alertus.html).

0 commit comments

Comments
 (0)