1# Mage Community Code of Conduct 2 3This is a copy of the [go code of conduct](https://golang.org/conduct). It applies to all areas of the magefile github organization, the #mage and #mage-dev slack channels on gopher slack, and the mage google group (https://groups.google.com/forum/#!forum/magefile). 4 5Reports may be directed to Nate Finch, the Mage Project Steward at nate.finch@gmail.com, or Carmen Andoh and Van Riper, the Go Project Stewards at conduct@golang.org. 6 7## About 8Online communities include people from many different backgrounds. The Go contributors are committed to providing a friendly, safe and welcoming environment for all, regardless of gender identity and expression, sexual orientation, disabilities, neurodiversity, physical appearance, body size, ethnicity, nationality, race, age, religion, or similar personal characteristics. 9 10The first goal of the Code of Conduct is to specify a baseline standard of behavior so that people with different social values and communication styles can talk about Go effectively, productively, and respectfully. 11 12The second goal is to provide a mechanism for resolving conflicts in the community when they arise. 13 14The third goal of the Code of Conduct is to make our community welcoming to people from different backgrounds. Diversity is critical to the project; for Go to be successful, it needs contributors and users from all backgrounds. (See Go, Open Source, Community.) 15 16We believe that healthy debate and disagreement are essential to a healthy project and community. However, it is never ok to be disrespectful. We value diverse opinions, but we value respectful behavior more. 17 18## Gopher values 19These are the values to which people in the Go community (“Gophers”) should aspire. 20 21## Be friendly and welcoming 22* Be patient 23 * Remember that people have varying communication styles and that not everyone is using their native language. (Meaning and tone can be lost in translation.) 24* Be thoughtful 25 * Productive communication requires effort. Think about how your words will be interpreted. 26 * Remember that sometimes it is best to refrain entirely from commenting. 27* Be respectful 28 * In particular, respect differences of opinion. 29* Be charitable 30 * Interpret the arguments of others in good faith, do not seek to disagree. 31 * When we do disagree, try to understand why. 32* Avoid destructive behavior: 33 * Derailing: stay on topic; if you want to talk about something else, start a new conversation. 34 * Unconstructive criticism: don't merely decry the current state of affairs; offer—or at least solicit—suggestions as to how things may be improved. 35 * Snarking (pithy, unproductive, sniping comments) 36 * Discussing potentially offensive or sensitive issues; this all too often leads to unnecessary conflict. 37 * Microaggressions: brief and commonplace verbal, behavioral and environmental indignities that communicate hostile, derogatory or negative slights and insults to a person or group. 38People are complicated. You should expect to be misunderstood and to misunderstand others; when this inevitably occurs, resist the urge to be defensive or assign blame. Try not to take offense where no offense was intended. Give people the benefit of the doubt. Even if the intent was to provoke, do not rise to it. It is the responsibility of all parties to de-escalate conflict when it arises. 39 40## Code of Conduct 41### Our Pledge 42In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. 43 44### Our Standards 45Examples of behavior that contributes to creating a positive environment include: 46 47Using welcoming and inclusive language 48Being respectful of differing viewpoints and experiences 49Gracefully accepting constructive criticism 50Focusing on what is best for the community 51Showing empathy towards other community members 52Examples of unacceptable behavior by participants include: 53 54The use of sexualized language or imagery and unwelcome sexual attention or advances 55Trolling, insulting/derogatory comments, and personal or political attacks 56Public or private harassment 57Publishing others’ private information, such as a physical or electronic address, without explicit permission 58Other conduct which could reasonably be considered inappropriate in a professional setting 59Our Responsibilities 60Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 61 62Project maintainers 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 63 64### Scope 65This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 66 67This Code of Conduct also applies outside the project spaces when the Project Stewards have a reasonable belief that an individual’s behavior may have a negative impact on the project or its community. 68 69### Conflict Resolution 70We do not believe that all conflict is bad; healthy debate and disagreement often yield positive results. However, it is never okay to be disrespectful or to engage in behavior that violates the project’s code of conduct. 71 72If you see someone violating the code of conduct, you are encouraged to address the behavior directly with those involved. Many issues can be resolved quickly and easily, and this gives people more control over the outcome of their dispute. If you are unable to resolve the matter for any reason, or if the behavior is threatening or harassing, report it. We are dedicated to providing an environment where participants feel welcome and safe. 73 74Reports should be directed to Carmen Andoh and Van Riper, the Go Project Stewards, at conduct@golang.org \[or Nate Finch at nate.finch@gmail.com\]. It is the Project Stewards’ duty to receive and address reported violations of the code of conduct. They will then work with a committee consisting of representatives from the Open Source Programs Office and the Google Open Source Strategy team. If for any reason you are uncomfortable reaching out the Project Stewards, please email the Google Open Source Programs Office at opensource@google.com. 75 76We will investigate every complaint, but you may not receive a direct response. We will use our discretion in determining when and how to follow up on reported incidents, which may range from not taking action to permanent expulsion from the project and project-sponsored spaces. We will notify the accused of the report and provide them an opportunity to discuss it before any action is taken. The identity of the reporter will be omitted from the details of the report supplied to the accused. In potentially harmful situations, such as ongoing harassment or threats to anyone’s safety, we may take action without notice. 77 78### Attribution 79This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 80 81## Summary 82* Treat everyone with respect and kindness. 83* Be thoughtful in how you communicate. 84* Don’t be destructive or inflammatory. 85* If you encounter an issue, please mail conduct@golang.org. 86