Skip to content

Conversation

@Johnathan858
Copy link
Contributor

The sleeping rule has the most extreme penalty of all the Hackspace rules (immediate permanent ban without warning) and yet until now it's been hidden away under a section nobody reads. An informal survey of several members has highlighted that very few people were aware of the severity of this rule (or that it covers naps as well as overnight sleeping). In particular, members who are deaf did not know this rule existed at all because it's shared verbally during the Hackspace tour, and being deaf they did not hear it. The Hackspace rules need to be accessible to people with disabilities, and therefore a visible, written, easy-to-find version of the rule is necessary.

If you are thinking, 'the rule is written under the UK Legislation section so we don't need it elsewhere' - there are a number of reasons why this is inadequate:

  1. People already know UK laws and legislation so they assume they don't need to read this section and will skip it;
  2. People are busy and don't have time to read every word on the rules site so they skim or skip things;
  3. Many members are autistic, ADD or otherwise neurodivergent and don't have the attention span to read through the entire rules site. This again is an accessibility issue;
  4. Even when people are intentionally trying to find the 'no sleeping' rule, they have difficulty finding it because it's miscategorised. There is no UK legislation against sleeping. The UK legislation says no living in a commercial space, which is not the same as a complete ban on sleeping. As it's not UK legislation, people don't think to look for it there.

For all these reasons, the sleeping rule is best placed as a core rule so it's visible and accessible. This also gives confidence that people will actually see the rule and therefore it's less likely to be broken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant