-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathcode-of-conduct.html
258 lines (246 loc) · 21.6 KB
/
code-of-conduct.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
<!DOCTYPE html>
<html>
<head>
<title>PHPConf.Asia 2018</title>
<meta charset="UTF-8">
<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/materialize/1.0.0-alpha.4/css/materialize.min.css">
<link type="text/css" rel="stylesheet" href="/styles/main-20180401.css" media="screen,projection" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<link rel="apple-touch-icon" sizes="57x57" href="/icons/apple-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="/icons/apple-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="/icons/apple-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="/icons/apple-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="/icons/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="/icons/apple-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="/icons/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="/icons/apple-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="/icons/apple-icon-180x180.png">
<link rel="icon" type="image/png" sizes="192x192" href="/icons/android-icon-192x192.png">
<link rel="icon" type="image/png" sizes="32x32" href="/icons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="96x96" href="/icons/favicon-96x96.png">
<link rel="icon" type="image/png" sizes="16x16" href="/icons/favicon-16x16.png">
<link rel="manifest" href="/manifest.json">
<meta name="msapplication-TileColor" content="#ffffff">
<meta name="msapplication-TileImage" content="/icons/ms-icon-144x144.png">
<meta name="theme-color" content="#ffffff">
<meta name="description" content="PHPConf.Asia - The Pan-Asian PHP conference!" />
<meta property="og:title" content="PHPConf.Asia 2018" />
<meta property="og:type" content="website" />
<meta property="og:url" content="https://2018.phpconf.asia/" />
<meta property="og:image" content="https://2018.phpconf.asia/images/slides1.jpg" />
<meta property="og:site_name" content="PHPConf.Asia" />
<meta property="fb:admins" content="711713493" />
<meta property="og:description" content="The Pan-Asian PHP conference! Conference days are on 27th to 28th September 2018. Workshops days are on 26 and 29 Sept. CFP opens now!" />
<meta name="twitter:card" content="summary" />
<meta name="twitter:site" content="@PHPConfAsia" />
<meta name="twitter:domain" content="phpconf.asia" />
<meta name="twitter:description" content="The Pan-Asian PHP conference! Conference days are on 27th to 28th September 2018. Workshops days are on 26 and 29 Sept. CFP opens now!" />
<meta name="twitter:image" content="https://2018.phpconf.asia/images/phpconfasia-logo.png" />
<meta itemprop="image" content="https://2018.phpconf.asia/images/phpconfasia-logo.png" />
<script>
(function(w, d, s, l, i) {
w[l] = w[l] || [];
w[l].push({
'gtm.start': new Date().getTime(),
event: 'gtm.js'
});
var f = d.getElementsByTagName(s)[0],
j = d.createElement(s),
dl = l != 'dataLayer' ? '&l=' + l : '';
j.async = true;
j.src =
'https://www.googletagmanager.com/gtm.js?id=' + i + dl;
f.parentNode.insertBefore(j, f);
})(window, document, 'script', 'dataLayer', 'GTM-N53PK2F');
</script>
</head>
<body>
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-N53PK2F"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<div class="navbar-fixed">
<nav>
<div class="nav-wrapper">
<a href="/" class="brand-logo hide-on-med-and-down"><span>PHPConf.Asia</span></a>
<a href="/" class="brand-logo center hide-on-large-only"><span>PHPConf.Asia</span></a>
<a href="#" data-target="mobile-nav" class="sidenav-trigger"><i class="material-icons">menu</i></a>
<ul class="right hide-on-med-and-down">
<li><a href="/">Home</a></li>
<li><a href="https://phpconfasia2018.codecraft.com.sg" target="_blank">Tickets</a></li>
<li><a href="/#schedule">Schedule</a></li>
<li><a href="/#venue">Venue</a></li>
<li><a href="/#sponsors">Sponsors</a></li>
<li><a href="/#speakers">Speakers</a></li>
<li><a href="/#singapore">About Singapore</a></li>
<li class="active"><a href="/code-of-conduct.html">Code of Conduct</a></li>
<li><a href="https://twitter.com/phpconfasia" target="_blank">Twitter</a></li>
<li><a href="https://2016.phpconf.asia" target="_blank">2016</a></li>
</ul>
</div>
<div class="row date-details hide-on-med-and-down z-depth-1">
<div class="col s12 right-align">
<h5 class="red-text">Workshops on 26<sup>th</sup> & 29<sup>th</sup> September, 2018 | Conference on 27<sup>th</sup> & 28<sup>th</sup> September, 2018</h5>
</div>
</div>
</nav>
</div>
<ul class="sidenav" id="mobile-nav">
<li><a href="/">Home</a></li>
<li><a href="https://phpconfasia2018.codecraft.com.sg" target="_blank">Tickets</a></li>
<li><a href="/#schedule">Schedule</a></li>
<li><a href="#venue">Venue</a></li>
<li><a href="/sponsorship.html">Sponsors</a></li>
<li><a href="#speakers">Speakers</a></li>
<li><a href="#singapore">About Singapore</a></li>
<li><a href="/code-of-conduct.html">Code of Conduct</a></li>
<li><a href="https://twitter.com/phpconfasia" target="_blank">Twitter</a></li>
<li><a href="https://2016.phpconf.asia" target="_blank">2016</a></li>
</ul>
<div class="main">
<div class="parallax-container">
<div class="parallax"><img src="/images/parallax1.jpg"></div>
</div>
<div class="container">
<div class="section row">
<div class="col s12">
<h3>Code of Conduct</h3>
<p><strong>PHPConf.Asia</strong> is a Pan-Asian conference aimed at spreading the adoption, knowledge and professionalism of PHP and its derivative technologies in the South East Asia developer community through talks, collaborations
and networking.</p>
<p>We value each individual speaker, participant and member of our organising team – regardless of gender, language, race, religion, nationality, disability, appearance or sexual orientation.</p>
<p>We ask everyone attending the conference to respect each other, to provide an inclusive and safe environment where everyone can feel welcomed, participate, and learn together in peace and harmony.</p>
<h4>Definitions</h4>
<p>In view of our Asian setting, the following non-exclusive list of behaviour are construed as harassment:</p>
<ul>
<li>Physical contact and simulated physical contact (eg, textual descriptions like “*hug*” or “*backrub*”) without consent or after a request to stop.</li>
<li>Offensive comments related to race, religion, gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance</li>
<li>Gratuitous or off-topic sexual images or behaviour in spaces where they’re not appropriate</li>
<li>Threats of violence</li>
<li>Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm</li>
<li>Deliberate intimidation</li>
<li>Stalking or following</li>
<li>Harassing photography or recording, including logging online activity for harassment purposes</li>
<li>Sustained disruption of discussion</li>
<li>Unwelcome sexual attention</li>
<li>Pattern of inappropriate social contact, such as requesting/assuming inappropriate levels of intimacy with others</li>
<li>Continued one-on-one communication after requests to cease</li>
<li>Publication of non-harassing private communication</li>
</ul>
<p>Be careful in the words that you choose. Excessive swearing and offensive jokes are not appropriate for PHPConf.Asia.</p>
<p>If a participant engages in behaviour that violates this code of conduct, the conference organisers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund or reporting
them to the police.</p>
<h4>Reporting</h4>
<p>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 have “organiser” badges on their lanyard.</p>
<h5>Attendee Procedure for Incident Handling</h5>
<p>1. Keep in mind that all conference staff will be wearing a badge on their lanyard with “Organiser” on it. The staff will also be prepared to handle the incident. All of our staff are informed of the code of conduct policy and guide
for handling harassment at the conference.</p>
<p>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.</p>
<p>The important information consists of:</p>
<ul class="styled">
<li>Identifying information (name/badge number) of the participant doing the harassing</li>
<li>The behaviour that was in violation</li>
<li>The approximate time of the behaviour (if different than the time the report was made)</li>
<li>The circumstances surrounding the incident</li>
<li>Other people involved in the incident</li>
</ul>
<p>The staff is well informed on how to deal with the incident and how to further proceed with the situation.</p>
<p>3. If everyone is presently physically safe, involve police or security only at a victim’s request. If you do feel your safety in jeopardy please do not hesitate to contact the police by dialling 999. If you do not have a mobile
phone, please ask a member of venue staff to use a phone.</p>
<p>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. PHPConf.Asia staff requests that they be your first resource when reporting a conference-related incident, so that they may enforce the Code of Conduct and take quick action toward a
resolution.
</p>
<p>A list of PHPConf.Asia organisers can be found below.</p>
<h5>Staff Procedure for Incident Handling</h5>
<p>Be sure to have a good understanding of our Code of Conduct policy. Also have a good understanding of what is expected from an attendee that wants to report a harassment incident.</p>
<p>Try to get as much of the incident in written form by the reporter. If you cannot, transcribe it yourself as it was told to you. The important information to gather include the following:</p>
<ul class="styled">
<li>Identifying information (e.g. name, description) of the participant doing the harassing</li>
<li>The behaviour that was in violation</li>
<li>The approximate time of the behaviour (if different than the time the report was made)</li>
<li>The circumstances surrounding the incident</li>
<li>Other people involved in the incident</li>
</ul>
<p>Prepare an initial response to the incident. This initial response is very important and will set the tone for PHPConf.Asia. Depending on the severity/details of the incident, please follow these guidelines:</p>
<ul class="styled">
<li>If there is any general threat to attendees or the safety of anyone including conference staff is in doubt, summon security or police</li>
<li>Offer the victim a private place to sit</li>
<li>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)</li>
<li>Ask them “how can I help?”</li>
<li>Provide them with your list of emergency contacts if they need help later</li>
<li>If everyone is presently physically safe, involve police or security only at a victim’s request</li>
</ul>
<p>There are also some guidelines as to what not to do as an initial response:</p>
<ul class="styled">
<li>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.</li>
<li>Do not ask for their advice on how to deal with the complaint. This is a staff responsibility.</li>
<li>Do not offer them input into penalties. This is the staff’s responsibility.</li>
</ul>
<p>Once something is reported to a staff member, immediately meet with the conference chair and/or event coordinator. The main objectives of this meeting is to find out the following:</p>
<ul class="styled">
<li>What happened?</li>
<li>Are we doing anything about it?</li>
<li>Who is doing those things?</li>
<li>When are they doing them?</li>
</ul>
<p>After the staff meeting and discussion, have a staff member (preferably the conference chair or event coordinator if available) communicate with the alleged harasser. Make sure to inform them of what has been reported about them.</p>
<p>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.</p>
<p>Some things for the staff to consider when dealing with Code of Conduct offenders:</p>
<ul class="styled">
<li>Warning the harasser to cease their behaviour and that any further reports will result in sanctions</li>
<li>Requiring that the harasser avoid any interaction with, and physical proximity to, their victim for the remainder of the event</li>
<li>Ending a talk that violates the policy early</li>
<li>Not publishing the video or slides of a talk that violated the policy</li>
<li>Not allowing a speaker who violated the policy to give (further) talks at the event now or in the future</li>
<li>Immediately ending any event volunteer responsibilities and privileges the harasser holds</li>
<li>Requiring that the harasser not volunteer for future events your organization runs (either indefinitely or for a certain time period)</li>
<li>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)</li>
<li>Requiring that the harasser immediately leave the event and not return</li>
<li>Banning the harasser from future events (either indefinitely or for a certain time period)</li>
<li>Removing a harasser from membership of relevant organisations</li>
<li>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)</li>
</ul>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>If some attendees were angered by the incident, it is best to apologise 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.</p>
<p>The contact details of key conference organisers are below:</p>
<ul>
<li><strong>Michael Cheng</strong> <a href="http://twitter.com/coderkungfu">@coderkungfu</a> | <a href="/cdn-cgi/l/email-protection#34595d57575c515a5374445c44575b5a521a55475d55"><span class="__cf_email__" data-cfemail="cca1a5afafa4a9a2ab8cbca4bcafa3a2aae2adbfa5ad">[email protected]</span><script data-cfhash='f9e31' type="text/javascript">/* <![CDATA[ */!function(t,e,r,n,c,a,p){try{t=document.currentScript||function(){for(t=document.getElementsByTagName('script'),e=t.length;e--;)if(t[e].getAttribute('data-cfhash'))return t[e]}();if(t&&(c=t.previousSibling)){p=t.parentNode;if(a=c.getAttribute('data-cfemail')){for(e='',r='0x'+a.substr(0,2)|0,n=2;a.length-n;n+=2)e+='%'+('0'+('0x'+a.substr(n,2)^r).toString(16)).slice(-2);p.replaceChild(document.createTextNode(decodeURIComponent(e)),c)}p.removeChild(t)}}catch(u){}}()/* ]]> */</script></a> | mobile:
+65 91855166</li>
</ul>
<hr />
<h4>Attribution</h4>
<p>This Code of Conduct is adapted from <a href="https://github.com/python/pycon-code-of-conduct" target="_blank">PyCon Code of Conduct</a> and the <a href="http://geekfeminism.org/about/code-of-conduct/" target="_blank">GeekFeminism.org Code of Conduct</a>.</p>
</div>
</div>
</div>
<footer class="page-footer">
<div class="footer-copyright center-align">
<span class="white-text">© PHPConf.Asia 2018</span>
</div>
</footer>
</div>
<script type="text/javascript" src="https://code.jquery.com/jquery-2.1.1.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/materialize/1.0.0-alpha.4/js/materialize.min.js"></script>
<script type="text/javascript" src="/scripts/app.js"></script>
<script>
! function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0],
p = /^http:/.test(d.location) ? 'http' : 'https';
if (!d.getElementById(id)) {
js = d.createElement(s);
js.id = id;
js.src = p + '://platform.twitter.com/widgets.js';
fjs.parentNode.insertBefore(js, fjs);
}
}(document, 'script', 'twitter-wjs');
</script>
</body>
</html>