From 90934875ede1a2a17b8d21cc6f2205bd7f0bf083 Mon Sep 17 00:00:00 2001 From: Sharmila G Sivakumar Date: Wed, 29 May 2019 16:05:07 +0530 Subject: [PATCH 1/2] Code of Conduct updated with reporting guide I am yet to add the License. Will do by tonight. Please comment. --- WEBSITE-CODE-OF-CONDUCT.md | 153 ++++++++++++++++++++++++++----------- 1 file changed, 109 insertions(+), 44 deletions(-) diff --git a/WEBSITE-CODE-OF-CONDUCT.md b/WEBSITE-CODE-OF-CONDUCT.md index 49cc819..4991bc8 100644 --- a/WEBSITE-CODE-OF-CONDUCT.md +++ b/WEBSITE-CODE-OF-CONDUCT.md @@ -1,62 +1,127 @@ -# Contributor Covenant Code of Conduct +# Code Of Conduct -## Our Pledge +## PyCon India 2019 - Code of Conduct -In 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, nationality, personal appearance, race, religion, or sexual identity and orientation. +PyCon India is a community organized conference intended for advocating the use and adoption of the Python programming language in India. It is also a platform for fostering networking and collaboration among the Python developer community in India. -## Our Standards +We value the participation of every member of the Python community and want all attendees to have an enjoyable and rewarding experience. Diversity is one of our biggest strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to. To make clear what is expected, all delegates/attendees, speakers, exhibitors, organizers and volunteers at PyCon India are required to conform to the following Code of Conduct. Organizers will enforce this code throughout the event. -Examples of behavior that contributes to creating a positive environment include: -* Using welcoming and inclusive language -* Being respectful of differing viewpoints and experiences -* Gracefully accepting constructive criticism -* Focusing on what is best for the community -* Showing empathy towards other community members -Examples of unacceptable behavior by participants include: +### Where +This Code of Conduct applies to the venue of PyCon India 2019 Conference, pre-event & post-event informal gatherings, related online forums and all conference related events, whether officially organized by PyCon India or not. -* The use of sexualized language or imagery and unwelcome sexual attention or advances -* Trolling, insulting/derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or electronic address, without explicit permission -* Other conduct which could reasonably be considered inappropriate in a professional setting -## Our Responsibilities +### Aim +PyCon India 2019 welcomes and is dedicated to providing a harassment-free conference experience for everyone, regardless of age, gender, sexual orientation, physical appearance, disability, neurotype, race, religion, political opinion, culture or employment. We don’t tolerate harassment of attendees in any form. -Project 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. +We believe in the broad spectrum of individual and collective experience and in the inherent dignity of all people. We believe that amazing things happen when people from different worlds and world-views approach each other to create a conversation. -Project 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. +### Be the best you can be +* Be generous, sensitive, understanding and respectful to your fellow Pythonistas, staff and workers. +* Seek out newcomers and help them feel like they belong. +* Listen with empathy when someone has a different perspective. +* Talk to someone if you notice that something could be better. +* All communication should be appropriate for a professional audience, including people from many different backgrounds. -## Scope +### Please refrain from -This 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. +* Offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion +* Violent threats or language directed against another person. +* Swearing, insults and discriminatory jokes and language. +* Deliberate intimidation, stalking, following, harassing photography or recording +* Sustained disruption of talks or other event +* Posting sexually explicit or violent material. Sexual language or imagery is inappropriate for all aspects of the conference, including talks +* Posting (or threatening to post) other people's personally identifying information ("doxing"). +* Personal insults, especially those using racist or sexist terms. +* Unwelcome sexual attention or inappropriate physical contact. +* Advocating for, or encouraging, any of the above behavior. +* Repeated harassment of others. In general, if someone asks you to stop, then stop. -## Enforcement -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the -project team at contact@in.pycon.org. The project team will review and investigate all complaints, and -will respond in a way that it deems appropriate to the circumstances. The project team is obligated to -maintain confidentiality with regard to the reporter of an incident. Further details of specific -enforcement policies may be posted separately. -Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary -or permanent repercussions as determined by other members of the project's leadership. +We have zero tolerance on harassment of conference participants in any form, including, but not limited to the activities mentioned here. -## Attribution +Participants asked to stop any harassing behavior are expected to comply immediately. -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] +### Code for Speakers -[homepage]: http://contributor-covenant.org -[version]: http://contributor-covenant.org/version/1/4/ +Sexual language or imagery is inappropriate for your talks or slides. Refrain from using sexist, racist or exclusionary language anywhere in your content. + +### Code for Exhibitors and Sponsors + +Exhibitors in the expo hall, sponsor or vendor booths, are subject to the anti-harassment policy. + +Exhibitors should not use sexualized images, activities, or other material. + +Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment. + +### Code for Participants + +Be kind and sensitive to the people around you and avoid any kind of offensive behavior. Sexist, racist or any other form of exclusionary or offensive jokes or excessive public swearing are not appropriate at any venue of PyCon India. + + +## Reporting Guide + +If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff. Conference staff will be wearing “PyCon India Staff” or “PyCon India Volunteer” badges. + +All reports will be kept confidential. In some cases we may determine that a public statement will need to be made. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. + +If you believe anyone is in physical danger, please notify appropriate law enforcement first. If you are unsure what law enforcement agency is appropriate, please include this in your report and we will attempt to notify them. + +If you are unsure whether the incident is a violation, or whether the space where it happened is covered by this Code of Conduct, we encourage you to still report it. We would much rather have a few extra reports where we decide to take no action, rather than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. And knowing about incidents that are not violations, or happen outside our spaces, can also help us to improve the Code of Conduct or the processes surrounding it. + +### In your report please include: + +* Your contact info (so we can get in touch with you if we need to follow up) +* Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well. +* When and where the incident occurred. Please be as specific as possible. +* Your account of what occurred. If there is a publicly available record (e.g. a mailing list archive or a public IRC logger) please include a link. +* Any extra context you believe existed for the incident. +* If you believe this incident is ongoing. +* Any other information you believe we should have. + +### What happens after you file a report? + +The working group will immediately meet to review the incident and determine: + +* What happened. +* Whether this event constitutes a code of conduct violation. +* Who the bad actor was. +* Whether this is an ongoing situation, or if there is a threat to anyone's physical safety. + +Conference staff will be happy to help participants contact venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. We value your attendance. + +If this is determined to be an ongoing incident or a threat to physical safety, the staff's immediate priority will be to protect everyone involved. This means we may delay an "official" response until we believe that the situation has ended and that everyone is physically safe. + +Once the working group has a complete account of the events they will make a decision as to how to response. Responses may include: + + * Nothing (if we determine no violation occurred). + * A private reprimand from the working group to the individual(s) involved. + * A public reprimand. + * Expulsion from the conference with no refund. + * A permanent or temporary ban from some or all PyCon India spaces (mailing lists, IRC, etc.) + * A request for a public or private apology. + +We'll respond within one week to the person who filed the report with either a resolution or an explanation of why the situation is not yet resolved. + +Once we've determined our final action, we'll contact the original reporter to let them know what action (if any) we'll be taking. We'll take into account feedback from the reporter on the appropriateness of our response, but we don't guarantee we'll act on it. + +Finally, the PyCon India Staff will make a report on the situation. + +What if your report concerns a possible violation by a staff member? + + +In that case, you can make a report directly to any or all of the current (vice/co) chairs of the Code of Conduct committee. Their e-mail addresses are listed on the Code of Conduct Committee page. The chairs will follow the usual enforcement process with the other members, but will exclude the member(s) that the report concerns from any discussion or decision making. + +If your report concerns all current (vice/co) chairs of the committee, please send your report directly to the PSF Board of Directors at psf@python.org instead. + + + +Thank you for helping to make PyCon India a welcoming, friendly event for all. + +## Contact Information + + + +If the matter is especially urgent, you may also ask to be put in touch with the conference chair - Vijay Kumar From e9ab59354867625916ab11067039c33acaaa0fb9 Mon Sep 17 00:00:00 2001 From: Sharmila G Sivakumar Date: Thu, 30 May 2019 00:55:40 +0530 Subject: [PATCH 2/2] Update WEBSITE-CODE-OF-CONDUCT.md --- WEBSITE-CODE-OF-CONDUCT.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/WEBSITE-CODE-OF-CONDUCT.md b/WEBSITE-CODE-OF-CONDUCT.md index 4991bc8..c1dd5ff 100644 --- a/WEBSITE-CODE-OF-CONDUCT.md +++ b/WEBSITE-CODE-OF-CONDUCT.md @@ -121,7 +121,12 @@ If your report concerns all current (vice/co) chairs of the committee, please se Thank you for helping to make PyCon India a welcoming, friendly event for all. ## Contact Information +If the matter is especially urgent, you may also ask to be put in touch with the conference chair - Vijay Kumar +## License +This Code of Conduct was forked from +1. "PSF Code of Conduct" by Python Software Foundation which is under a Creative Commons Attribution 3.0 Unported License +2. "Django Code of Conduct - Reporting Guide" by Django Software Foundation which is under a Creative Commons Attribution license. -If the matter is especially urgent, you may also ask to be put in touch with the conference chair - Vijay Kumar +PyCon India Conference Code of Conduct is licensed under a Creative Commons Attribution 3.0 Unported License.