[committee] SOC feedback form - draft responses

[Felix von Perger]

Hi all,

Here are my proposed responses to the SOC feedback form
https://docs.google.com/forms/d/1Ulv0Z1Z8lXk263CvWfIKyuL48MIY8Ds3OaItEv5a9CE/viewform
which will be discussed at the meeting with SOC and other Cameron Hall 
presidents on Friday (tomorrow).

Note that I haven't sent these yet, they are open for discussion. Please 
feel free to comment.

*
*
*SOC + Cameron Hall Collective Transparency Meeting*
How have you found the communication between your club and SOC compared 
to previous years?
> Overall, somewhat improved.

In 2019, has your club been faced with any issues or difficulties?
> Primarily, a number of important communications are occurring by 
> Facebook and not by email (or at best, they are sent out by email only 
> after a significant delay), and then being sent to individual student 
> emails rather than to the preferred contact addresses (ie. UCC has our 
> own committee mailing list and aliases, which we keep up to date). See 
> below for details.
>
> Somewhat less important is the number of clubs which have been 
> affiliated with similar purposes. UCC is now one of potentially 
> eight(!) Guild-affiliated computer-related clubs on campus (including 
> Data Science, CSSC, Programming Competition Society, Coders for 
> Causes, Robogals, EEEWA and UWA League Club), which would seem quite 
> excessive. This causes competition for memberships, as many of these 
> other clubs have overlapping target audiences, and results in a 
> division of resources which could otherwise be put to use working on 
> the same things. In general, however, the higher number of clubs is 
> not matched by a higher amount of funding for those clubs, and 
> stretches already thin resources even further. As such, SOC should 
> attempt to reduce the number of affiliated clubs by some fair and 
> reasonable means, and introduce stricter requirements for new 
> affiliations.

Is there any way that SOC can help alleviate or resolve the difficulties 
outlined in the previous question?
> Deleting or disabling all the SOC-related Facebook groups and using 
> only email for relevant communications, thus addressing the unfair 
> disadvantage of people who do not use Facebook.
>
> [Note: The UWA Student Guild should not be encouraging the use of 
> commercial advertising platforms such as Facebook in the first place, 
> least of all mandating its use for official purposes. The University 
> conveniently provides a number of IT services, including email, which 
> it uses effectively as the official method of communication.]

Generally, is there anything you think needs to be changed within SOC in 
order to make the job of your committee easier?
> 1. Put all the policies, rules, forms and documents in one place, so 
> that one does not have to attempt to navigate the website to find 
> things. (a single page on the website, with links to all the policies, 
> regulations and forms for everything that SOC / Tenancy has anything 
> to do with, or could possibly apply to clubs, including event 
> policies, EMPs/RMPs/camp/stall/pubcrawl forms, training programmes, 
> etc. would be very much appreciated)
>
> 2. For UCC specifically - send all SOC-related communications to 
> committee-only at ucc.asn.au (ideally this would be instead of sending to 
> our exec student emails, although if necessary, then just send it to 
> committee-only at ucc.asn.au as well).

- [FVP]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ucc.gu.uwa.edu.au/pipermail/committee/attachments/20190502/761dc309/attachment.htm