Thanks @kevinjos, this has some tight wording. I'd prefer for bullet-points to be on sequential lines to conform with the markdown/HTML semantics, but that's just formatting.
There are some issues that I covered in my proposal which I think are missing from yours:
- Asking people to leave
- _Specific_ discussion of sleeping at Noisebridge
- Leaving food out (outside of a general notion of mess)
- Smoking near the street-level entrance
Did you drop those things because you want to cover them in subsequent revisions, because you don't think we really agree on them, or just though the back-and-forth of drafting?
rules/community-guidelines.md on Mar 25, 2014
I'm not clear what “fair usage” means in this context? What were you trying to communicate?
rules/community-guidelines.md on Mar 25, 2014
Suggestion:
> We have promised the landlord that we will not attempt to service or perform maintenance on the elevator. Instead, elevator issues should be reported secretary@noisebridge.net, and will be taken up with building management.
rules/community-guidelines.md on Mar 25, 2014
Typo.
rules/community-guidelines.md on Mar 25, 2014
Suggestion: remove the bullet point on this line, and change to:
> There are only very specific circumstances under which we may use any of these places. None of these circumstances are likely to come up in regular use. Entering these spaces under any other circumstances jeopardizes our continued tenancy.
rules/community-guidelines.md on Mar 25, 2014
Suggested alternate line:
> Noisebridge is an infrastructure provider for technical-creative projects. In order to continue serving that function, we must maintain this infrastructure.
rules/community-guidelines.md on Mar 25, 2014
I've really enjoyed s/home/hostel. Here's an alternate line:
> Noisebridge is a hackerspace not a hostel. Using Noisebridge like a place to live impedes our mission, and makes it less useful as an infrastructure provider for others.
rules/community-guidelines.md on Mar 25, 2014
Suggestion:
> Noisebridge has designated places to store projects. Storing projects in common areas is anti-social. If your project is stored in a common area, it may be re-purposed or dicarded. If you do not know where to store your project, ask: in person, by mailing-list, or perusing the wiki.
rules/community-guidelines.md on Mar 25, 2014
This seems to have a lot of wishy-washy sort of language in it. Suggestion:
> We are all responsible for keeping Noisebridge clean and tidy. You are responsible for cleaning up after yourself. Leaving your mess for others is antisocial.
rules/community-guidelines.md on Mar 25, 2014
I'm not sure about this line. I'd definitely like to talk about do-ocracy and and the one-revert principle, but I'm not sure that this is the right place for it. I think the easiest solution would be to drop it from this document, and open an issue. We could add it in a different document or a subsequent commit.
In particular, I think that do-ocracy and one-revert are principles would really benefit from @kevinjos' approach of a very short, pithy delivery in the bureaucracy, and a longer discussion & explanation on the wiki.
rules/community-guidelines.md on Mar 25, 2014
I'm fine with this sentiment, but I think it could be expressed better. How about putting a specific expiry date in the header? Then if we make a change, we can likewise extend the expiry date. I'm concerned that a relative time might have ambiguous meaning.
No description provided.