ACM@USC Code of Conduct
Why Have a Code of Conduct?
ACM@USC's community includes people from many different backgrounds. The ACM@USC 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 ACM@USC 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.
Where Does the Code of Conduct Apply?
If you join in or contribute to the ACM@USC 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 ACM@USC groups, in-person meetings, and events, including:
- The ACM@USC GroupMe
- The ACM@USC GitLab
- Weekly Meetings
Other ACM@USC 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 ACM@USC community should aspire.
- Be friendly and welcoming
- Be patient
- Remember that people have varying communication styles and that not everyone is using their native language (meaning and tone can be lost in translation).
- Be thoughtful
- Productive communication requires effort. Think about how your words will be interpreted.
- Remember that sometimes it is best to refrain entirely from commenting.
- Be respectful
- In particular, respect differences of opinion.
- Be charitable
- Interpret the arguments of others in good faith, do not seek to disagree.
- When we do disagree, try to understand why.
- Avoid destructive behavior:
- Derailing: stay on topic; if you want to talk about something else, start a new conversation.
- Unconstructive criticism: don't merely condemn the current state of affairs; offer—or at least solicit—suggestions as to how things may be improved.
- Snarking (pithy, unproductive, sniping comments)
- Discussing potentially offensive or sensitive issues; this all too often leads to unnecessary conflict.
- Microaggressions: brief and commonplace verbal, behavioral, and environmental indignities that communicate hostile, derogatory or negative slights and insults to a person or group.
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 ACM@USC spaces:
- Expressing or provoking:
- insulting, demeaning, hateful, or threatening remarks;
- discrimination based on age, nationality, race, (dis)ability, gender (identity or expression), sexuality, religion, or similar personal characteristic;
- bullying or systematic harassment;
- unwelcome sexual advances, including sexually explicit content.
- Excessive advertisement for unnecessary or non-beneficial commercial products and services.
- Posting spam-like content that disrupts the environment of the community.
Moderation & Enforcement
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.
- On your first offense, you will receive a written notice from one of our community moderators. Depending on the degree of the reported behavior, you may be asked to apologize, either in public or directly to the party that you have offended.
- On a second offense, you will be temporarily removed from the community. The period of the temporary ban may vary from 3 days to a month, decided based on the seriousness of the reported behavior. Please note that this ban does not indicate that you are no longer welcomed in the community - it represents an official warning for your behavior.
- On a third offense, you may be asked to leave the community. Your account may be suspended for an indefinite amount of time, and you may be publicly identified.
This procedure only serves as a general guideline for moderation & enforcement of our community conduct. Under all circumstances, the Working Group or ACM@USC's staff members may take any action we deem appropriate, including immediate removal from the community. Being banned from the ACM@USC 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 at email@example.com.
The Code of Conduct Working Group is a group of people that represent the ACM@USC community. They are responsible for handling conduct-related issues. Their purpose is to de-escalate conflicts and try to resolve issues to the satisfaction of all parties. They are:
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.
- Email firstname.lastname@example.org
- Your message will reach the Working Group.
- Reports are confidential within the Working Group.
- Should you choose to remain anonymous then the Working Group cannot notify you of the outcome of your report.
- You may contact a member of the group directly if you do not feel comfortable contacting the group as a whole. That member will then raise the issue with the Working Group as a whole, preserving the privacy of the reporter (if desired).
- If your report concerns a member of the Working Group they will be recused from Working Group discussions of the report.
- The Working Group will strive to handle reports with discretion and sensitivity, to protect the privacy of the involved parties, and to avoid conflicts of interest.
- You should receive a response within 48 hours (likely sooner). (Should you choose to contact a single Working Group member, it may take longer to receive a response.)
- The Working Group will meet to review the incident and determine what happened.
- With the permission of person reporting the incident, the Working Group may reach out to other community members for more context.
- The Working Group will reach a decision as to how to act. These may include:
- A request for a private or public apology.
- A private or public warning.
- An imposed vacation (for instance, asking someone to abstain for a week from group events).
- A permanent or temporary ban from some or all ACM@USC spaces.
- The Working Group will reach out to the original reporter to let them know the decision.
- Appeals to the decision may be made to the Working Group, or to any of its members directly.
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. Bans and other forceful measures are to be employed only as a last resort.
Changes to the Code of Conduct (including to the members of the Working Group) should be proposed by creating an issue or making a pull request to this document.
- Treat everyone with respect and kindness.
- Be thoughtful in how you communicate.
- Don't be destructive or inflammatory.
- If you encounter an issue, please mail email@example.com.
This was adapted from Hack Club's Code of Conduct. It is to be noted that many parts of Hack Club's Code of Conduct are adopted from the Code of Conduct documents of the Go, Django, FreeBSD, and Rust projects.