Skip to content
Bath CS Wiki

BathCS Admins

BathCS admins handover

To summarise, BathCS admins are the students who help manage the cs organisation on GitLab (usually the owners), which usually involves communication between societies.

Due to the technical expertise required for some positions, it has two implications:

  • Admins will not be elected, but will have to apply and get chosen by current society members
  • Admins may not be chosen every year, and will be replaced when needed
  • Choosing process will be started at the end of semester 1, so that incomers can be trained with the previous admins.

The layout of the admins should roughly be as follows:

  • At least two maintainers — This role requires programming experience and will manage the domain as well as maintaining current projects (or adding projects).

    • They should have “Owner” role in GitLab organisation

  • One organiser — This role is for communication between societies and making sure they actually respond to messages + will help manage the hand over procedure (this can be a maintainer, but the work load will be a bit more).

    • They should have “Developer” role in GitLab organisation

Choosing procedure

  • Email all Computer Science students with a signup form. Get the PAL leaders to add a section to their session to get more applicants

    This form should include a description about the person and why they think they are qualified to be an admin.

    Friends of friends may want to be asked if they want to join as I expect this might not be a popular volunteering role

  • Current computer science initiatives should have a meeting (with the current admins), to go through the submissions and decide on the next admins.

Handover

  • New admins should be given roles in GitLab — Recommended for the first couple weeks to assign them as “Developer” and then bump to “Owner” later on
  • New admins should be added to the VaultTub organisation. Again, they should start on “User” and then changed to “Owner” later on.

During the next couple weeks, the current admins should have meetings with the new admins and start to go over the different aspects of the organisation + link to wiki.

This may include training (especially in security info) — however please make sure all this information can be found on the wiki.

Nearer the summer holiday:

  • The new admins have their expected role
  • Old admins should be removed from the GitLab + VaultTub organisations (during/after the summer)