Proposed Code of Conduct to replace Rule 1

Google Groups
1

Hi all,

The Hackspace is a safe space, and the board feel clarifying what is and
isn’t acceptable will help keep the space safe and usable to everyone as
the membership increases in size. To help in this, we have prepared the
following code of conduct, with the intention of it replacing Rule 1
http://wiki.hacman.org.uk/Hackspace_Rules#Rule_1:_Don.27t_be_a_dick as of
the 1st of February 2016.

Please provide feedback here about the document so that we can improve it.
Modifications are encouraged, but must be justified and commonly agreed
upon by the membership.

-Bob
on behalf of the Board

Hackspace Manchester Code of Conduct

This code of conduct applies in the Hackspace, in all Hackspace
communication channels, and when you are representing the Hackspace at
outside events.

We want to be inclusive; do not engage in homophobic, racist,
transphobic, ableist, sexist, or otherwise exclusionary behavior. Do not
make exclusionary jokes. Don’t even make them “ironically”.
2.

Don’t harass people. Physical contact or sexual attention without
consent is harassment. Dressing or acting in a certain way is not consent.
3.

Aggression and elitism are unwelcome - knowledge is not a competition.
4.

Although alcoholic drinks are allowed in the space, there is no
expectation or pressure to drink alcohol or conversely not to drink
alcohol. However, those who are obviously intoxicated will be asked to
leave the space.
5.

We’d rather you ask about gender than assume, and if you get it wrong,
apologise. Mistakes happen, however you should always use the person’s
preferred pronouns when addressing or discussing them.
6.

People’s private lives are their own. Do not share details about others
that they have not explicitly made public. This includes, but is not
limited to sexuality, gender, medical conditions, housing, relationship or
financial status.
7.

Discussion of how to make our hackspace more inclusive is welcome.
Claims that this “has gone too far” aren’t.

If you have any concerns about someone’s behaviour please let us know
either in person, or by emailing board@hacman.org.uk. If you do not wish
to email the whole board, individual board members can be contacted via
@hacman.org.uk

2

I think it is worth putting in writing the events that will take place in
case of contravention of the Code of Conduct.

KimballOn 15 January 2016 at 12:38, Bob Clough bob@clough.me wrote:

Hi all,

The Hackspace is a safe space, and the board feel clarifying what is and
isn’t acceptable will help keep the space safe and usable to everyone as
the membership increases in size. To help in this, we have prepared the
following code of conduct, with the intention of it replacing Rule 1
http://wiki.hacman.org.uk/Hackspace_Rules#Rule_1:_Don.27t_be_a_dick as
of the 1st of February 2016.

Please provide feedback here about the document so that we can improve it.
Modifications are encouraged, but must be justified and commonly agreed
upon by the membership.

-Bob
on behalf of the Board

Hackspace Manchester Code of Conduct

This code of conduct applies in the Hackspace, in all Hackspace
communication channels, and when you are representing the Hackspace at
outside events.

We want to be inclusive; do not engage in homophobic, racist,
transphobic, ableist, sexist, or otherwise exclusionary behavior. Do not
make exclusionary jokes. Don’t even make them “ironically”.
2.

Don’t harass people. Physical contact or sexual attention without
consent is harassment. Dressing or acting in a certain way is not consent.
3.

Aggression and elitism are unwelcome - knowledge is not a competition.
4.

Although alcoholic drinks are allowed in the space, there is no
expectation or pressure to drink alcohol or conversely not to drink
alcohol. However, those who are obviously intoxicated will be asked to
leave the space.
5.

We’d rather you ask about gender than assume, and if you get it wrong,
apologise. Mistakes happen, however you should always use the person’s
preferred pronouns when addressing or discussing them.
6.

People’s private lives are their own. Do not share details about
others that they have not explicitly made public. This includes, but is
not limited to sexuality, gender, medical conditions, housing, relationship
or financial status.
7.

Discussion of how to make our hackspace more inclusive is welcome.
Claims that this “has gone too far” aren’t.

If you have any concerns about someone’s behaviour please let us know
either in person, or by emailing board@hacman.org.uk. If you do not wish
to email the whole board, individual board members can be contacted via
@hacman.org.uk

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

3

Very good point. We’ll get that added :)On 15 January 2016 at 12:41, Kimball Johnson kimball@bowerham.net wrote:

I think it is worth putting in writing the events that will take place in
case of contravention of the Code of Conduct.

Kimball

On 15 January 2016 at 12:38, Bob Clough bob@clough.me wrote:

Hi all,

The Hackspace is a safe space, and the board feel clarifying what is and
isn’t acceptable will help keep the space safe and usable to everyone as
the membership increases in size. To help in this, we have prepared the
following code of conduct, with the intention of it replacing Rule 1
http://wiki.hacman.org.uk/Hackspace_Rules#Rule_1:_Don.27t_be_a_dick as
of the 1st of February 2016.

Please provide feedback here about the document so that we can improve
it. Modifications are encouraged, but must be justified and commonly agreed
upon by the membership.

-Bob
on behalf of the Board

Hackspace Manchester Code of Conduct

This code of conduct applies in the Hackspace, in all Hackspace
communication channels, and when you are representing the Hackspace at
outside events.

We want to be inclusive; do not engage in homophobic, racist,
transphobic, ableist, sexist, or otherwise exclusionary behavior. Do not
make exclusionary jokes. Don’t even make them “ironically”.
2.

Don’t harass people. Physical contact or sexual attention without
consent is harassment. Dressing or acting in a certain way is not consent.
3.

Aggression and elitism are unwelcome - knowledge is not a competition.
4.

Although alcoholic drinks are allowed in the space, there is no
expectation or pressure to drink alcohol or conversely not to drink
alcohol. However, those who are obviously intoxicated will be asked to
leave the space.
5.

We’d rather you ask about gender than assume, and if you get it
wrong, apologise. Mistakes happen, however you should always use the
person’s preferred pronouns when addressing or discussing them.
6.

People’s private lives are their own. Do not share details about
others that they have not explicitly made public. This includes, but is
not limited to sexuality, gender, medical conditions, housing, relationship
or financial status.
7.

Discussion of how to make our hackspace more inclusive is welcome.
Claims that this “has gone too far” aren’t.

If you have any concerns about someone’s behaviour please let us know
either in person, or by emailing board@hacman.org.uk. If you do not
wish to email the whole board, individual board members can be contacted
via @hacman.org.uk

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

4

I think it should be relatively clear when people are representing the
hackspace, but that list is more likely to be too large and changeable to
really function. Even a wiki page could get too onerous quickly. It would
be better that the fact that the rules are in place be made /at/ the event,
as that removes doubt and plausible deniability.

ChrisOn Fri, Jan 15, 2016 at 12:41 PM, Kimball Johnson kimball@bowerham.net wrote:

I think it is worth putting in writing the events that will take place in
case of contravention of the Code of Conduct.

Kimball

On 15 January 2016 at 12:38, Bob Clough bob@clough.me wrote:

Hi all,

The Hackspace is a safe space, and the board feel clarifying what is and
isn’t acceptable will help keep the space safe and usable to everyone as
the membership increases in size. To help in this, we have prepared the
following code of conduct, with the intention of it replacing Rule 1
http://wiki.hacman.org.uk/Hackspace_Rules#Rule_1:_Don.27t_be_a_dick as
of the 1st of February 2016.

Please provide feedback here about the document so that we can improve
it. Modifications are encouraged, but must be justified and commonly agreed
upon by the membership.

-Bob
on behalf of the Board

Hackspace Manchester Code of Conduct

This code of conduct applies in the Hackspace, in all Hackspace
communication channels, and when you are representing the Hackspace at
outside events.

We want to be inclusive; do not engage in homophobic, racist,
transphobic, ableist, sexist, or otherwise exclusionary behavior. Do not
make exclusionary jokes. Don’t even make them “ironically”.
2.

Don’t harass people. Physical contact or sexual attention without
consent is harassment. Dressing or acting in a certain way is not consent.
3.

Aggression and elitism are unwelcome - knowledge is not a competition.
4.

Although alcoholic drinks are allowed in the space, there is no
expectation or pressure to drink alcohol or conversely not to drink
alcohol. However, those who are obviously intoxicated will be asked to
leave the space.
5.

We’d rather you ask about gender than assume, and if you get it
wrong, apologise. Mistakes happen, however you should always use the
person’s preferred pronouns when addressing or discussing them.
6.

People’s private lives are their own. Do not share details about
others that they have not explicitly made public. This includes, but is
not limited to sexuality, gender, medical conditions, housing, relationship
or financial status.
7.

Discussion of how to make our hackspace more inclusive is welcome.
Claims that this “has gone too far” aren’t.

If you have any concerns about someone’s behaviour please let us know
either in person, or by emailing board@hacman.org.uk. If you do not
wish to email the whole board, individual board members can be contacted
via @hacman.org.uk

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

5

Kimball was talking more about the consequences of breaching the CoC I thinkOn 15 Jan 2016 12:48 p.m., “Chris Hilliard” badspyro@gmail.com wrote:

I think it should be relatively clear when people are representing the
hackspace, but that list is more likely to be too large and changeable to
really function. Even a wiki page could get too onerous quickly. It would
be better that the fact that the rules are in place be made /at/ the event,
as that removes doubt and plausible deniability.

Chris

On Fri, Jan 15, 2016 at 12:41 PM, Kimball Johnson kimball@bowerham.net wrote:

I think it is worth putting in writing the events that will take place in
case of contravention of the Code of Conduct.

Kimball

On 15 January 2016 at 12:38, Bob Clough bob@clough.me wrote:

Hi all,

The Hackspace is a safe space, and the board feel clarifying what is and
isn’t acceptable will help keep the space safe and usable to everyone as
the membership increases in size. To help in this, we have prepared the
following code of conduct, with the intention of it replacing Rule 1
http://wiki.hacman.org.uk/Hackspace_Rules#Rule_1:_Don.27t_be_a_dick
as of the 1st of February 2016.

Please provide feedback here about the document so that we can improve
it. Modifications are encouraged, but must be justified and commonly agreed
upon by the membership.

-Bob
on behalf of the Board

Hackspace Manchester Code of Conduct

This code of conduct applies in the Hackspace, in all Hackspace
communication channels, and when you are representing the Hackspace at
outside events.

We want to be inclusive; do not engage in homophobic, racist,
transphobic, ableist, sexist, or otherwise exclusionary behavior. Do not
make exclusionary jokes. Don’t even make them “ironically”.
2.

Don’t harass people. Physical contact or sexual attention without
consent is harassment. Dressing or acting in a certain way is not consent.
3.

Aggression and elitism are unwelcome - knowledge is not a
competition.
4.

Although alcoholic drinks are allowed in the space, there is no
expectation or pressure to drink alcohol or conversely not to drink
alcohol. However, those who are obviously intoxicated will be asked to
leave the space.
5.

We’d rather you ask about gender than assume, and if you get it
wrong, apologise. Mistakes happen, however you should always use the
person’s preferred pronouns when addressing or discussing them.
6.

People’s private lives are their own. Do not share details about
others that they have not explicitly made public. This includes, but is
not limited to sexuality, gender, medical conditions, housing, relationship
or financial status.
7.

Discussion of how to make our hackspace more inclusive is welcome.
Claims that this “has gone too far” aren’t.

If you have any concerns about someone’s behaviour please let us know
either in person, or by emailing board@hacman.org.uk. If you do not
wish to email the whole board, individual board members can be contacted
via @hacman.org.uk

–
You received this message because you are subscribed to the Google
Groups “Hackspace Manchester” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

6

Kimball was talking more about the consequences of breaching the CoC I
think

yes, indeed.

7

Hello,

I am replying directly because I cannot reply to the thread.

I suggest changing point 1 because there are people who may pick up on
and be particular about the phrasing of your current point 1. I suggest
changing it to:

We want to be inclusive; do not engage in exclusionary behavior, for
example homophobic, racist, transphobic, ableist, sexist, or otherwise. Do
not make exclusionary jokes. Don’t even make them “ironically”.

This way you’re making the list as examples and logically it may read as
"this is a list, here are some of the points that there may be issue with,
but there could be more" where as the current point one could be read as
"here is a list, this is the only list we’re concerned about".

8

That’s a good point. Maybe “Including but not limited to” instead of "For
example"On 15 Jan 2016 1:02 p.m., “Bob Clough” parag0n@ivixor.net wrote:

---------- Forwarded message ----------
From: “Christopher Stanton” stanto@gmail.com

Hello,

I am replying directly because I cannot reply to the thread.

I suggest changing point 1 because there are people who may pick up on
and be particular about the phrasing of your current point 1. I suggest
changing it to:

We want to be inclusive; do not engage in exclusionary behavior, for
example homophobic, racist, transphobic, ableist, sexist, or otherwise. Do
not make exclusionary jokes. Don’t even make them “ironically”.

This way you’re making the list as examples and logically it may read as
"this is a list, here are some of the points that there may be issue with,
but there could be more" where as the current point one could be read as
"here is a list, this is the only list we’re concerned about".

-Stanto

9

I would like to politely dissent on the linguistic content of the code of conduct.

I feel that by framing these goals for inclusion as a set of absolutes it’s ultimately coherseive behaviour and not actually very inclusive at all

The rule 1 that we have in place already prohibits the behaviours listed in the proposed code of conduct. We don’t need more rules we need consequences to rule breaking to be enforced> On 15 Jan 2016, at 12:52, Kimball Johnson kimball@bowerham.net wrote:

On 15 January 2016 at 12:51, Bob Clough parag0n@ivixor.net wrote:
Kimball was talking more about the consequences of breaching the CoC I think

yes, indeed.

–
You received this message because you are subscribed to the Google Groups “Hackspace Manchester” group.
To unsubscribe from this group and stop receiving emails from it, send an email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

10

Hi Mark,

We’re not making any new rules. As you stated, Rule 1 does already
covered the listed behaviour, however the goal of the above is to provide
examples and guidance to new and old members prevent miscommunication and
musunderstanding.

As a Board member, i find Rule 1 as it is suffers from the issue of being
difficult to enforce. It uses needlessly aggressive, accusatory and
gendered language, instead of a warning on the basis of “cut that out, its
breaching the code of conduct”, the subtext of any conversation is
basically " you are being a cock"

I agree on the consequences point. We are preparing some modifications to
make that more explicit.

-BobOn 15 Jan 2016 1:14 p.m., “Mark Ashworth” m.aj.ashworth@gmail.com wrote:

I would like to politely dissent on the linguistic content of the code of
conduct.

I feel that by framing these goals for inclusion as a set of absolutes
it’s ultimately coherseive behaviour and not actually very inclusive at all

The rule 1 that we have in place already prohibits the behaviours listed
in the proposed code of conduct. We don’t need more rules we need
consequences to rule breaking to be enforced

Sent from my iPhone

On 15 Jan 2016, at 12:52, Kimball Johnson kimball@bowerham.net wrote:

On 15 January 2016 at 12:51, Bob Clough parag0n@ivixor.net wrote:

Kimball was talking more about the consequences of breaching the CoC I
think

yes, indeed.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

11

That’s a good point. Maybe “Including but not limited to” instead of “For
example”

Yes I know I have “lurker status”, but… :wink:

A meta-comment - coming to this cold, the proposed new roles instantly
made me think “WTF has been going on there?” I have no idea if there’s
been any sort of an incident, but if I was a prospective new member I’d
be a little concerned as to why the board needed to draw up such a list
in the first place. Just a thought.

I don’t think the list of behaviours in 1) is a good idea I’m afraid, I
think it focuses too much on gender/sexuality/race whereas there are a
lot of other things that come under the old Rule 1 of “dickish behaviour”.

“Including but not limited to” is no better either, why pick out just
one subset of behaviours to mention explicitly and then end it with in
effect “And anything else we don’t like”? The list is simply unnecessary
if you are going to do that.

  1. Consent usually involves some sort of action, either verbal or
    physical, so saying that actions can’t be interpreted as consent when
    giving consent is an action seems hopelessly muddled and unenforceable.

  2. seems incredibly specific, and the problem it seeks to address sounds
    more like an unwitting social gaffe than an issue that needs to be
    addressed by a rule.

  3. What is “public?” If someone is discussing any of these issues in the
    HS within the earshot of others, what does that come under?

I’m not sure what this is trying to say either:

“Discussion of how to make our hackspace more inclusive is welcome.
Claims that this “has gone too far” aren’t.”

I’d probably condense most of it down to something like this:

“The hackspace is an inclusive organisation that is open to anyone to
join and the membership have a wide range of life experience, beliefs
and lifestyles. Please respect those differences - if you don’t
understand someone or you find that something they’ve done troubles you,
please talk to the person involved in private first. If you are on the
receiving end of such a request, please don’t take offence. Both parties
need to be prepared to differ but still respect the other person’s
viewpoint, and act accordingly. If you can’t resolve issues that way,
please talk to either the entire board or an individual board member if
you prefer. The board will take all such requests seriously and address
them promptly. The board’s decision on how the issue should be resolved
will be final, and may as a last resort terminate membership.”

Alan Burlison

12

Changing rule 1 to a new code of conduct to my mind is a rule change.

As to subject of the phasing of rule 1 personally I like how subjective it is your in that you breach the rule only when you cause harm or distress to another member it allows for personal interpretation but can be objectively measured and allows for dissenting opinions to be voiced without automatically being in breach of the rule.

I don’t feel that the language is particularly or specifically gendered as I’ve always thought it meant Cocky behaviour as in overconfidence about the likelihood of it causing harm or damage.

At the same time we need to have a POC for rule breaches and a proper process for dealing with disputes, a code of conduct doesn’t fulfill this requirement and without a disputes procedure is just as ineffective.> On 15 Jan 2016, at 13:29, Bob Clough parag0n@ivixor.net wrote:

Hi Mark,

We’re not making any new rules. As you stated, Rule 1 does already covered the listed behaviour, however the goal of the above is to provide examples and guidance to new and old members prevent miscommunication and musunderstanding.

As a Board member, i find Rule 1 as it is suffers from the issue of being difficult to enforce. It uses needlessly aggressive, accusatory and gendered language, instead of a warning on the basis of “cut that out, its breaching the code of conduct”, the subtext of any conversation is basically " you are being a cock"

I agree on the consequences point. We are preparing some modifications to make that more explicit.

-Bob

On 15 Jan 2016 1:14 p.m., “Mark Ashworth” m.aj.ashworth@gmail.com wrote:
I would like to politely dissent on the linguistic content of the code of conduct.

I feel that by framing these goals for inclusion as a set of absolutes it’s ultimately coherseive behaviour and not actually very inclusive at all

The rule 1 that we have in place already prohibits the behaviours listed in the proposed code of conduct. We don’t need more rules we need consequences to rule breaking to be enforced

Sent from my iPhone

On 15 Jan 2016, at 12:52, Kimball Johnson kimball@bowerham.net wrote:

On 15 January 2016 at 12:51, Bob Clough parag0n@ivixor.net wrote:
Kimball was talking more about the consequences of breaching the CoC I think

yes, indeed.

–
You received this message because you are subscribed to the Google Groups “Hackspace Manchester” group.
To unsubscribe from this group and stop receiving emails from it, send an email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups “Hackspace Manchester” group.
To unsubscribe from this group and stop receiving emails from it, send an email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups “Hackspace Manchester” group.
To unsubscribe from this group and stop receiving emails from it, send an email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

13

A code of conduct is not a rule - The rule should be something like
’observe the Code of Conduct’. Infact the one for LAMM is (off the top of
my head atleast) ‘Dont be an idiot (see Code of Conduct)’. I also agree
with Stanto, that the first rule should list those as examples, not as an
exhaustive list.

Keeping rules easy to remember is a good idea, but as with all rules,
expansion on what that actually means is going to be needed.On Fri, 15 Jan 2016 at 13:14 Mark Ashworth m.aj.ashworth@gmail.com wrote:

I would like to politely dissent on the linguistic content of the code of
conduct.

I feel that by framing these goals for inclusion as a set of absolutes
it’s ultimately coherseive behaviour and not actually very inclusive at all

The rule 1 that we have in place already prohibits the behaviours listed
in the proposed code of conduct. We don’t need more rules we need
consequences to rule breaking to be enforced

Sent from my iPhone

On 15 Jan 2016, at 12:52, Kimball Johnson kimball@bowerham.net wrote:

On 15 January 2016 at 12:51, Bob Clough parag0n@ivixor.net wrote:

Kimball was talking more about the consequences of breaching the CoC I
think

yes, indeed.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

14

I’m very much in favour of the new CoC, and I’ll be glad to see Rule 1
go. Thanks!On 15 January 2016 at 12:38, Bob Clough bob@clough.me wrote:

Hi all,

The Hackspace is a safe space, and the board feel clarifying what is and
isn’t acceptable will help keep the space safe and usable to everyone as the
membership increases in size. To help in this, we have prepared the
following code of conduct, with the intention of it replacing Rule 1 as of
the 1st of February 2016.

Please provide feedback here about the document so that we can improve it.
Modifications are encouraged, but must be justified and commonly agreed upon
by the membership.

-Bob
on behalf of the Board

Hackspace Manchester Code of Conduct

This code of conduct applies in the Hackspace, in all Hackspace
communication channels, and when you are representing the Hackspace at
outside events.

We want to be inclusive; do not engage in homophobic, racist, transphobic,
ableist, sexist, or otherwise exclusionary behavior. Do not make
exclusionary jokes. Don’t even make them “ironically”.

Don’t harass people. Physical contact or sexual attention without consent is
harassment. Dressing or acting in a certain way is not consent.

Aggression and elitism are unwelcome - knowledge is not a competition.

Although alcoholic drinks are allowed in the space, there is no expectation
or pressure to drink alcohol or conversely not to drink alcohol. However,
those who are obviously intoxicated will be asked to leave the space.

We’d rather you ask about gender than assume, and if you get it wrong,
apologise. Mistakes happen, however you should always use the person’s
preferred pronouns when addressing or discussing them.

People’s private lives are their own. Do not share details about others that
they have not explicitly made public. This includes, but is not limited to
sexuality, gender, medical conditions, housing, relationship or financial
status.

Discussion of how to make our hackspace more inclusive is welcome. Claims
that this “has gone too far” aren’t.

If you have any concerns about someone’s behaviour please let us know either
in person, or by emailing board@hacman.org.uk. If you do not wish to email
the whole board, individual board members can be contacted via
@hacman.org.uk

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

15

I have always found the current rule one to be a tad childish.

I am in favour of a code of conduct the one outlined is a good start but I
prefer Alan’s approach.On 15 January 2016 at 15:03, Jim MacArthur jim@mode7.co.uk wrote:

I’m very much in favour of the new CoC, and I’ll be glad to see Rule 1
go. Thanks!

On 15 January 2016 at 12:38, Bob Clough bob@clough.me wrote:

Hi all,

The Hackspace is a safe space, and the board feel clarifying what is and
isn’t acceptable will help keep the space safe and usable to everyone as
the
membership increases in size. To help in this, we have prepared the
following code of conduct, with the intention of it replacing Rule 1 as
of
the 1st of February 2016.

Please provide feedback here about the document so that we can improve
it.
Modifications are encouraged, but must be justified and commonly agreed
upon
by the membership.

-Bob
on behalf of the Board

Hackspace Manchester Code of Conduct

This code of conduct applies in the Hackspace, in all Hackspace
communication channels, and when you are representing the Hackspace at
outside events.

We want to be inclusive; do not engage in homophobic, racist,
transphobic,
ableist, sexist, or otherwise exclusionary behavior. Do not make
exclusionary jokes. Don’t even make them “ironically”.

Don’t harass people. Physical contact or sexual attention without
consent is
harassment. Dressing or acting in a certain way is not consent.

Aggression and elitism are unwelcome - knowledge is not a competition.

Although alcoholic drinks are allowed in the space, there is no
expectation
or pressure to drink alcohol or conversely not to drink alcohol. However,
those who are obviously intoxicated will be asked to leave the space.

We’d rather you ask about gender than assume, and if you get it wrong,
apologise. Mistakes happen, however you should always use the person’s
preferred pronouns when addressing or discussing them.

People’s private lives are their own. Do not share details about others
that
they have not explicitly made public. This includes, but is not limited
to
sexuality, gender, medical conditions, housing, relationship or financial
status.

Discussion of how to make our hackspace more inclusive is welcome. Claims
that this “has gone too far” aren’t.

If you have any concerns about someone’s behaviour please let us know
either
in person, or by emailing board@hacman.org.uk. If you do not wish to
email
the whole board, individual board members can be contacted via
@hacman.org.uk

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send an email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

16

I am in favour of a code of conduct the one outlined is a good start but I
prefer Alan’s approach.

The problem with specific lists of dickishness is that people are really
good at finding new forms of dickishness that aren’t on the list :slight_smile: I
think a general “play nice” backed up by “and we (the board) will decide
what ‘nice’ constitutes in case of disagreement” means that dealing with
problems won’t turn into a legalistic debate around what the rules
actually mean.

Slightly tweaked below:

The hackspace is an inclusive organisation that is open to anyone to
join and the membership have a wide range of life experiences, beliefs
and lifestyles. Please respect those differences - if you don’t
understand someone or you find that something they’ve done troubles you,
please talk to the person involved in private first. If you are on the
receiving end of such a request, please don’t take offence. Both parties
need to be prepared to differ but still respect the other person’s
viewpoint, and behave accordingly. If you can’t resolve an issue that
way, please talk to either the entire board or an individual board
member if you prefer. The board will take all such requests seriously
and address them promptly. After discussion, the board will inform all
involved parties on how the issue is to be resolved. That resolution may
include termination of membership if the board believe that is in the
interests of the hackspace members as a whole. The board’s decision on
how an issue is to be resolved is final.

Alan Burlison

17

Hi Alan,

I agree that there needs to be more flexibility, a lot more information on
what people should do regarding reporting problems, and the procedures that
will be followed in case of an incident, though I would personally look at
pushing the latter two into the rules themselves as opposed to appending it
to the Code of Conduct.

The issue with just saying ‘respect other people’ is people have a
different level of understanding of what that means. The list we put
together as part of the CoC is not meant to be an exhaustive list of rules,
but is intended to provide a baseline level of expected behaviour by
including examples of incidents which have been known to happen in techie
dominated spaces and events.

-BobOn 15 January 2016 at 16:02, Alan Burlison alan.burlison@gmail.com wrote:

On 15/01/2016 15:29, Alexander Lang wrote:

I am in favour of a code of conduct the one outlined is a good start but I

prefer Alan’s approach.

The problem with specific lists of dickishness is that people are really
good at finding new forms of dickishness that aren’t on the list :slight_smile: I
think a general “play nice” backed up by “and we (the board) will decide
what ‘nice’ constitutes in case of disagreement” means that dealing with
problems won’t turn into a legalistic debate around what the rules actually
mean.

Slightly tweaked below:

The hackspace is an inclusive organisation that is open to anyone to join
and the membership have a wide range of life experiences, beliefs and
lifestyles. Please respect those differences - if you don’t understand
someone or you find that something they’ve done troubles you, please talk
to the person involved in private first. If you are on the receiving end of
such a request, please don’t take offence. Both parties need to be prepared
to differ but still respect the other person’s viewpoint, and behave
accordingly. If you can’t resolve an issue that way, please talk to either
the entire board or an individual board member if you prefer. The board
will take all such requests seriously and address them promptly. After
discussion, the board will inform all involved parties on how the issue is
to be resolved. That resolution may include termination of membership if
the board believe that is in the interests of the hackspace members as a
whole. The board’s decision on how an issue is to be resolved is final.

–
Alan Burlison

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send an email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

18

Indeed, this is our intention.On 15 January 2016 at 14:57, Tom Bloor tom.bloor@gmail.com wrote:

A code of conduct is not a rule - The rule should be something like
’observe the Code of Conduct’. Infact the one for LAMM is (off the top of
my head atleast) ‘Dont be an idiot (see Code of Conduct)’. I also agree
with Stanto, that the first rule should list those as examples, not as an
exhaustive list.

Keeping rules easy to remember is a good idea, but as with all rules,
expansion on what that actually means is going to be needed.

On Fri, 15 Jan 2016 at 13:14 Mark Ashworth m.aj.ashworth@gmail.com wrote:

I would like to politely dissent on the linguistic content of the code of
conduct.

I feel that by framing these goals for inclusion as a set of absolutes
it’s ultimately coherseive behaviour and not actually very inclusive at all

The rule 1 that we have in place already prohibits the behaviours listed
in the proposed code of conduct. We don’t need more rules we need
consequences to rule breaking to be enforced

Sent from my iPhone

On 15 Jan 2016, at 12:52, Kimball Johnson kimball@bowerham.net wrote:

On 15 January 2016 at 12:51, Bob Clough parag0n@ivixor.net wrote:

Kimball was talking more about the consequences of breaching the CoC I
think

yes, indeed.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"Hackspace Manchester" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to hacman+unsubscribe@googlegroups.com.
To post to this group, send email to hacman@googlegroups.com.
Visit this group at https://groups.google.com/group/hacman.
For more options, visit https://groups.google.com/d/optout.

19

Thanks for all the feedback today people, we’ll work on a revised draft
over the next day or so and send it out when we’re happy with it.On 15 January 2016 at 12:38, Bob Clough bob@clough.me wrote:

Hi all,

The Hackspace is a safe space, and the board feel clarifying what is and
isn’t acceptable will help keep the space safe and usable to everyone as
the membership increases in size. To help in this, we have prepared the
following code of conduct, with the intention of it replacing Rule 1
http://wiki.hacman.org.uk/Hackspace_Rules#Rule_1:_Don.27t_be_a_dick as
of the 1st of February 2016.

Please provide feedback here about the document so that we can improve it.
Modifications are encouraged, but must be justified and commonly agreed
upon by the membership.

-Bob
on behalf of the Board

Hackspace Manchester Code of Conduct

This code of conduct applies in the Hackspace, in all Hackspace
communication channels, and when you are representing the Hackspace at
outside events.

We want to be inclusive; do not engage in homophobic, racist,
transphobic, ableist, sexist, or otherwise exclusionary behavior. Do not
make exclusionary jokes. Don’t even make them “ironically”.
2.

Don’t harass people. Physical contact or sexual attention without
consent is harassment. Dressing or acting in a certain way is not consent.
3.

Aggression and elitism are unwelcome - knowledge is not a competition.
4.

Although alcoholic drinks are allowed in the space, there is no
expectation or pressure to drink alcohol or conversely not to drink
alcohol. However, those who are obviously intoxicated will be asked to
leave the space.
5.

We’d rather you ask about gender than assume, and if you get it wrong,
apologise. Mistakes happen, however you should always use the person’s
preferred pronouns when addressing or discussing them.
6.

People’s private lives are their own. Do not share details about
others that they have not explicitly made public. This includes, but is
not limited to sexuality, gender, medical conditions, housing, relationship
or financial status.
7.

Discussion of how to make our hackspace more inclusive is welcome.
Claims that this “has gone too far” aren’t.

If you have any concerns about someone’s behaviour please let us know
either in person, or by emailing board@hacman.org.uk. If you do not wish
to email the whole board, individual board members can be contacted via
@hacman.org.uk

20

The issue with just saying ‘respect other people’ is people have a
different level of understanding of what that means. The list we put
together as part of the CoC is not meant to be an exhaustive list of rules,
but is intended to provide a baseline level of expected behaviour by
including examples of incidents which have been known to happen in techie
dominated spaces and events.

That’s why I don’t think lists are very useful - some people have very
broad shoulders and a robust sense of humour, others far less so. What
would offend one person won’t even register with another, which is why I
think the rule should centre around feedback, listening and respect. I’d
hate to think the banter at the hackspace had to stop.

Alan Burlison

$ scala -e 'println(Seq(5937258800786469487L,7454127455866286707L,
2333816157527044713L,8387145410718886944L,7597045224257953900L,7020662622960182574L)
.flatMap(.toHexString).grouped(2).map(a=>a.map(c=>Integer.parseInt(c.toString,16)))
.map(d=>(d(0)<<4)+d(1)).map(.toChar).mkString)'
Real programmers can write Perl in any language.
$