Changeset - 247061253327
[Not reviewed]
0 2 0
Joshua Simmons - 5 years ago 2017-08-09 22:01:07
i@joshuasimmons.name
remove old contact info
2 files changed with 2 insertions and 2 deletions:
0 comments (0 inline, 0 general)
pinaxcon/templates/static_pages/harassment-procedure-attendee.md
Show inline comments
 
This procedure has been adopted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports)”.
 

	
 
1\. Keep in mind that all conference staff will be wearing a conference t-shirt/button with the word “STAFF” on it (or otherwise clearly marked as staff). The staff will also be prepared to handle the incident. All of our staff are informed of the [code of conduct policy](/code-of-conduct) and guide for handling harassment at the conference. *There will be a mandatory staff meeting onsite at the conference when this will be reiterated.*
 

	
 
2\. Report the harassment incident (preferably in writing) to a conference staff member. All reports are confidential. Please do not disclose public information about the incident until the staff have had sufficient time in which to address the situation. This is as much for your safety and protection as it is the other attendees.
 

	
 
When reporting the event to staff, try to gather as much information as available but do not interview people about the incident. Staff will assist you in writing the report/collecting information.
 

	
 
The important information consists of:
 

	
 
- Identifying information (name/badge number) of the participant doing the harassing
 
- The behavior that was in violation
 
- The approximate time of the behavior (if different than the time the report was made)
 
- The circumstances surrounding the incident
 
- Other people involved in the incident
 

	
 
The staff is well informed on how to deal with the incident and how to further proceed with the situation.
 

	
 
3\. If everyone is presently physically safe, involve law enforcement or security only at a victim's request. If you do feel your safety in jeopardy please do not hesitate to contact local law enforcement by dialing 911. If you do not have a cell phone, you can use any hotel phone or simply ask a staff member.
 

	
 
**Note**: Incidents that violate the Code of Conduct are extremely damaging to the community, and they will not be tolerated. The silver lining is that, in many cases, these incidents present a chance for the offenders, and the community at large, to grow, learn, and become better. North Bay Python staff requests that they be your first resource when reporting a North Bay Python-related incident, so that they may enforce the Code of Conduct and take quick action toward a resolution.
 

	
 
A listing of [North Bay Python staff is located here](/about/staff), including contact phone numbers. If at all possible, all reports should be made directly to [Ewa Jodlowska](mailto:ewa@python.org) (Event Coordinator) or [Jesse Noller](mailto:jnoller@python.org) (PyCon Chair).
...
 
\ No newline at end of file
 
A listing of [North Bay Python staff is located here](/about/staff), including contact phone numbers. If at all possible, all reports should be made directly to Bleep and Bloop.
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/harassment-procedure-staff.md
Show inline comments
...
 
@@ -41,25 +41,25 @@ Allow the alleged harasser to give their side of the story to the staff. After t
 

	
 
Some things for the staff to consider when dealing with Code of Conduct offenders:
 

	
 
- Warning the harasser to cease their behavior and that any further reports will result in sanctions
 
- Requiring that the harasser avoid any interaction with, and physical proximity to, their victim for the remainder of the event
 
- Ending a talk that violates the policy early
 
- Not publishing the video or slides of a talk that violated the policy
 
- Not allowing a speaker who violated the policy to give (further) talks at the event now or in the future
 
- Immediately ending any event volunteer responsibilities and privileges the harasser holds
 
- Requiring that the harasser not volunteer for future events your organization runs (either indefinitely or for a certain time period)
 
- Requiring that the harasser refund any travel grants and similar they received (this would need to be a condition of the grant at the time of being awarded)
 
- Requiring that the harasser immediately leave the event and not return
 
- Banning the harasser from future events (either indefinitely or for a certain time period)
 
- Removing a harasser from membership of relevant organizations
 
- Publishing an account of the harassment and calling for the resignation of the harasser from their responsibilities (usually pursued by people without formal authority: may be called for if the harasser is the event leader, or refuses to stand aside from the conflict of interest, or similar, typically event staff have sufficient governing rights over their space that this isn't as useful)
 

	
 
Give accused attendees a place to appeal to if there is one, but in the meantime the report stands. Keep in mind that it is not a good idea to encourage an apology from the harasser.
 

	
 
It is very important how we deal with the incident publicly. Our policy is to make sure that everyone aware of the initial incident is also made aware that it is not according to policy and that official action has been taken - while still respecting the privacy of individual attendees.  When speaking to individuals (those who are aware of the incident, but were not involved with the incident) about the incident it is a good idea to keep the details out.
 

	
 
Depending on the incident, the conference chair, or designate, may decide to make one or more public announcements. If necessary, this will be done with a short announcement either during the plenary and/or through other channels. No one other than the conference chair or someone delegated authority from the conference chair should make any announcements. No personal information about either party will be disclosed as part of this process.
 

	
 
If some attendees were angered by the incident, it is best to apologize to them that the incident occurred to begin with.  If there are residual hard feelings, suggest to them to write an email to the conference chair or to the event coordinator. It will be dealt with accordingly.
 

	
 
A listing of [North Bay Python staff is located here](/about/staff), including contact phone numbers. If at all possible, all reports should be made directly to [Ewa Jodlowska](mailto:ewa@python.org) (Event Coordinator) or [Jesse Noller](mailto:jnoller@python.org) (PyCon Chair).
...
 
\ No newline at end of file
 
A listing of [North Bay Python staff is located here](/about/staff), including contact phone numbers. If at all possible, all reports should be made directly to Bleep and Bloop.
...
 
\ No newline at end of file
0 comments (0 inline, 0 general)