|
1 | | -# Code of Conduct |
| 1 | +# Contributor Covenant Code of Conduct |
2 | 2 |
|
3 | | -## Our Commitment |
| 3 | +## Our Pledge |
4 | 4 |
|
5 | | -The SDKMAN CLI Native project is committed to providing a safe, welcoming, and harassment-free environment for all contributors, regardless of experience level, background, or identity. We value respectful collaboration and constructive dialogue. |
| 5 | +We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, 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. |
6 | 8 |
|
7 | 9 | ## Our Standards |
8 | 10 |
|
9 | | -### Expected Behavior |
10 | | - |
11 | | -**Be Respectful and Professional** |
12 | | -- Treat all community members with courtesy and respect |
13 | | -- Use welcoming and inclusive language |
14 | | -- Be patient with newcomers and those learning |
15 | | -- Accept constructive criticism gracefully |
16 | | -- Focus on what is best for the project and community |
17 | | - |
18 | | -**Engage in Constructive Technical Discussion** |
19 | | -- Technical disagreements are natural and welcome |
20 | | -- Debate ideas and approaches, not people |
21 | | -- Support your positions with reasoning and evidence |
22 | | -- Be open to changing your mind when presented with better solutions |
23 | | -- Assume good faith in technical discussions |
24 | | - |
25 | | -**Collaborate Before Contributing** |
26 | | -- Discuss new features or significant changes on our Discord server *before* starting work |
27 | | -- Small, incremental pull requests are strongly preferred |
28 | | -- Large "change the world" PRs will not be accepted without prior discussion |
29 | | -- Seek guidance early to ensure alignment with project direction |
30 | | -- Be receptive to feedback and willing to iterate |
31 | | - |
32 | | -**Respect the Contribution Process** |
33 | | -- Break large changes into small, reviewable increments |
34 | | -- Each PR should represent a focused, atomic change |
35 | | -- Engage in conversation to guide and inform decisions |
36 | | -- Understand that maintainers may redirect or decline contributions |
37 | | - |
38 | | -### Unacceptable Behavior |
39 | | - |
40 | | -The following behaviors will not be tolerated: |
41 | | - |
42 | | -- Rude, hostile, or aggressive communication |
43 | | -- Personal attacks, insults, or derogatory comments |
44 | | -- Harassment of any kind, public or private |
45 | | -- Publishing others' private information without permission |
46 | | -- Dismissive or condescending language toward other contributors |
47 | | -- Deliberately derailing technical discussions |
48 | | -- Submitting large, undiscussed PRs that disregard project guidelines |
49 | | -- Any conduct that could reasonably be considered inappropriate in a professional setting |
| 11 | +Examples of behavior that contributes to a positive environment for our community include: |
| 12 | + |
| 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 |
| 18 | + |
| 19 | +Examples of unacceptable behavior include: |
| 20 | + |
| 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 |
| 26 | + |
| 27 | +## Enforcement Responsibilities |
| 28 | + |
| 29 | +Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. |
| 30 | + |
| 31 | +Community leaders 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, and will communicate reasons for moderation decisions when appropriate. |
50 | 32 |
|
51 | 33 | ## Scope |
52 | 34 |
|
53 | | -This Code of Conduct applies to all project spaces on GitHub, including: |
54 | | -- Issues and pull requests |
55 | | -- Code reviews and comments |
56 | | -- Discussions and wikis |
57 | | -- Repository documentation |
| 35 | +This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our 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. |
58 | 36 |
|
59 | 37 | ## Enforcement |
60 | 38 |
|
61 | | -Violations of this Code of Conduct will not be tolerated. If you experience or witness unacceptable behavior, please report it by contacting the project maintainer. |
| 39 | +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [email protected]. All complaints will be reviewed and investigated promptly and fairly. |
| 40 | + |
| 41 | +All community leaders are obligated to respect the privacy and security of the reporter of any incident. |
| 42 | + |
| 43 | +## Enforcement Guidelines |
| 44 | + |
| 45 | +Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: |
| 46 | + |
| 47 | +### 1. Correction |
| 48 | + |
| 49 | +**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. |
| 50 | + |
| 51 | +**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. |
| 52 | + |
| 53 | +### 2. Warning |
| 54 | + |
| 55 | +**Community Impact**: A violation through a single incident or series of actions. |
| 56 | + |
| 57 | +**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. |
| 58 | + |
| 59 | +### 3. Temporary Ban |
| 60 | + |
| 61 | +**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. |
| 62 | + |
| 63 | +**Consequence**: A temporary ban from any sort of 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. Violating these terms may lead to a permanent ban. |
| 64 | + |
| 65 | +### 4. Permanent Ban |
| 66 | + |
| 67 | +**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. |
62 | 68 |
|
63 | | -Reports will be reviewed and investigated. The maintainer will respond as deemed appropriate to the circumstances, which may include warnings, temporary bans, or permanent removal from the project. |
| 69 | +**Consequence**: A permanent ban from any sort of public interaction within the community. |
64 | 70 |
|
65 | | -All community members are expected to respect the privacy and security of the reporter of any incident. |
| 71 | +## Attribution |
66 | 72 |
|
67 | | -## Questions or Concerns |
| 73 | +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. |
68 | 74 |
|
69 | | -If you have questions about this Code of Conduct or how it applies, please reach out on our Discord server or open a discussion on GitHub. |
| 75 | +Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. |
70 | 76 |
|
71 | | ---- |
| 77 | +For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations]. |
72 | 78 |
|
73 | | -*This Code of Conduct is focused on maintaining a professional, collaborative environment where incremental progress and respectful dialogue lead to better software.* |
| 79 | +[homepage]: https://www.contributor-covenant.org |
| 80 | +[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html |
| 81 | +[Mozilla CoC]: https://github.com/mozilla/diversity |
| 82 | +[FAQ]: https://www.contributor-covenant.org/faq |
| 83 | +[translations]: https://www.contributor-covenant.org/translations |
0 commit comments