<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p> </p>
<p>Hi all,</p>
<p>On a rather diff-erent note to my previous email, I've got
another suggestion for how to go about regulations. This relates
primarily to dealing with cultural issues but I've outlined a few
other things (some covered by my initial suggestion, many not)
which should probably also be addressed.<br>
</p>
<p>I'd have preferred send this out after the full agenda from the
last meeting had been discussed (minutes <i>are</i> on their way
soon!), although hopefully this can still be considered and
discussed ahead of time.<br>
</p>
<p>For your convenience and amusement I have attached a plaintext
document containing all of UniSFA's current committee regulations.
These can also be found online <a moz-do-not-send="true"
href="https://drive.google.com/drive/folders/18KzpZxLlGWsRcB0pyYEPXFvEFxGrVhky">here</a>
and <a moz-do-not-send="true"
href="https://www.facebook.com/notes/unisfa/facebook-rules-last-updated-26214/10150818298981026/">here</a>.<br>
</p>
<p>I would suggest that committee read through and compare these
UCC's current regulations (<a
href="https://github.com/ucc/regulations/">https://github.com/ucc/regulations/</a>).<br>
</p>
<p>For some additional background, it may also be worth reading the
<a href="https://unigames.ucc.asn.au/regulations.php">Unigames
Regulations</a> (these are similar in structure and style to our
own).<br>
</p>
<p>In terms of reviewing and updating UCC regulations, I think we
should look towards UniSFA as an example to follow. Conveniently,
in terms of their structure and phrasing, UniSFA's regulations can
be easily applied to UCC with only relatively minor changes. For
the most part this would involve trivial tweaks such as replacing
<tt>UniSFA </tt>with<tt> UCC</tt>, <tt>CCC</tt> with <tt>door</tt>,
<tt>Facebook</tt> with <tt>Facebook/Discord/IRC/email</tt>, etc.</p>
<p>To be clear, I think that the following points are addressed well
by UniSFA's regulations but not by our own: (and that we should
adopt them in a UCC-ised form)<br>
</p>
<ul>
<li>Clubroom rules - will need to be rewritten somewhat for UCC<br>
</li>
<li>Dooring policy<br>
</li>
<li>Sexual harrassment policy (this also defines in part a
procedure for complaints in general)<br>
</li>
<li>Online code of conduct (UniSFA's "Facebook rules")</li>
<li>CCC duties/guidelines (UniSFA equivalent of door)</li>
</ul>
<p>Of course, UCC has a number of things which we do differently to
UniSFA (or they just don't have) - in this case I believe our
current regulations are reasonable;<br>
</p>
<ul>
<li>concise definition of groups (door/wheel)<br>
</li>
<li>wheel regulations and ethical guidelines</li>
<li>account locking</li>
<li>computer use priority</li>
<li>network use guidelines (note that these do not mention
moderation or disciplinary actions that may be performed)</li>
</ul>
<p>Lastly, a few things which I don't feel are addressed adequately
by either UniSFA's regulations or by our own, and really should
be:<br>
</p>
<ul>
<li>group application guidelines (even the LOLCATDOG wasn't
included in the current set of regulations :-O but we should
probably bring it back)</li>
<ul>
<li>emphasis on committee's trust that people will use their
powers responsibly and are prepared to follow/enforce
regulations (equally so for door and wheel)<br>
</li>
<li>including a similarly specific process to LOLCATDOG for
wheel applications (although probably with fewer, but more
open-ended, questions)<br>
</li>
<li>explicitly stating a timeframe for all group membership
expirations / renewals / reapplications (as UniSFA does for
CCC)<br>
</li>
</ul>
<li>group training programmes<br>
</li>
<ul>
<li>Unigames does official gatekeeper training, although I
haven't found it online</li>
<li>Suggestion for door: very much follow the Unigames model, it
seems to work</li>
<li>Suggestion for wheel: emphasise/formalise the induction
process with specific steps (ie. reading, understanding and
signing the ethical guidelines on some sort of form, also the
stuff in <tt>/home/wheel/docs/WelcomeToWheel</tt>)</li>
<li>Suggestion for committee/door: attending Student Leadership
Training (run by the Guild, covers all kinds of
human-interaction topics that UCC committees tend to be bad
at) - either formally in regulation or just as a standing
recommendation</li>
</ul>
<li>complaints process (see UniSFA sexual harrassment policy)<br>
</li>
<ul>
<li>Google Form for people to provide feedback, comments and
complaints about member behaviour</li>
<li>Committee will be notified and can take immediate action
depending on nature of complaint (specifically dooring,
account locking, etc)<br>
</li>
<li>Reviewed at next meeting, committee makes call to drop /
take action / escalate based on seriousness.</li>
<li>Parties involved will be informed (in confidence) of details
about the complaint within 7 days of complaint being raised<br>
</li>
<li>Complainant can choose to remain anonymous</li>
<li>Respondent is given an opportunity to respond to the
complaint such that committee may reconsider any judgements
made<br>
</li>
</ul>
<li>procedure for delegation of wheel privileges to non-wheel
members (ie. sprocket/winadmin/webmasters, or on an individual
machine basis)</li>
<ul>
<li>even just clarifying that wheel has the ability to do this</li>
<li>revive the group membership form from 1999?<br>
</li>
</ul>
<li>explicitly <i>not</i> having an SLA (people seem to have
surprising uptime expectations for club systems)</li>
<ul>
<li>something like "How to break UCC responsibly - an official
guide" (ie. more specific procedures than just what is in the
wheel ethical guidelines)</li>
<li>suggestions welcome<br>
</li>
</ul>
<li>privacy policy (this is probably even a legal requirement)</li>
<ul>
<li>proposal: give us your data so we can use it for whatever we
want, whenever and however we want (?!)<br>
</li>
<li><b>suggestions needed</b></li>
</ul>
<li>co-location regulations</li>
<ul>
<li>from recent discussions: wheel keys / procedures for admin
access? firewalling? shutdown procedure? remote management?<br>
</li>
<li>VMs and co-located hardware<br>
</li>
<li>suggestions needed</li>
</ul>
</ul>
<p>The primary reason for proposing a more-regulations-are-better
approach, and for wishing to formalise such a large range of
things that have not necessarily been so previously, is so that
this sets very clear boundaries for acceptable behaviour, defines
clear procedures for people to follow, and there is far less scope
for hostilities on the basis of speculation and apparent lack of
transparency (which has been an issue recently). When there's no
formal procedure defined, it's easy to argue that one isn't being
followed.</p>
<p>Naturally, the effectiveness of regulations comes down to how
well they are followed and enforced. I think there's a fair amount
of work to be done there as well, but it's good to start
somewhere.<br>
</p>
<p>It's important that there is possibility for discussion of these
potential proposed changes, and I would encourage anyone who has
thoughts on the matter to provide feedback by replying to this
email.<br>
</p>
<p>Best regards,</p>
<p>- [FVP]<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 22/3/19 11:35 am, Felix von Perger
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9c3a76a5-466c-5bc2-ee51-37973378e621@ucc.asn.au">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p>Hi all,</p>
<p>Below is a diff of the <a moz-do-not-send="true"
href="https://github.com/ucc/regulations">current regulations</a>
to my local copy in <tt>/home/wheel/frekk/regulations/README.md</tt>.</p>
<p>Note that this is a draft and I'm open to feedback. Please let
me know if you think anything here can be improved.<br>
</p>
<p>I'm proposing a few changes - in summary;</p>
<ul>
<li>Clarifying the group application processes for Door and
Wheel, bringing back the LOLCATDOG</li>
<li>Defining a procedure for wheel to grant sprocket, winadmin
and webmasters<br>
</li>
<li>Defining a co-location policy</li>
<li>Ensuring dispense credit is accepted as donations</li>
</ul>
<p> </p>
<blockquote type="cite">
<pre><font color="#8a2be2">diff --git a/README.md b/README.md</font>
index 5a93eb4..3e483fc 100644
<font color="#0000ff">--- a/README.md</font>
<font color="#800000">+++ b/README.md</font>
<font color="#00ff00">@@ -5,8 +5,6 @@ This document constitutes a complete list of all current UCC Committee Regulatio</font>
- The Committee shall make every reasonable effort to clearly communicate all responsibilities and tasks to the members to whom they apply
- The Committee may require a member sign a statement that they are aware of their responsibilities
<font color="#ff0000"><span style="background: #d7d7d7">- </span></font>
<font color="#ff0000"><span style="background: #d7d7d7">-- Members wishing to apply to join any group are ecouraged to contact committee in writing</span></font>
- Members shall adhere to the [Club Service Usage Guidelines](#usage_guidelines)
<font color="#00ff00">@@ -26,6 +24,7 @@ This document constitutes a complete list of all current UCC Committee Regulatio</font>
- The Committee will afford powers to Door members so that they may fulfil these responsibilities
- An absolute majority of the Committee may remove Door members or call for their reapplication as they see fit
- See the [Door Group Manual](#door_manual) for technical details about Door
<font color="#008000"><span style="background: #e7e7e7">+ - Members wishing to apply to join the Door group are encouraged to complete the [LOLCATDOG](#lolcatdog) and send it to [Committee and Door](<a class="moz-txt-link-freetext" href="mailto:committee@ucc.asn.au?cc=door@ucc.asn.au&subject=Door%20Application" moz-do-not-send="true">mailto:committee@ucc.asn.au?cc=door@ucc.asn.au&subject=Door%20Application</a>)</span></font>
- Committee and Door members may temporarily evict and ban individuals from the room (known as 'dooring' or 'being doored')
- The dooring may be conditional, for example on time or behaviour
<font color="#00ff00">@@ -41,8 +40,16 @@ This document constitutes a complete list of all current UCC Committee Regulatio</font>
- To adhere to the [Wheel Group Ethical Guidelines](#wheel_ethics)
- The Committee will afford powers to Wheel members so that they may fulfil these responsibilities
- An absolute majority of the Committee may remove Wheel members or call for their reapplication as they see fit
<font color="#008000"><span style="background: #e7e7e7">+ - Members wishing to apply to join the Wheel group may do so by contacting [Committee and wheel](<a class="moz-txt-link-freetext" href="mailto:committee@ucc.asn.au?cc=wheel@ucc.asn.au&subject=Wheel%20Application" moz-do-not-send="true">mailto:committee@ucc.asn.au?cc=wheel@ucc.asn.au&subject=Wheel%20Application</a>)</span></font>
- Wheel members shall have administrator access to all club machines, and are responsible for administering such access
<font color="#008000"><span style="background: #e7e7e7">+ - Wheel members may, at their discretion, grant administrator access to a member, for any of the following;</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - Clubroom \*nix desktop machines (`sprocket`)</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - Clubroom Windows desktop machines (`winadmin`)</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - Club website (`webmasters`)</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - Any individual machine, where by the Wheel member's judgement, the security risk to other systems is limited</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - Upon granting a member such access, the Wheel member shall make every reasonable effort to communicate this to the Committee and other members of Wheel</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - Administrator access granted as per the above may be challenged at the next Committee meeting</span></font>
- Wheel members may lock and unlock member accounts
- Accounts may be locked if:
<font color="#00ff00">@@ -54,10 +61,17 @@ This document constitutes a complete list of all current UCC Committee Regulatio</font>
- A club member may be rewarded with dispense credit for performing certain services for the club
- Emptying a full bin: 96c
- Restocking the coke or snack machine: 128c
- Driving a food run: 512c
<font color="#008000"><span style="background: #e7e7e7">+- A club member may co-locate a machine on club premises with permission of the Committee</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - At least two Wheel members shall be nominated, and granted administrator access to the co-located machine, by the club member</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - Such administrator access should be possible from within the club network</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - Wheel members should make an effort to inform the owner of a co-located machine when accessing it administratively</span></font>
<font color="#008000"><span style="background: #e7e7e7">+ - Usage of club resources by co-located machines shall be in accordance with the [Club Service Usage Guidelines](#usage_guidelines)</span></font>
<font color="#008000"><span style="background: #e7e7e7">+</span></font>
- Donations to the club must be reported to the Committee, and are considered to remain the property of the donor until they are accepted by the Committee, at which point they become the property of the club
<font color="#008000"><span style="background: #e7e7e7">+ - All monetary additions to a club member's dispense credit are automatically accepted as donations to the club and are non-refundable</span></font>
- The club shall abide by the [Joint Event Subcommittee Regulations](<a class="moz-txt-link-freetext" href="https://github.com/gozzarda/subcommittee_regulations" moz-do-not-send="true">https://github.com/gozzarda/subcommittee_regulations</a>)
<font color="#00ff00">@@ -126,8 +140,44 @@ The following is intended as a quick reference guide for Door members</font>
- In the event of a fire or other emergency, evacuate in accordance with [University Emergency Procedures](<a class="moz-txt-link-freetext" href="http://www.safety.uwa.edu.au/incidents-injuries-emergency/procedures" moz-do-not-send="true">http://www.safety.uwa.edu.au/incidents-injuries-emergency/procedures</a>), closing the room if it is empty and safe to do so
<font color="#ff0000"><span style="background: #d7d7d7">-Appendix C: Wheel Group Ethical Guidelines <a name="wheel_ethics"></a></span></font>
<font color="#008000"><span style="background: #e7e7e7">+Appendix C: LOLCATDOG <a name="lolcatdog"></a></span></font>
<font color="#008000"><span style="background: #e7e7e7">+---------------------</span></font>
<font color="#008000"><span style="background: #e7e7e7">+</span></font>
<font color="#008000"><span style="background: #e7e7e7">+The following is the Largely On-Line Coke Aptitude Test and Door Official Grading. Door group applicants should answer all questions and submit their answers to the committee (<a class="moz-txt-link-rfc2396E" href="mailto:committee@ucc.asn.au" moz-do-not-send="true"><committee@ucc.asn.au></a>) and Door group (<a class="moz-txt-link-rfc2396E" href="mailto:door@ucc.asn.au" moz-do-not-send="true"><door@ucc.asn.au></a>) mailing lists. Ask a member of Door, Wheel, or the committee if you need help.</span></font>
<font color="#008000"><span style="background: #e7e7e7">+</span></font>
<font color="#008000"><span style="background: #e7e7e7">+### Open Questions</span></font>
<font color="#008000"><span style="background: #e7e7e7">+1. Why do you want to be on Door?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+2. What difference will putting you on Door make?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+</span></font>
<font color="#008000"><span style="background: #e7e7e7">+### Policy Questions</span></font>
<font color="#008000"><span style="background: #e7e7e7">+3. Where would you find the Door Group policy?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+4. Why do we have door members?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+5. Who should you contact with questions/concerns about the policy?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+6. How does committee officially contact Door members?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+</span></font>
<font color="#008000"><span style="background: #e7e7e7">+### Practical Questions</span></font>
<font color="#008000"><span style="background: #e7e7e7">+7. What is the vending machine code to unlock the door?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+8. If someone is violent, refuses to leave, or otherwise poses a danger to people or property, you should call UWA Security. What is their number? Give both the emergency and non-emergency numbers.</span></font>
<font color="#008000"><span style="background: #e7e7e7">+9. Briefly describe how the door system works (describe how the above code actually unlocks the door).</span></font>
<font color="#008000"><span style="background: #e7e7e7">+10. If you are unable to unlock the door from the snack machine, how else should you open the door? Give both methods.</span></font>
<font color="#008000"><span style="background: #e7e7e7">+11. Who has clubroom keys on their person and who is able to get the clubroom key out from the Guild Student Centre?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+12. What needs to be done when closing the clubroom?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+13. What needs to be done when leaving Cameron Hall?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+14. If you are unable to correct an issue with something in the clubroom, who should you inform?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+</span></font>
<font color="#008000"><span style="background: #e7e7e7">+### Dispense Questions</span></font>
<font color="#008000"><span style="background: #e7e7e7">+15. What is your current dispense account balance?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+16. What is the current balance of the account zanchey?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+17. Where is the dispense log kept?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+18. What was the first drink dispensed this year?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+19. Name someone who is able to open the vending machines.</span></font>
<font color="#008000"><span style="background: #e7e7e7">+20. How would you rename slot 5 of the coke machine to vanilla coke?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+21. How would you disable slot 33 of the snack machine?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+22. What is wrong with this command: `dispense acct Zanchey +500 "money in safe bag 54"`?</span></font>
<font color="#008000"><span style="background: #e7e7e7">+</span></font>
<font color="#008000"><span style="background: #e7e7e7">+Appendix D: Wheel Group Ethical Guidelines <a name="wheel_ethics"></a></span></font>
------------------------------------------
<font color="#008000"><span style="background: #e7e7e7">+</span></font>
</pre>
<style type="text/css">pre { font-family: "DejaVu Sans Mono", monospace; font-size: 10pt; background: transparent none repeat scroll 0% 0%; }p { margin-bottom: 0.25cm; line-height: 115%; background: transparent none repeat scroll 0% 0%; }</style></blockquote>
</blockquote>
</body>
</html>