Wack Club's community includes people from many different backgrounds. The Wack Club contributors are committed to providing a friendly, safe, and welcoming environment for all, regardless of age, disability, gender, nationality, race, religion, sexuality, or similar personal characteristic.
The 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 communicate effectively, productively, and respectfully.
The second goal is to provide a mechanism for resolving conflicts in the community when they arise.
The third goal of the Code of Conduct is to make our community welcoming to people from different backgrounds. Diversity is critical in order for us to build a thriving community; for Wack Club to be successful, it needs hackers from all backgrounds.
With that said, a healthy community must allow for disagreement and debate. The Code of Conduct is not a mechanism for people to silence others with whom they disagree.
If you join in or contribute to the Wack Club ecosystem in any way, you are encouraged to follow the Code of Conduct while doing so.
Explicit enforcement of the Code of Conduct applies to all official online Wack Club groups, in-person meetings, and events including:
Other Wack Club groups (such as hackathons, conferences, meetups, and other unofficial forums) are encouraged to adopt this Code of Conduct. Those groups must provide their own moderators and/or working group (see below).
These are the values to which people in the Wack Club community should aspire.
People 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.
These actions are explicitly forbidden in Wack Club spaces:
Please understand that speech and actions have consequences, and unacceptable behavior will not be tolerated. When you participate in areas where the code of conduct applies, you should act in the spirit of the "Hacker values". If you conduct yourself in a way that is explicitly forbidden by the Code of Conduct, you will be warned and asked to stop, and your messages may be removed by community moderators. Repeated offenses may result in a temporary or permanent ban from the community.
This procedure only serves as a general guideline for moderation & enforcement of our community conduct. Under all circumstances, the Working Group or Wack Club's staff members may take any action we deem appropriate, including immediate removal from the community. Being banned from the Wack Club community may also prevent you from participating in our community events, including but not restricted to: local club meetings, hackathons, or challenges.
Please understand that we will not restrict your ability to contact the Code of Conduct working group under any circumstance. If you have any questions or concerns about our decision, please reach out to us directly. If your Slack account is under suspension, email us directly at firstname.lastname@example.org.
The Working Group is responsible for handling conduct-related issues. Their mission is to de-escalate conflicts and try to resolve issues to the satisfaction of all parties. For all projects related to and/or maintained by Wack Club HQ, the Working Group is made up of the Wack Club staff team and Community team. The specific team member(s) handling each violation depend on the location and nature of the issue.
If you encounter a conduct-related issue, you should report it to the Working Group using the process described below. Do not post about the issue publicly or try to rally sentiment against a particular individual or group.
Note that the goal of the Code of Conduct and the Working Group is to resolve conflicts in the most harmonious way possible. We hope that in most cases issues may be resolved through polite discussion and mutual agreement. Bannings and other forceful measures are to be employed only as a last resort.
Changes to the Code of Conduct should be proposed by creating an issue or making a pull request to this document.
This was adapted from Go's Code of Conduct. It is to be noted that many parts of Go's Code of Conduct are adopted from the Code of Conduct documents of the Django, FreeBSD, and Rust projects.