Changeset - 247061253327
[Not reviewed]
0 2 0
Joshua Simmons - 4 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
...
 
@@ -11,13 +11,13 @@ 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
...
 
@@ -53,13 +53,13 @@ Some things for the staff to consider when dealing with Code of Conduct offender
 
- 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)