-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
366 lines (361 loc) · 19.4 KB
/
index.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
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
<!DOCTYPE html>
<html lang="en-GB">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>mcrtech Slack Community</title>
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/[email protected]/css/bulma.min.css" />
<link rel="icon" href="icon.jpg" />
</head>
<body>
<header class="navbar">
<div class="navbar-brand">
<div class="navbar-item">
<img src="icon.jpg" alt="" width="28" height="28" />
</div>
<div class="navbar-item">
<h1>mcrtech Slack Community</h1>
</div>
</div>
<nav class="navbar-menu">
<div class="navbar-end">
<a class="navbar-item" href="#about">About</a>
<a class="navbar-item" href="#coc">Code of Conduct</a>
</div>
</nav>
</header>
<section id="about" class="hero is-link">
<div class="hero-body">
<div class="container">
<h2 class="title">About mcrtech</h2>
<div class="columns">
<div class="column is-half-tablet content">
<p>The mcrtech community is a community on Slack based around Manchester, UK.</p>
<p>
We’re open to people based in, or with links to, Manchester, Greater Manchester or the wider North West
who are either working in, studying for, or interested in technology.
</p>
<p>
The administrators for the Slack act as community moderators. They are @chrismatheson, @cnorthwood,
@Hakim Cassimally, @Parul Singh, @s10wen and @Tom.
</p>
</div>
<div class="column is-half-tablet content has-text-right">
<a
href="https://join.slack.com/t/mcrtech/shared_invite/zt-qnbdrcvb-YIQnZuF7HwIpcxHzuNvXgw"
class="button is-warning is-large"
>Join our Slack community</a
>
</div>
</div>
</div>
</div>
</section>
<section class="section" id="coc">
<div class="container">
<h2 class="title">Code of Conduct</h2>
<p class="subtitle">Be polite, kind to others. Do not insult or put down others. Behave professionally.</p>
<div class="columns">
<div class="column is-half-tablet content">
<p>
mcrtech operates under
<a href="https://en.wikipedia.org/wiki/Chatham_House_Rule">Chatham House Rule</a>. You are free to use the
information in mcrtech in other contexts. However, you should not disclose the identity or affiliation of
any commenter in mcrtech without first getting their permission.
</p>
<p>
mcrtech is dedicated to providing a harassment-free experience for everyone. We do not tolerate harassment
of participants in any form.
</p>
<p>
The mcrtech chat group aims to provide a safe space where contributors can disclose situations that they
are currently experiencing. It’s not always the case that the original contributor will be looking for
advice or feedback. Do not offer unsolicited advice or feedback without first checking the intentions of
the original comment poster. Specifically, members should only give advice and feedback if the poster
requested it. If in doubt, check first and use
<a href="https://resultsmatter.blogspot.com/2007/05/gestalt-protocol.html">the Gestalt Protocol</a>.
</p>
<p>
This code of conduct applies to all mcrtech spaces, including public channels, private channels and direct
messages, both online and off. Anyone who violates this code of conduct may be sanctioned or expelled from
these spaces at the administrators’ discretion.
</p>
<p>
Some mcrtech spaces may have additional rules in place, which will be made available to participants.
Participants are responsible for knowing and abiding by these rules. For example, general political
discussion should be contained to the #politics channel, which is opt-in. Political debate can get heated,
but robust debate around ideas will be tolerated, although criticism of the person holding those views is
not permitted.
</p>
<p>Harassment includes:</p>
<ul>
<li>
Offensive comments related to gender, gender identity and expression, sexual orientation, disability,
mental illness, neuro(a)typicality, physical appearance, body size, race, or religion
</li>
<li>
Unwelcome comments regarding a person’s lifestyle choices and practices, including those related to
food, health, parenting, drugs, and employment.
</li>
<li>Deliberate misgendering or use of “dead” or rejected names</li>
<li>Gratuitous or off-topic sexual images or behaviour in spaces where they’re not appropriate</li>
<li>
Physical contact and simulated physical contact (e.g., textual descriptions like “hug” or “backrub”)
without consent or after a request to stop.
</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>
Deliberate “outing” of any aspect of a person’s identity without their consent except as necessary to
protect vulnerable people from intentional abuse
</li>
<li>Publication of non-harassing private communication</li>
<li>
Instances of
<a href="https://everydayfeminism.com/2014/12/the-problem-with-privilege-explaining/"
>Privileged Explaining</a
>
</li>
</ul>
<p>
<strong>mcrtech prioritises marginalised people’s safety over privileged people’s comfort.</strong>
</p>
<p>The administrators will not act on, and may act against those making complaints regarding:</p>
<ul>
<li>
<a href="https://www.uncommonthought.com/mtblog/archives/2013/04/24/reverse-isms-an.php"
>“Reverse”-isms</a
>, including “<a href="https://en.wikipedia.org/wiki/Reverse_racism">reverse racism</a>”, “<a
href="https://geekfeminism.wikia.org/wiki/Reverse_sexism"
>reverse sexism</a
>”, and “<a
href="http://affinitymagazine.us/2017/07/06/theres-no-such-thing-as-cisphobia-youre-just-being-immature/"
>cisphobia</a
>”.
</li>
<li>
Reasonable communication of boundaries, such as “leave me alone”, “go away”, or “I’m not discussing this
with you”.
</li>
<li>Communicating in a “tone” you don’t find congenial</li>
<li>Criticising racist, sexist, transphobic, or otherwise oppressive behaviour or assumptions</li>
</ul>
<h3>Reporting</h3>
<p>
If a member of mcrtech is harassing you, notice that someone else is being harassed, or have any other
concerns, please contact one of the following members of the admin team directly by DM: @chrismatheson
@cnorthwood @Hakim Cassimally @Parul Singh @s10wen @Tom
</p>
<p>
This code of conduct applies to mcrtech spaces, but if you are being harassed by a member of mcrtech
outside our spaces, we still want to know about it. We will take all good-faith reports of harassment by
mcrtech members, especially the administrators, seriously. This includes harassment outside our spaces and
harassment that took place at any point in time. The abuse team reserves the right to exclude people from
mcrtech based on their past behaviour, including behaviour outside mcrtech spaces and behaviour towards
people who are not in mcrtech.
</p>
<p>
In order to protect volunteer admins from abuse and burnout, we reserve the right to reject any report we
believe to have been made in bad faith. Reports intended to silence legitimate criticism may be deleted
without response.
</p>
<p>
We will respect confidentiality requests to protect victims of abuse. At our discretion, we may publicly
name a person about whom we’ve received harassment complaints or privately warn third parties about them
if we believe that doing so will increase mcrtech members’ safety or the general public. We will not name
harassment victims without their affirmative consent.
</p>
<h3>Consequences</h3>
<p>Participants asked to stop any harassing behaviour are expected to comply immediately.</p>
<p>
If a participant engages in harassing behaviour, the administrators may take any action they deem
appropriate, up to and including expulsion from all mcrtech spaces and identification of the participant
as a harasser to other mcrtech members or the general public.
</p>
<h3>Advertising</h3>
<p>
A team of dedicated admins runs mcrtech for the enjoyment and benefit of its members. Our admins give up
their own time to foster and develop the community, and as such, we aim to keep the community an
advertising-free zone. One exception to this is the #show channel, where community members can share
projects or work they are launching that is of interest to the mcrtech community. If your only posts are
in #show, however, we deem that to be advertising, rather than a place for community members to show their
work. Similarly, events that are being run in or of specific interest to the Manchester/North West
community are permitted to be posted in the #events channel, although repeated posting of the same event
(other than reasonable reminders) will be considered spam. If you are an event organiser who only posts in
#events, this is permitted but please ask an admin first. We take a firm stance on members posting
advertisements of any kind in the community, and we reserve the right to remove posts that fall afoul of
this rule. An admin will inform the poster, and an admin will remove persistent offenders from the Slack
team.
</p>
<h3>Recruiting</h3>
<p>
We encourage members to share open job postings, and we have a #jobs channel specifically for this
purpose. Re-posting across other channels or requesting re-posts in private channels is forbidden. We also
support member-to-member recommendations. Soliciting via direct message is not permitted, except for
contacting a poster of a job via Direct Message unless they have specifically asked not to do that.
Soliciting includes pitching an agency or outsourcing via DM to a job poster that's clearly looking for
permanent members of staff. Unpaid employment or anything else the admins consider exploitative employment,
jobs based outside of the North West, or remote jobs being advertised by a company without a link to the
area are not permitted. When posting a job, please include some basic details and not just a “DM me for
more info” request - we highly encourage posting salaries on job ads (you are likely to be asked what the
range is anyway, if you do not). Any discussions on a particular post should occur in a thread on that post.
Although detail is encouraged, please do not post extremely long job ads (more than a screen high),
especially shortly after a more recent post, as this can be seen as trying to bury your competition.
</p>
<h3>Examples of behaviour</h3>
<p>
The following are examples of behaviours we wish to discourage, and alternative suggestions that can help
build a more positive community
</p>
</div>
</div>
<table class="table is-fullwidth is-striped">
<thead>
<tr>
<th scope="col">Example</th>
<th scope="col">Suggested Alternative</th>
<th scope="col">Rationale</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<p>
A: Hi, does someone know how to configure Prettier to autoformat on save in VS Code? I’ve attached a
screenshot of my settings and can’t figure it out
</p>
<p>B: Is that a light theme in your IDE? Real developers only use dark themes</p>
</td>
<td>
<p>
If the theme/setup is not relevant to the discussion, best not to say anything. Otherwise, if the
discussion is on settings/themes, “I use a dark theme myself, have you tried it and see how it
compares?”
</p>
</td>
<td>
<p>
How people configure their IDE is their personal preference - this comment is not constructive and can
be seen as gatekeeping especially if it’s not relevant to the wider discussion.
</p>
</td>
</tr>
<tr>
<td>
<p>
A: Can someone help me with this code? It’s failing to return the result I expect and I can’t figure
out why (with PHP code snippet)
</p>
<p>B: Why are you using PHP? That’s a trash language. No wonder it won’t work.</p>
</td>
<td>
<p>
Best not to say anything (criticism of languages etc is permitted in discussion, but only if relevant
to the conversation eg, if there is a major bug or similar found, but not as a sweeping statement in
response to another question)
</p>
</td>
<td>
<p>
Language choice is often due to wider constraints where the context isn’t clear. Making fun of
particular languages, especially if someone is new to coding and that’s what they’ve learnt can be
discouraging and elitist.
</p>
</td>
</tr>
<tr>
<td>
<p>
A: I’m thinking of using Create React App for my next project, has anyone got any experience they can
share?
</p>
<p>B: Why bother using React, it just makes sites really bloated and slows them down</p>
</td>
<td>
<p>
B: What kind of project are you looking at doing? React can be the right tool in some cases but there
can be downsides, so it’ll be useful to know what you’re planning on doing with it to advise
</p>
</td>
<td>
<p>
The initial example doesn’t answer the question and places the question asker on a defensive stature
and potentially shut down the conversation, rather than impart knowledge or encourage discussion.
</p>
</td>
</tr>
<tr>
<td>
<p>Why are all recruiters such liars who edit my CVs? They’re a stain on the industry.</p>
</td>
<td>
<p>
I just found out that a recruiter changed the skills on my CV without letting me know when they
submitted it to a hiring manager. I hate when people do this! I won’t be working with them again.
</p>
</td>
<td>
<p>
Although it can be tempting to vent, attacks on particular job roles within the wider tech sector are
rarely constructive and can be hurtful to people who have those roles. Rephrasing it in a more
specific and actionable way is more helpful to the wider community to identify bad apples to avoid. It
can be helpful to name the recruiter/company to advise others of those who have bad practice to be
avoided.
</p>
</td>
</tr>
<tr>
<td>
<p>
This hiring manager is such an idiot, they’re asking for Perl experience for a front-end role,
no-one’s going to have that!
</p>
</td>
<td>
<p>
I think you’ll find it hard to find a front-end developer with these particular skills, you might want
to review the skills list or the job title at least to accurately reflect what you want it to do.
</p>
</td>
<td>
<p>This rephrases it from a personal attack on the individual to a constructive criticism.</p>
</td>
</tr>
<tr>
<td>
<p>A: Hi, I’m Bob and I’m a DevOps Engineer at Foobar Design, nice to meet you!</p>
<p>B: No you’re not, DevOps is not a role, it’s a culture.</p>
</td>
<td>
<p>
B: Nice to meet you! What kind of devops do you do, are you embedded in a product team or a separate
platform team?
</p>
</td>
<td>
<p>
This is especially offputting as they’re a new member of the community, and telling someone that their
job title isn’t real or similar can belittle or demotivate them. Although the initial meaning of the
term as a culture has been eroded over time, we have to recognise the reality that exists.
</p>
</td>
</tr>
</tbody>
</table>
</div>
</section>
</body>
</html>