]>
Commit | Line | Data |
---|---|---|
5cdf2301 JK |
1 | # Git Code of Conduct |
2 | ||
3 | This code of conduct outlines our expectations for participants within | |
4 | the Git community, as well as steps for reporting unacceptable behavior. | |
5 | We are committed to providing a welcoming and inspiring community for | |
6 | all and expect our code of conduct to be honored. Anyone who violates | |
7 | this code of conduct may be banned from the community. | |
8 | ||
9 | ## Our Pledge | |
10 | ||
11 | In the interest of fostering an open and welcoming environment, we as | |
12 | contributors and maintainers pledge to make participation in our project and | |
13 | our community a harassment-free experience for everyone, regardless of age, | |
14 | body size, disability, ethnicity, sex characteristics, gender identity and | |
15 | expression, level of experience, education, socio-economic status, | |
16 | nationality, personal appearance, race, religion, or sexual identity and | |
17 | orientation. | |
18 | ||
19 | ## Our Standards | |
20 | ||
21 | Examples of behavior that contributes to creating a positive environment | |
22 | include: | |
23 | ||
24 | * Using welcoming and inclusive language | |
25 | * Being respectful of differing viewpoints and experiences | |
26 | * Gracefully accepting constructive criticism | |
27 | * Focusing on what is best for the community | |
28 | * Showing empathy towards other community members | |
29 | ||
30 | Examples of unacceptable behavior by participants include: | |
31 | ||
32 | * The use of sexualized language or imagery and unwelcome sexual attention or | |
33 | advances | |
34 | * Trolling, insulting/derogatory comments, and personal or political attacks | |
35 | * Public or private harassment | |
36 | * Publishing others' private information, such as a physical or electronic | |
37 | address, without explicit permission | |
38 | * Other conduct which could reasonably be considered inappropriate in a | |
39 | professional setting | |
40 | ||
41 | ## Our Responsibilities | |
42 | ||
43 | Project maintainers are responsible for clarifying the standards of acceptable | |
44 | behavior and are expected to take appropriate and fair corrective action in | |
45 | response to any instances of unacceptable behavior. | |
46 | ||
47 | Project maintainers have the right and responsibility to remove, edit, or | |
48 | reject comments, commits, code, wiki edits, issues, and other contributions | |
49 | that are not aligned to this Code of Conduct, or to ban temporarily or | |
50 | permanently any contributor for other behaviors that they deem inappropriate, | |
51 | threatening, offensive, or harmful. | |
52 | ||
53 | ## Scope | |
54 | ||
55 | This Code of Conduct applies within all project spaces, and it also applies | |
56 | when an individual is representing the project or its community in public | |
57 | spaces. Examples of representing a project or community include using an | |
58 | official project e-mail address, posting via an official social media account, | |
59 | or acting as an appointed representative at an online or offline event. | |
60 | Representation of a project may be further defined and clarified by project | |
61 | maintainers. | |
62 | ||
63 | ## Enforcement | |
64 | ||
65 | Instances of abusive, harassing, or otherwise unacceptable behavior may be | |
66 | reported by contacting the project team at git@sfconservancy.org. All | |
67 | complaints will be reviewed and investigated and will result in a response | |
68 | that is deemed necessary and appropriate to the circumstances. The project | |
69 | team is obligated to maintain confidentiality with regard to the reporter of | |
70 | an incident. Further details of specific enforcement policies may be posted | |
71 | separately. | |
72 | ||
73 | Project maintainers who do not follow or enforce the Code of Conduct in good | |
74 | faith may face temporary or permanent repercussions as determined by other | |
75 | members of the project's leadership. | |
76 | ||
3f9ef874 JK |
77 | The project leadership team can be contacted by email as a whole at |
78 | git@sfconservancy.org, or individually: | |
79 | ||
80 | - Ævar Arnfjörð Bjarmason <avarab@gmail.com> | |
81 | - Christian Couder <christian.couder@gmail.com> | |
82 | - Jeff King <peff@peff.net> | |
83 | - Junio C Hamano <gitster@pobox.com> | |
84 | ||
5cdf2301 JK |
85 | ## Attribution |
86 | ||
87 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], | |
88 | version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html | |
89 | ||
90 | [homepage]: https://www.contributor-covenant.org | |
91 | ||
92 | For answers to common questions about this code of conduct, see | |
93 | https://www.contributor-covenant.org/faq |