-
Notifications
You must be signed in to change notification settings - Fork 26
code-of-conduct: duplicates removed: report guide #92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sharmi
wants to merge
4
commits into
pythonindia:master
Choose a base branch
from
sharmi:patch-2
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,74 @@ | ||
| --- | ||
| layout: default | ||
| title: Reporting Guide | ||
| header: Reporting Guide | ||
| bloglike: true | ||
| nav: reporting-guide | ||
| --- | ||
|
|
||
| # 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 | ||
|
|
||
| ## License | ||
|
|
||
| This Reporting guide was forked "Django Code of Conduct - Reporting Guide" by Django Software Foundation which is under a Creative Commons Attribution license. | ||
|
|
||
| PyCon India Conference Reporting Guide is licensed under a Creative Commons Attribution 3.0 Unported License. | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has to be changed. Sharmila please use your name over here. Also we will need to add contact information, like mobile no. and email. Please let me know if you would be willing to disclose your mobile no. / email over here.