|
| 1 | +<!-- # Generated by synthtool. DO NOT EDIT! !--> |
| 2 | +# Code of Conduct |
| 3 | + |
| 4 | +## Our Pledge |
| 5 | + |
| 6 | +In the interest of fostering an open and welcoming environment, we as |
| 7 | +contributors and maintainers pledge to making participation in our project and |
| 8 | +our community a harassment-free experience for everyone, regardless of age, body |
| 9 | +size, disability, ethnicity, gender identity and expression, level of |
| 10 | +experience, education, socio-economic status, nationality, personal appearance, |
| 11 | +race, religion, or sexual identity and orientation. |
| 12 | + |
| 13 | +## Our Standards |
| 14 | + |
| 15 | +Examples of behavior that contributes to creating a positive environment |
| 16 | +include: |
| 17 | + |
| 18 | +* Using welcoming and inclusive language |
| 19 | +* Being respectful of differing viewpoints and experiences |
| 20 | +* Gracefully accepting constructive criticism |
| 21 | +* Focusing on what is best for the community |
| 22 | +* Showing empathy towards other community members |
| 23 | + |
| 24 | +Examples of unacceptable behavior by participants include: |
| 25 | + |
| 26 | +* The use of sexualized language or imagery and unwelcome sexual attention or |
| 27 | + advances |
| 28 | +* Trolling, insulting/derogatory comments, and personal or political attacks |
| 29 | +* Public or private harassment |
| 30 | +* Publishing others' private information, such as a physical or electronic |
| 31 | + address, without explicit permission |
| 32 | +* Other conduct which could reasonably be considered inappropriate in a |
| 33 | + professional setting |
| 34 | + |
| 35 | +## Our Responsibilities |
| 36 | + |
| 37 | +Project maintainers are responsible for clarifying the standards of acceptable |
| 38 | +behavior and are expected to take appropriate and fair corrective action in |
| 39 | +response to any instances of unacceptable behavior. |
| 40 | + |
| 41 | +Project maintainers have the right and responsibility to remove, edit, or reject |
| 42 | +comments, commits, code, wiki edits, issues, and other contributions that are |
| 43 | +not aligned to this Code of Conduct, or to ban temporarily or permanently any |
| 44 | +contributor for other behaviors that they deem inappropriate, threatening, |
| 45 | +offensive, or harmful. |
| 46 | + |
| 47 | +## Scope |
| 48 | + |
| 49 | +This Code of Conduct applies both within project spaces and in public spaces |
| 50 | +when an individual is representing the project or its community. Examples of |
| 51 | +representing a project or community include using an official project e-mail |
| 52 | +address, posting via an official social media account, or acting as an appointed |
| 53 | +representative at an online or offline event. Representation of a project may be |
| 54 | +further defined and clarified by project maintainers. |
| 55 | + |
| 56 | +This Code of Conduct also applies outside the project spaces when the Project |
| 57 | +Steward has a reasonable belief that an individual's behavior may have a |
| 58 | +negative impact on the project or its community. |
| 59 | + |
| 60 | +## Conflict Resolution |
| 61 | + |
| 62 | +We do not believe that all conflict is bad; healthy debate and disagreement |
| 63 | +often yield positive results. However, it is never okay to be disrespectful or |
| 64 | +to engage in behavior that violates the project’s code of conduct. |
| 65 | + |
| 66 | +If you see someone violating the code of conduct, you are encouraged to address |
| 67 | +the behavior directly with those involved. Many issues can be resolved quickly |
| 68 | +and easily, and this gives people more control over the outcome of their |
| 69 | +dispute. If you are unable to resolve the matter for any reason, or if the |
| 70 | +behavior is threatening or harassing, report it. We are dedicated to providing |
| 71 | +an environment where participants feel welcome and safe. |
| 72 | + |
| 73 | + |
| 74 | +Reports should be directed to *[email protected]*, the |
| 75 | +Project Steward(s) for *Google Cloud Client Libraries*. It is the Project Steward’s duty to |
| 76 | +receive and address reported violations of the code of conduct. They will then |
| 77 | +work with a committee consisting of representatives from the Open Source |
| 78 | +Programs Office and the Google Open Source Strategy team. If for any reason you |
| 79 | +are uncomfortable reaching out to the Project Steward, please email |
| 80 | + |
| 81 | + |
| 82 | +We will investigate every complaint, but you may not receive a direct response. |
| 83 | +We will use our discretion in determining when and how to follow up on reported |
| 84 | +incidents, which may range from not taking action to permanent expulsion from |
| 85 | +the project and project-sponsored spaces. We will notify the accused of the |
| 86 | +report and provide them an opportunity to discuss it before any action is taken. |
| 87 | +The identity of the reporter will be omitted from the details of the report |
| 88 | +supplied to the accused. In potentially harmful situations, such as ongoing |
| 89 | +harassment or threats to anyone's safety, we may take action without notice. |
| 90 | + |
| 91 | +## Attribution |
| 92 | + |
| 93 | +This Code of Conduct is adapted from the Contributor Covenant, version 1.4, |
| 94 | +available at |
| 95 | +https://www.contributor-covenant.org/version/1/4/code-of-conduct.html |
0 commit comments