Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

Note

Superseded by 2023 Projects Structure (Patch Notes [1])

This is the exec’s initial proposal to split off Projects into its own society, CSESoc Projects, based off of Shrey’s and Tom’s first draft. We might have missed something since we’re approaching this from an external perspective, so if we’ve forgotten something or you want to add in your thoughts, please read and comment below! This is also in preparation for the upcoming meeting to discuss and finalise this proposal! 🥳

Rationales for our suggestions are written in the purple boxes.

Objectives

  • ✂ Split the administration of Projects off from the main CSESoc Body.

  • 🌱 Allow for longer-term planning and growth on the part of the Projects body.

  • ⬇ Reduce the size of CSESoc by 3 directors to allow more internal growth.

Structure - 3 Levels

(blue star)

...

5 Execs (elected) (previously Project Directors)

All execs are responsible for looking after each project.

...

  • 2x Co-President

  • one

    1x Treasurer

    • also does Arc Delegate responsibilities

    • the other does GEDI responsibilities

    1x Treasurer
    • Secretary responsibilities

  • 1x CTO / Technical Officer

    also does Secretary responsibilities

    (name pending)

    • liase with CSESoc regarding CSESoc’s technical requirements and infrastructure

  • 1x HR

    • one also does Arc Delegate responsibilities

    • the other does GEDI responsibilities

VPs don’t make sense since VPs are for managing multiple teams in a portfolio. CSESoc Projects doesn’t have any portfolios.

👨‍🏫👩‍🏫 ~17 Directors (chosen by execs) (previously Project Leads)

  • 1-2x Project Directors (name TBD) per Project

    • Each project responsible for running one society bonding event per year.

  • 1-2x Trainee Directors

...

  • 👐 CSESoc would devolve all projects, including CSESoc Website would be devolved to CSESoc Projects

    • If you stop maintaining our website we stop giving you money 😠The CSESoc Website must be maintained in a timely manner to reflect yearly changes and display up to date information to the CSE community and potential sponsors.

Since CSESoc Website could fall into either society, we think CSESoc Projects should take the website team. The website is still a project, and it should get the full support of Projects.

...

  • (blue star) CSESoc will also grant the CSESoc Projects CTO near-admin permissions in the Atlassian Suite, to properly set up Confluence spaces for their projects, and proper CI/CD with Jira.

    • Execs of CSESoc Projects will not be able to access https://compclub.atlassian.net/wiki/spaces/CP space.

    • Execs of CSESoc will not be able to access a CSESoc Projects Exec space, except the CSESoc Secretary since they are full admin of the Atlassian Suite.

    • The above can be ignored if both exec parties cbbs setting up permissions and they’re happy sharing

      • (which will probably happen)

Projects teams heavily use Confluence for documentation and Jira for sprint planning. Projects definitely could apply for their own license and set up their own Confluence and Jira, however:

  • time and effort

  • CSESoc piggyback off projects for its open-source license which is free and applying for another one could mean Atlassian shuts down the current instance of Confluence and Jira since we no longer have an “open-source” project that we said we had.

Overall it’s just easier to use the same instance of Confluence and Jira, especially when all the tickets and backlogs are already set up.

...

  • 💸 CSESoc will give CSESoc Projects at least $3000 per year. This number should be reviewed often.

This is an ESTIMATE NUMBER. CSESoc Projects needs to provide us a draft budget for us to confirm this amount. In 2022, the Projects team was allocated $2000.

Other Details

  • (blue star) CSESoc Projects would be Arc@UNSW affiliated.

    • Not a total requirement, if we can’t get affiliated we can always use CSESoc’s Arc Delegate

Arc affiliation is incredibly important to have someone who you can go to about things like bullying, misconduct, etc. Having Arc@UNSW is a guarantee that there will be someone to deal with that sort of stuff. It sets minimum standards on the constitution, etc.

There is precisely 0 reason to not arc-affiliate, and so much risk to not doing so.

EDIT: Since arc affiliation was rejected, the constitution should have strict grievance related procedures.

  • 🚪 CSESoc Projects would be primarily inwards focused, with limited responsibility for out-reach to CSE Students (i.e. they'd hold applications, but the intent would be that they don't run events that overlap with workshops for everyone, like a hub for development).

    • Open to community though as projects open-source

This is mainly to make sure there isn't "competition" between the two societies. Basically, CSESoc will not start their own software projects without checking in with CSE Projects; and CSE Projects won't run big events aimed outside the society without checking in with CSESoc.

  • 🤑 CSESoc Projects are discouraged restricted from having it’s own sponsors

CSESoc will give you all the money you need.

The below is strikethrough as the society will not be arc affiliated

Arc gives you like $2000 anyways if you’re Arc affiliated. Arc would also have a problem with a society spending too much on internals (and could potentially lose Arc affiliation)

What would a sponsorship package deal look like if CSESoc Projects were to get sponsors? For CSESoc, this involves marketing or advertising them, and hosting dedicated and shared events. CSESoc Projects is inwardly focused, so holding dedicated events doesn’t really make sense. This only leaves advertising. Advertisements on our projects is something the execs can decide in the future, but at this point in time, we don’t want to encourage anything that may lead to ads on our websites - it’s just not a good look. Another offer could be putting them at the top of Jobsboard, which isn’t fair to students either.

If money is an issue, you can always ask CSESoc for more, within reason.

If sponsors are giving too much money, we don’t want to create an environment where developers are being “paid”, either directly or indirectly. This is a volunteering student society, and introducing too much money could complicate things.

We recognise that sponsors allows a society to become self-sufficient, and this could definitely be something the society aims for in the future. But for now, we’re discouraging sponsors. Also we don’t wanna fight over sponsors between the two societes 😢

Next steps

  • 📣 CSESoc and CSESoc Projects will aim to have the same recruitment drive for Directors, but not Subcom

    • This may change in future years.

...