xref: /aosp_15_r20/external/okio/docs/code_of_conduct.md (revision f9742813c14b702d71392179818a9e591da8620c)
1Open Source Code of Conduct
2===========================
3
4At Square, we are committed to contributing to the open source community and simplifying the process
5of releasing and managing open source software. We’ve seen incredible support and enthusiasm from
6thousands of people who have already contributed to our projects — and we want to ensure our community
7continues to be truly open for everyone.
8
9This code of conduct outlines our expectations for participants, as well as steps to reporting
10unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and
11expect our code of conduct to be honored.
12
13Square’s open source community strives to:
14
15 * **Be open**: We invite anyone to participate in any aspect of our projects. Our community is
16   open, and any responsibility can be carried by a contributor who demonstrates the required
17   capacity and competence.
18
19 * **Be considerate**: People use our work, and we depend on the work of others. Consider users and
20   colleagues before taking action. For example, changes to code, infrastructure, policy, and
21   documentation may negatively impact others.
22
23 * **Be respectful**: We expect people to work together to resolve conflict, assume good intentions,
24   and act with empathy. Do not turn disagreements into personal attacks.
25
26 * **Be collaborative**: Collaboration reduces redundancy and improves the quality of our work. We
27   strive for transparency within our open source community, and we work closely with upstream
28   developers and others in the free software community to coordinate our efforts.
29
30 * **Be pragmatic**: Questions are encouraged and should be asked early in the process to avoid
31   problems later. Be thoughtful and considerate when seeking out the appropriate forum for your
32   questions. Those who are asked should be responsive and helpful.
33
34 * **Step down considerately**: Members of every project come and go. When somebody leaves or
35   disengages from the project, they should make it known and take the proper steps to ensure that
36   others can pick up where they left off.
37
38This code is not exhaustive or complete. It serves to distill our common understanding of a
39collaborative, shared environment, and goals. We expect it to be followed in spirit as much as in
40the letter.
41
42Diversity Statement
43-------------------
44
45We encourage everyone to participate and are committed to building a community for all. Although we
46may not be able to satisfy everyone, we all agree that everyone is equal.
47
48Whenever a participant has made a mistake, we expect them to take responsibility for it. If someone
49has been harmed or offended, it is our responsibility to listen carefully and respectfully, and do
50our best to right the wrong.
51
52Although this list cannot be exhaustive, we explicitly honor diversity in age, culture, ethnicity,
53gender identity or expression, language, national origin, political beliefs, profession, race,
54religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate
55discrimination based on any of the protected characteristics above, including participants with
56disabilities.
57
58Reporting Issues
59----------------
60
61If you experience or witness unacceptable behavior — or have any other concerns — please report it by
62emailing [[email protected]][codeofconduct_at]. For more details, please see our Reporting
63Guidelines below.
64
65Thanks
66------
67
68Some of the ideas and wording for the statements and guidelines above were based on work by the
69[Twitter][twitter_coc], [Ubuntu][ubuntu_coc], [GDC][gdc_coc], and [Django][django_coc] communities.
70We are thankful for their work.
71
72Reporting Guide
73---------------
74
75If you experience or witness unacceptable behavior — or have any other concerns — please report it by
76emailing [[email protected]][codeofconduct_at]. All reports will be handled with
77discretion.
78
79In your report please include:
80
81 * Your contact information.
82 * Names (real, nicknames, or pseudonyms) of any individuals involved. If there are additional
83   witnesses, please include them as well.
84 * Your account of what occurred, and if you believe the incident is ongoing. If there is a publicly
85   available record (e.g. a mailing list archive or a public IRC logger), please include a link.
86 * Any additional information that may be helpful.
87
88After filing a report, a representative from the Square Code of Conduct committee will contact you
89personally. The committee will then review the incident, follow up with any additional questions,
90and make a decision as to how to respond.
91
92Anyone asked to stop unacceptable behavior is expected to comply immediately. If an individual
93engages in unacceptable behavior, the Square Code of Conduct committee may take any action they deem
94appropriate, up to and including a permanent ban from all of Square spaces without warning.
95
96
97[codeofconduct_at]: mailto:[email protected]
98[twitter_coc]: https://github.com/twitter/code-of-conduct/blob/master/code-of-conduct.md
99[ubuntu_coc]: https://ubuntu.com/community/code-of-conduct
100[gdc_coc]: https://www.gdconf.com/code-of-conduct
101[django_coc]: https://www.djangoproject.com/conduct/reporting/
102
103