Rules: Difference between revisions
m (→Examples: replaced this with a more comprehensive think tank link) |
No edit summary |
||
| Line 1: | Line 1: | ||
=== Rules === | === Rules === | ||
Try to '''frame your rules in terms of expected behavior''' (what ''to'' do) rather than forbidden behavior (what ''not'' to do). That way it's easier for patrons and volunteers to remember what to do when they're not thinking too hard about. | Try to '''frame your rules in terms of expected behavior''' (what ''to'' do) rather than forbidden behavior (what ''not'' to do). That way it's easier for patrons and volunteers to remember what to do when they're not thinking too hard about. Knowing what is expected and what is not allowed helps define the social environment. | ||
===Examples=== | ===Examples=== | ||
[http://opensourcebridge.org/about/code-of-conduct/ Code of Conduct] from an open source event. | [http://opensourcebridge.org/about/code-of-conduct/ Code of Conduct] from an open source event. | ||
----- | ----- | ||
Safety might be first... No one gets hurt in an open shop... | Safety might be first... No one gets hurt in an open shop... | ||
Give & get respect. Respect the tools, Respect the process, Respect the people, not necessarily in that order. | |||
Respect the tools, Respect the process, Respect the people, not necessarily in that order. | Remember to define respect so that people know what it means to respect tools/process/people/etc. | ||
Ask | Ask if there is an issue... | ||
Ask a more experienced person if there is a question... | Ask a more experienced person if there is a question... | ||
For example, don't know how this brake system works, and it's a safety issue, | For example, don't know how this brake system works, and it's a safety issue, | ||
ask a | ask a more experienced person to look it over before it goes out the door... | ||
A double checking type buddy system... | A double checking type buddy system... | ||
Revision as of 17:38, 2 March 2016
Rules
Try to frame your rules in terms of expected behavior (what to do) rather than forbidden behavior (what not to do). That way it's easier for patrons and volunteers to remember what to do when they're not thinking too hard about. Knowing what is expected and what is not allowed helps define the social environment.
Examples
Code of Conduct from an open source event.
Safety might be first... No one gets hurt in an open shop...
Give & get respect. Respect the tools, Respect the process, Respect the people, not necessarily in that order. Remember to define respect so that people know what it means to respect tools/process/people/etc.
Ask if there is an issue... Ask a more experienced person if there is a question... For example, don't know how this brake system works, and it's a safety issue, ask a more experienced person to look it over before it goes out the door... A double checking type buddy system...
Tools go back where you found them.
Tools stay in the shop.
Think Tank
- need examples of expected shop behavior policies
- alcohol at shop - during meetings - pros and cons? - hit "next message" to scroll through the entire conversation