Code of conduct for the Code Fellows community
Switch branches/tags
Nothing to show
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
_layouts
assets/css added gh-pages theme assets (#9) Oct 24, 2018
LICENSE Initial commit Sep 24, 2015
README.md fixed typo on line 19 Mar 20, 2017
_config.yml

README.md

Code of Conduct

This code of conduct outlines our expectations for participants within the Code Fellows community, as well as steps for reporting unacceptable behavior. We are committed to providing a welcoming and inspiring community for all and expect our code of conduct to be honored.

Anyone who violates this code of conduct may be immediately removed from any current classes, refunded according to the terms of their student contract, and banned from the community.

Community Goal: Be Kind

Our community of staff, instructors, and current & former students strives to be kind. This is the guiding principle for conducting oneself within the Code Fellows community.

While kindness can be generally understood, we recognize that kindness in a professional setting means (but is not limited to):

  • Be friendly and patient
  • Be welcoming: We strive to be a community who welcomes and supports people of all backgrounds and identities. This includes, but is not limited to, members of any race, ethnicity, culture, national origin, color, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.
  • Be considerate: Your work will be used by other people and you in turn will depend on the work of others. Any decision you take will affect users and colleagues and you should take those consequences into account when making decisions. Remember that we’re a worldwide community, so you might not be communicating in someone else’s primary language.
  • Give attribution, engage honestly: Since our code often depends on the work and assistance of others, we will be sure to give proper attribution. As members of the community, we agree to represent ourselves truthfully, claim only work that is our own, properly attribute collaborations, and engage honestly in all assignments.
  • Be respectful: Not all of us will agree all of the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. Your presence may not impact other's ability to learn.
  • Be careful in the words that we choose: We are a community of learning professionals and we conduct ourselves professionally. Be kind to others both within the community and beyond the community. Do not insult, minimize, marginalize, or put down other participants, cultures, or sub-cultures. Contribute positively to the learning environment.
  • Try to understand why we disagree: Disagreements, both social and technical, happen all the time. It is important that we resolve disagreements and differing views constructively. Remember that we’re different. The strength of our community comes from its diversity—people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.
  • Harassment and exclusionary behavior aren’t acceptable.

Definitions

Plagiarism

Plagiarism is the re-use of someone else's code, without the permission or license of the author. Claiming someone else's work as your own is disrespectful to the author and to your learning process. "Cargo culting," or utilizing the techniques of another without applying your own thinking, is also considered plagiarism.

Violating the terms of a license in a professional software development setting can result in lawsuits and endanger businesses. Doing so in the classroom can result in loss of assignment points, bad references from instructors, removal from all Code Fellows courses, and community bans. Consequences will depend on severity and are at the discretion of the conduct review panel.

Attribution

We encourage an open-source work ethic, and we solve problems collaboratively. The difference between properly attributed work and plagiarized submissions is found in citing source material and permission of the original author.

Proper attribution includes a description of what code was used or what help was given. A link back to the original source material or ideas should be included whenever possible. This belongs in a section titled "Attributions" of the README file for the relevant code.

Please note: an online code repository that has no license is presumed to be closed source and should not be used as a reference. Please include a license file in your own publicly published code.

Harassment

We share a common understanding of what constitutes harassment, as it applies to a professional setting. Although this list cannot be exhaustive, we explicitly honor diversity in age, gender, gender identity or expression, culture, ethnicity, language, national origin, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate discrimination based on any of the protected characteristics above, including participants with disabilities.

Harassment includes, but is not limited to:

  • Offensive comments (or "jokes") related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro-typicality, physical appearance, body size, race, age, regional discrimination, political or religious affiliation
  • Unwelcome comments regarding a person’s lifestyle choices and practices, including those related to food, health, parenting, drugs, and employment
  • Deliberate misgendering. This includes deadnaming or persistently using a pronoun that does not correctly reflect a person’s gender identity. You must address people by the name they give you when not addressing them by their username or handle.
  • Physical contact and simulated physical contact (e.g., textual descriptions like “hug” or “backrub”) without consent or after a request to stop
  • Threats of violence, both physical and psychological
  • Incitement of violence towards any individual, including encouraging a person to engage in self-harm
  • Deliberate intimidation
  • Stalking or following
  • Harassing photography or recording, including logging online activity for harassment purposes
  • Sustained disruption of discussion
  • Unwelcome sexual attention, including gratuitous or off-topic sexual images or behavior
  • Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others
  • Continued one-on-one communication after requests to cease
  • Deliberate “outing” of any aspect of a person’s identity without their consent, except as necessary to protect others from intentional abuse
  • Publication of non-harassing private communication

We encourage everyone to participate and are committed to building a community for all. Although we will fail at times, we seek to treat everyone both as fairly and equally as possible. Whenever a participant has made a mistake, we expect them to take responsibility for it. If someone has been harmed or offended, it is our responsibility to listen carefully and respectfully, and to do our best to right the wrong.

Examples

We don't require students to participate in formal conduct training. Rather, we rely on common sense and a commitment to follow these guidelines. To provide greater clarity, here are some examples of how this should be interpreted:

  • A high-five is most welcome, as both parties are opting in. Avoid surprise hugs, back rubs, and general one-directional physical contact.
  • If someone solicits feedback, focus on the material. Do not comment on physical appearance.
  • In a learning environment, you'll find you have knowledge or insight someone else has not yet attained. Do not make others feel bad for not yet learning what you may find obvious. Avoid statements like "You haven't heard of Foo library?!?!" or, "Uh, obviously, you should just concat the strings."
  • Our community constitutes people from a wide array of backgrounds. This is a great strength. Talk to people about their backgrounds and histories as a learner and a listener. "Tell me more about that," is a better option than, "Well, that's not what I experienced."
  • Copying code from Stack Overflow, blogs, Google searches, online tutorials, etc., and pasting it into your own project is considered plagiarism. If you'd like to use someone else's code, at least retype the relevant portions yourself, and include a link back to the original in your project's README file.

Reporting Issues

Our community prioritizes marginalized people’s safety over privileged people’s comfort. We will not act on complaints regarding:

  • ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’
  • Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you”
  • Refusal to explain or debate social justice concepts
  • Communicating in a ‘tone’ you don’t find congenial
  • Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or assumptions
  • Diversity Statement

If you experience or witness unacceptable behavior—or have any other concerns—please report it by contacting us via conduct@codefellows.com. All reports will be handled with discretion. In your report please include:

  • Your contact information.
  • Names (real, nicknames, or pseudonyms) of any individuals involved. If there are additional witnesses, please include them as well.
  • Your account of what occurred and if you believe the incident is ongoing. If there is a publicly available record (e.g. Slack channel, a mailing list archive or a public IRC logger), please include a link, reference, or screenshot.
  • Any additional information that may be helpful.

After filing a report, a representative will contact you personally, review the incident, follow up with any additional questions, and make a decision as to how to respond. The response team has broad latitude to remove an offending student from class, or offer a warning, depending on the severity of the offense. No more than 1 warning will be given; a second offense will result in release from class, a refund according to the student contract, and a community ban.

If the person who is harassing you is part of the response team, they will recuse themselves from handling your incident. If the complaint originates from a member of the response team, a different member of the response team will handle it. We will respect confidentiality requests for the purpose of protecting victims of abuse.

Attribution & Acknowledgements

We all stand on the shoulders of giants across many open source communities. We’d like to thank the communities and projects that established codes of conduct and diversity statements as our inspiration, like Todo Group, Python, Contributor Covenant, Geek Feminism, and Citizen Code of Conduct.