Update rule six to be general prohibitions listicle. Also rename rule zero #74
Conversation
Remove items to be moved into rule 6
Move in items from rule 0, bit of a rewording.
Rename rule to be more literal. Alternative titles welcome. Hope I've done the subtitle syntax right. Also moved stuff around to try and lead with the most critical stuff. Might just be churn 😅
Fix the list. Add a call to action.
Actually change rule 6 name - thought I'd done that already. Must remember to change them on the main page before finalising...
AaronJackson
left a comment
AaronJackson
left a comment
There was a problem hiding this comment.
As we discussed, renaming of Rule 0 will be unpopular with some members. I don't know whether other spaces inherited it from us, or if we got it from elsewhere. While I like it, I agree that it has been misinterpreted too frequently (mostly by newer members). Hopefully "a.k.a Do not be on fire" is sufficient to preserve this legacy (if there is a legacy...)
|
|
||
| We encourage members to challenge **unsafe storage** by other members. If you do not feel comfortable challenging a member, we welcome emails to the [email protected] email address. | ||
|
|
||
| Wearing **safety gear** at the Hackspace is your own responsibility. We will provide appropriate Personal Protective Equipment (PPE), and we ask if you notice any low supplies please email [email protected]. |
There was a problem hiding this comment.
I fear this might have been dropped here but not properly mentioned elsewhere
There was a problem hiding this comment.
Yeah that was definetely meant to be moved not dropped.
|
We inherited it from London (who still have it).
IIRC Jake then did the poster and other spaces picked it up from there
"Do Not Be On Fire or unsafe” ?????
… On 3 Nov 2025, at 14:16, Aaron S. Jackson ***@***.***> wrote:
@AaronJackson commented on this pull request.
As we discussed, renaming of Rule 0 will be unpopular with some members. I don't know whether other spaces inherited it from us, or if we got it from elsewhere. While I like it, I agree that it has been misinterpreted too frequently (mostly by newer members). Hopefully "a.k.a Do not be on fire" is sufficient to preserve this legacy (if there is a legacy...)
In do-not-be-on-fire.rst <#74 (comment)>:
>
We encourage members to challenge **unsafe storage** by other members. If you do not feel comfortable challenging a member, we welcome emails to the ***@***.*** email address.
-Wearing **safety gear** at the Hackspace is your own responsibility. We will provide appropriate Personal Protective Equipment (PPE), and we ask if you notice any low supplies please email ***@***.***
I fear this might have been dropped here but not properly mentioned elsewhere
—
Reply to this email directly, view it on GitHub <#74 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABZHXHFS4KBWUBNH2WXVMT325PVNAVCNFSM6AAAAACK43744WVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTIMJRGIYTIMJXGM>.
You are receiving this because you are subscribed to this thread.
|
|
"Do Not Be On Fire or Otherwise Unsafe” could work. In some ways makes it easier to read the fire part literally? I'm not staked to changing the name (Personally, I grok "Do Not Be On Fire" perfectly, and quite like it.) I'll happily revert if requested, though the members meeting where it was brought up there seemed to be a general feeling toward changing it. Or at least considering changing it. |
Moved some prohibition items from rule zero to rule six and reworded rule zero a little bit for clarity.
No substantial changes but generally should be clearer and more literal.