Skip to content

Commit c833b3a

Browse files
phaltphalt
committed
inital commit
0 parents  commit c833b3a

File tree

5 files changed

+262
-0
lines changed

5 files changed

+262
-0
lines changed

Diff for: ‎LICENCE

+26
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
SOFTWARE
2+
========
3+
4+
Software under the build_template.py file is Copyright (c) 2015, Paul Hallett
5+
6+
All rights reserved.
7+
8+
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
9+
10+
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
11+
12+
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
13+
14+
* Neither the name of Paul Hallett nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
15+
16+
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
17+
18+
19+
CODE OF CONDUCT TEMPLATE
20+
========================
21+
22+
This Code of Conduct was forked from the Pycon US policy[0], which was originally forked from the Geek Feminism wiki, created by the Ada Initiate and other volunteers.[1] which is under a Creative Commons Zero[2] license.
23+
24+
[0] - https://github.com/python/pycon-code-of-conduct
25+
[1] - http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy
26+
[2] - http://creativecommons.org/licenses/by/3.0/

Diff for: ‎Makefile

+2
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
run:
2+
python build_template.py

Diff for: ‎README.md

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# Code of Conduct template
2+
3+
This is an open source generic *code of conduct* template suitable for user groups or conferences.
4+
Do not just copy and paste this code of conduct please read the *How to use* section below to use this document as intended.
5+
6+
## How to use
7+
8+
Copying and pasting this template and announcing you now have a code of conduct is not what this document is intended to be used. Code of Conducts are extremely serious and beneficial statements of your effort to provide a safe and welcoming environment at your events. Thus: the use of this template to build your code of conduct should be taken seriously and the lead organiser or chair of your event or usergroup should take the following steps:
9+
10+
### This template
11+
12+
The best way to use this code of conduct template is to:
13+
14+
1\. Fork or download this code of conduct template
15+
2\. Using a terminal, navigate to the directory of this template.
16+
3\. Use the `make run` command to quickly replace the template tags with your specific content.
17+
4\. Read the code of conduct thoroughly and correct any mistakes or fix any content that may not be relevant to your event.
18+
4\. *Add* content to this code of conduct that may be relevant to your event.
19+
5\. Give this code of conduct to each organiser or staff member involved in running or helping to run your events. Ensure they are all aware of the policies and procedures within.
20+
6\. Publish your code of conduct on a dedicated page and provide links on all associated web pages for your event.
21+
7\. Ensure attendees are aware of the code of conduct by an announcement through appropriate channels (email, social media.)
22+
23+
24+
### At your event
25+
26+
1\. Hold a staff meeting before the even begins and on each subsequent day that the event continues and explain the purpose of the code of conduct to the staff members. All the staff should have read and be aware of the code of conduct. Quiz them if you feel like they may not know.
27+
2\. At the beginning of the event ensure an announcement is made to the congregated attendees of the code of conduct existence and policies.
28+
3\. Provide attendees with copies or url link to the code of conduct.
29+
30+
31+
## Template tags
32+
33+
These are tags within the code of conduct that can be quickly replaced with the
34+
`make run` command or by using a search and replace tool:
35+
36+
- *{{ name }}* - the name of the event or user group.
37+
- *{{description }}* - the description of the event or user group.
38+
- *{{ type }}* - the type of event, such as a meet up or a conference.
39+
- *{{ contact_name }}* - the contact name of the organiser.
40+
- *{{ contact_number }}* - the contact number of the organiser.
41+
- *{{ second_contact_name }}* - the contact name of the second organiser.
42+
- *{{ second_contact_number }}* - the contact number of the second organiser.
43+
- *{{ law_enforcement_number }}* - the local law enforcement phone number.
44+

Diff for: ‎build_template.py

+40
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# -*- coding: utf-8 -*-
2+
from __future__ import unicode_literals
3+
4+
import os
5+
try:
6+
from jinja2 import Template
7+
except:
8+
print('Something went wrong finding jinja!')
9+
print('Please run `sudo easy_install jinja2` and try again.')
10+
11+
try: # Py2 hacks
12+
input = raw_input
13+
except:
14+
pass
15+
16+
PATH = os.path.dirname(os.path.abspath(__file__))
17+
coc_file = os.path.join(PATH, 'code-of-conduct.md')
18+
with open(coc_file, 'r') as f:
19+
template = Template(f.read())
20+
name = input('Event name: ')
21+
description = input('Event description: ')
22+
type = input('Enter the type of event (user group, conference): ')
23+
organiser_name = input('Enter an organiser name: ')
24+
organiser_number = input('Enter their contact number: ')
25+
organiser_2_name = input('Enter another organiser name: ')
26+
organiser_2_number = input('Enter their contact number: ')
27+
law = input('Enter local law enforcement number: ')
28+
template = template.render(
29+
name=name,
30+
description=description,
31+
type=type,
32+
organiser_name=organiser_name,
33+
organiser_number=organiser_number,
34+
organiser_2_name=organiser_2_name,
35+
organiser_2_number=organiser_2_number,
36+
law_enforcement_number=law
37+
)
38+
with open(coc_file, 'w') as f:
39+
f.write(template)
40+
print('All done! Be sure to check the document for spelling mistakes.')

Diff for: ‎code-of-conduct.md

+150
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,150 @@
1+
# Code of Conduct for {{ name }}
2+
3+
{{ description }}
4+
5+
We value the participation of each member of the community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees of {{ name }} are expected to show respect and courtesy to other people throughout the event, whether they are officially part of a {{ name }} event or not.
6+
7+
To make clear what is expected, all delegates/attendees, speakers, exhibitors, organizers and volunteers at any {{ name }} event are required to conform to the following Code of Conduct. Organisers will enforce this code throughout the event and you will be reminded of it at the start of the event and any subsequent days that this event occurs over.
8+
9+
## The Short Version
10+
11+
- {{ name }} is dedicated to providing a harassment-free {{ type }} experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of {{ name }} participants in any form.
12+
13+
- All communication should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery is *not appropriate* for any venue, including talks and socialising.
14+
15+
- Be kind to others. Do not insult or put down other people. Behave professionally. Remember that harassment and sexist, racist, or exclusionary jokes are not appropriate for this {{ type }}.
16+
17+
- Attendees violating these rules may be asked to leave the event without a refund at the sole discretion of the organisers.
18+
19+
In addition to these agreements, {{ name }} wants to be a friendly and welcoming place. We encourage all our attendees to act in the following manner:
20+
21+
- Be friendly and patient.
22+
- Be welcoming towards everyone. This includes new attendees at {{ name }} and especially those who are still learning.
23+
- Be considerate of others and treat them as you wish to be treated.
24+
25+
In short: *be excellent towards each other.*
26+
27+
Thank you for helping make this a welcoming, friendly {{ type }} for all.
28+
29+
## The Longer Version
30+
31+
Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.
32+
33+
Participants asked to stop any harassing behavior are expected to comply immediately.
34+
35+
Exhibitors, sponsors or vendor booths, or similar activities associated with the {{ type }} in anyway at all are also subject to the anti-harassment policy. In particular and if applicable, any exhibitors at the event should not use sexualized images, activities, or other material. No booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
36+
37+
Be careful in the words that you choose. Remember that sexist, racist, and other exclusionary jokes can be offensive to those around you. Excessive swearing and offensive jokes are not appropriate for {{ name }}.
38+
39+
If a participant engages in behavior that violates this code of conduct, the {{ type }} organisers may take any action they deem appropriate, including warning the offender or expulsion from the {{ type }} with no refund.
40+
41+
## Contact Information
42+
43+
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of {{ name }} staff. {{ name }} staff will be pointed out to you at the beginning of the event.
44+
45+
If the matter is especially urgent, please call or contact any of these individuals:
46+
47+
- {{ contact_name }} at {{ contact_number }}
48+
- {{ second_contact_name }} at {{ second_contact_number }}
49+
50+
{{ name }} 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.
51+
52+
## Procedure for Handling Harassment
53+
54+
If you feel like you are being harassed or feel uncomfortable and would like to talk to a member of staff, then please follow the following steps so that we can help you as quickly as possible:
55+
56+
(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)".)
57+
58+
1\. Keep in mind that all {{ name }} staff will be pointed out at the beginning of the event and should be in identifying uniform. The staff will also be prepared to handle the incident. All of our staff are informed of the this code of conduct policy and guide
59+
for handling harassment at the conference.
60+
61+
2\. Report the harassment incident (preferably in writing) to a staff member. All reports
62+
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.
63+
64+
When reporting the event to staff, try to gather as much information as available but do not
65+
interview people about the incident. Staff will assist you in writing the report/collecting information.
66+
67+
The important information consists of:
68+
69+
- Identifying information (name/badge number) of the participant doing the harassing.
70+
- The behavior that was in violation.
71+
- The approximate time of the behavior (if different than the time the report was made).
72+
- The circumstances surrounding the incident.
73+
- Other people involved in the incident.
74+
75+
The staff are well informed on how to deal with the incident and how to further proceed with the situation.
76+
77+
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 {{ law_enforcement_number }}. If you do not have a cell phone, you can simply ask a staff member.
78+
79+
**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. {{ name }} staff requests that they be your first resource when reporting a {{ name }}-related incident, so that they may enforce the Code of Conduct and take quick action toward a resolution.
80+
81+
If at all possible, all reports should be made directly to the {{ name }} organisers mentioned above.
82+
83+
## Staff Procedure for incident handling
84+
85+
All staff for {{ name }} will have been briefed on the following procedures for helping you to help with your safety.
86+
87+
(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)".)
88+
89+
Please make sures that you and other organisers have read this document in its entirety to ensure everyone helping to run this is event is aware of the code of conduct and it's procedures.
90+
91+
Try to get as much of the incident in writing from the reporter. If you cannot, transcribe it yourself as it was told to you. The important information to gather include the following:
92+
93+
- Identifying information (name/badge number) of the participant doing the harassing.
94+
- The behavior that was in violation.
95+
- The approximate time of the behavior (if different than the time the report was made).
96+
- The circumstances surrounding the incident.
97+
- Other people involved in the incident.
98+
99+
Prepare an initial response to the incident. This initial response is very important and will set the tone for {{ name }}. Depending on the severity/details of the incident, please follow these guidelines:
100+
101+
- If there is any general threat to attendees or the safety of anyone including staff is in doubt, summon security or police.
102+
- Offer the victim a private place to sit.
103+
- Ask "is there a friend or trusted person who you would like to be with you?" (if so, arrange for someone to fetch this person).
104+
- Ask them "how can I help?".
105+
- Provide them with your list of emergency contacts if they need help later.
106+
- If everyone is presently physically safe, involve law enforcement or security only at a victim's request.
107+
108+
There are also some guidelines as to what not to do as an initial response:
109+
110+
- Do not overtly invite them to withdraw the complaint or mention that withdrawal is OK. This suggests that you want them to do so, and is therefore coercive. "If you're OK with it [pursuing the complaint]" suggests that you are by default pursuing it and is not coercive.
111+
- Do not ask for their advice on how to deal with the complaint. This is a staff responsibility.
112+
- Do not offer them input into penalties. This is the staff's responsibility.
113+
114+
Once something is reported to a staff member, immediately meet with the event chair and/or event coordinator. The main objectives of this meeting is to find out the following:
115+
116+
- What happened?
117+
- Are we doing anything about it?
118+
- Who is doing those things?
119+
- When are they doing them?
120+
121+
After the staff meeting and discussion, have a staff member (preferably the event chair or event coordinator if available) communicate with the alleged harasser. Make sure to inform them of what has been reported about them.
122+
123+
Allow the alleged harasser to give their side of the story to the staff. After this point, if the report stands, let the alleged harasser know what actions will be taken against them.
124+
125+
Some things for the staff to consider when dealing with Code of Conduct offenders:
126+
127+
- Warning the harasser to cease their behavior and that any further reports will result in sanctions.
128+
- Requiring that the harasser avoid any interaction with, and physical proximity to, their victim for the remainder of the event.
129+
- Ending a talk that violates the policy early.
130+
- Not publishing the video or slides of a talk that violated the policy.
131+
- Not allowing a speaker who violated the policy to give (further) talks at the event now or in the future.
132+
- Immediately ending any event volunteer responsibilities and privileges the harasser holds.
133+
- Requiring that the harasser not volunteer for future events your organization runs (either indefinitely or for a certain time period).
134+
- 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).
135+
- Requiring that the harasser immediately leave the event and not return.
136+
- Banning the harasser from future events (either indefinitely or for a certain time period).
137+
- Removing a harasser from membership of relevant organizations.
138+
- 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).
139+
140+
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.
141+
142+
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.
143+
144+
Depending on the incident, the event 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 event chair or someone delegated authority from the event chair should make any announcements. No personal information about either party will be disclosed as part of this process.
145+
146+
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.
147+
148+
## License
149+
150+
This Code of Conduct was forked from the [Pycon US policy](https://github.com/python/pycon-code-of-conduct), which was originally forked from the [Geek Feminism wiki, created by the Ada Initiate and other volunteers.](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy) which is under a [Creative Commons Zero](http://creativecommons.org/licenses/by/3.0/) license.

0 commit comments

Comments
 (0)