|
| 1 | +Code of Conduct |
| 2 | +=============== |
| 3 | + |
| 4 | +OpenAPI Initiative Code of Conduct |
| 5 | + |
| 6 | +*The Linux Foundation* |
| 7 | + |
| 8 | +*Effective November 24, 2020* |
| 9 | + |
| 10 | +The OpenAPI Initiative (OAI) is an open source Linux Foundation project |
| 11 | +and home of the OpenAPI Specification (OAS) released under the Apache |
| 12 | +2.0 license. As contributors, maintainers, and participants in this |
| 13 | +project, we want to foster an open and welcoming environment. We pledge |
| 14 | +to make participation in our project and our community a harassment-free |
| 15 | +experience for everyone, regardless of age, body size, disability, |
| 16 | +ethnicity, gender identity and expression, level of experience, |
| 17 | +education, socio-economic status, nationality, personal appearance, |
| 18 | +race, religion, or sexual identity and orientation. |
| 19 | + |
| 20 | +Our Standards |
| 21 | +------------- |
| 22 | + |
| 23 | +Examples of behaviors that contribute to creating a positive environment |
| 24 | +include: |
| 25 | + |
| 26 | +- Using welcoming and inclusive language |
| 27 | + |
| 28 | +- Being respectful of differing viewpoints and experiences |
| 29 | + |
| 30 | +- Gracefully accepting constructive criticism |
| 31 | + |
| 32 | +- Focusing on what is best for the community |
| 33 | + |
| 34 | +- Showing empathy towards other community members |
| 35 | + |
| 36 | +- Assuming the best intent from others |
| 37 | + |
| 38 | +Examples of unacceptable behavior by participants include: |
| 39 | + |
| 40 | +- The use of sexualized language or imagery and unwelcome sexual attention or advances |
| 41 | + |
| 42 | +- Making unsolicited, insulting or derogatory comments, including personal (i.e., ad hominem) or political attacks to create conflict (e.g., trolling) |
| 43 | + |
| 44 | +- Public or private harassment |
| 45 | + |
| 46 | +- Publishing others' private information, such as a physical or electronic address, without explicit permission (e.g., doxxing) |
| 47 | + |
| 48 | +- Threatening, offensive, harmful comments, or behavior |
| 49 | + |
| 50 | +- Other conduct which could reasonably be considered inappropriate in a professional setting |
| 51 | + |
| 52 | +Our Responsibilities |
| 53 | +-------------------- |
| 54 | + |
| 55 | +The Code of Conduct Committee is responsible for clarifying the |
| 56 | +standards of acceptable behavior and is expected to take appropriate and |
| 57 | +fair corrective action in response to any instances of unacceptable |
| 58 | +behavior. |
| 59 | + |
| 60 | +Scope |
| 61 | +----- |
| 62 | + |
| 63 | +This Code of Conduct applies to OAI project spaces, as well as |
| 64 | +interactions in public spaces. Project spaces include, but are not |
| 65 | +limited to, official OAI code repositories, Slack, mailing lists, |
| 66 | +meetings, and events. Public spaces may include venues where an |
| 67 | +individual is representing the project or its community. Examples of |
| 68 | +this include a community member's email communication, forum posts, |
| 69 | +social media activity, or acting as a representative at an online or |
| 70 | +offline event. In addition, violations of this code of conduct outside |
| 71 | +of these spaces may affect a person's ability to participate in them. |
| 72 | + |
| 73 | +Enforcement |
| 74 | +----------- |
| 75 | + |
| 76 | +To report instances of abuse, harassment, or otherwise unacceptable |
| 77 | +behavior, contact |
| 78 | +[conduct \@openapis.org ](mailto:[email protected]). **We |
| 79 | +are committed to maintaining the confidentiality of anyone reporting an |
| 80 | +incident**. The Code of Conduct Committee will review and investigate |
| 81 | +all complaints, responding as deemed necessary and appropriate to the |
| 82 | +circumstances. For incidents relating to offline events, we aim to |
| 83 | +respond to reports within 24 hours, and for incidents relating to online |
| 84 | +activities, we aim to respond to reports within 7 days. |
| 85 | + |
| 86 | +The Code of Conduct Committee has the right and responsibility to |
| 87 | +remove, edit, or reject comments, commits, code, wiki edits, issues, and |
| 88 | +other contributions that are not aligned to this Code of Conduct, or |
| 89 | +take other appropriate action as deemed necessary for behaviors contrary |
| 90 | +to the standards listed above. In the case of offline or in-person |
| 91 | +events, if a participant engages in behavior that is not aligned to this |
| 92 | +Code of Conduct, the committee may take action, such as warning the |
| 93 | +offender, banning the offender from various online spaces (temporary or |
| 94 | +permanent), removing the offender from an event with no refund, or other |
| 95 | +options deemed appropriate. |
| 96 | + |
| 97 | +Further details of specific enforcement policies are currently being |
| 98 | +drafted. When these details are completed we will post updates to our |
| 99 | +website for transparency. |
| 100 | + |
| 101 | +Project maintainers who do not report possible incidents or follow |
| 102 | +responses in good faith may face temporary or permanent repercussions as |
| 103 | +determined by the Code of Conduct Committee. |
| 104 | + |
| 105 | +### Events |
| 106 | + |
| 107 | +Some OpenAPI events are governed by the [Linux Foundation Code of |
| 108 | +Conduct](https://events.linuxfoundation.org/about/code-of-conduct/) |
| 109 | +(E.g. API Specifications Conference) and will be listed on the event |
| 110 | +page. The OAI Code of Conduct is designed to be compatible with the |
| 111 | +above policy and also includes more details on responding to incidents. |
| 112 | + |
| 113 | +### Attribution |
| 114 | + |
| 115 | +This code of conduct is adapted from the [Contributor Covenant, version |
| 116 | +1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct) |
| 117 | +and the [PyCon 2019 Code of |
| 118 | +Conduct](https://us.pycon.org/2019/about/code-of-conduct/). |
0 commit comments