Relationship between CSESoc and Dev

If directors and exec do agree on splitting in some form (options 2 and 3 in the main doc), the Main and Dev exec have agreed to the following things to maximise our chances of Arc affiliating Dev as a new society:

A shared sponsorship pool

CSESoc and Dev would have a joint sponsorship drive (joint prospectus, both sides would be helping with raising money from companies). As a result, the sponsorship money will be shared as well - we would need to discuss the ratio after talking with Arc.

This arrangement already exists in other Arc-affiliated societies (for example, EngSoc and WIESoc). This was something that wasn’t in last year’s attempts to split off, and this only stands to benefit Dev more.

A shared events calendar

Dev will be allowed to run its own events (e.g. Techspire, Projects Showcase). However, because Dev events are rare and usually large in scale, a joint calendar will be created to ensure that Dev events do not draw people away from CSESoc events, and vice-versa (again, benefitting neither side).

This also means that Dev will not have an events team - because we do not have enough events, any events team will be underloaded for most of the year.

Communication

We also want to establish a way for CSESoc and Dev to remain in contact if we do split off - having 0 communication between the two societies benefits neither.

The Engineering societies in UNSW have established TOES (Team of Engineering Societies), which is basically a Discord server that the execs from all constituent societies are in and collaborations can happen easily. We want to establish something similar to this for next year, especially because the two societies will inevitably be linked (with a shared sponsorship pool, Confluence space etc.)