Computing Policy: Difference between revisions
From YSTV Documentation Wiki
(Removed comp social sec and changed from term to semester) |
|||
(4 intermediate revisions by 3 users not shown) | |||
Line 39: | Line 39: | ||
#There is no limit on the number of roles you can fill (at the discretion of the Computing Director). | #There is no limit on the number of roles you can fill (at the discretion of the Computing Director). | ||
#One week of notice will be given for a role being open. During the open week, any member can express their interest in the role to the Computing Director. | #One week of notice will be given for a role being open. During the open week, any member can express their interest in the role to the Computing Director. | ||
#At the end of this week,one of the following will occur: | #At the end of this week, one of the following will occur: | ||
##If no member has come forward, the Computing Director may appoint someone (with their consent) at the next computing meeting. | ##If no member has come forward, the Computing Director may appoint someone (with their consent) at the next computing meeting. | ||
##If one member has expressed interest, they can be appointed to the role by the Computing Director. | ##If one member has expressed interest, they can be appointed to the role by the Computing Director. | ||
Line 45: | Line 45: | ||
#If you wish to step-down, you must give one week of notice to the Computing Director. | #If you wish to step-down, you must give one week of notice to the Computing Director. | ||
#If you are no longer a student at the University of York, you will automatically be deemed to have stepped-down. | #If you are no longer a student at the University of York, you will automatically be deemed to have stepped-down. | ||
#All roles open for their week notice in week 5 | #All roles open for their week notice in week 5 Semester 1 and appointments made in week 6. | ||
#The Computing Director reserves the right to remove any of the roles or persons holding them. | #The Computing Director reserves the right to remove any of the roles or persons holding them. | ||
==Meetings== | ==Meetings== | ||
#Chaired by the Computing Director, if they are unavailable the Deputy Computing Director will chair. | #Chaired by the Computing Director, if they are unavailable the Deputy Computing Director will chair. | ||
#Both the | #Both the Computing Director and the Deputy Computing Director are required to attend; apologies need to be sent if not attending. | ||
#A computing meeting should be held at least once a term, ideally per-week if possible. | #A computing meeting should be held at least once a term, ideally per-week if possible. | ||
#Can be called by anyone on the computing team. | #Can be called by anyone on the computing team. | ||
#Unless in the case of an emergency, advance notice of at least 24 hours must be given for the meeting. | #Unless in the case of an emergency, advance notice of at least 24 hours must be given for the meeting. | ||
#The Deputy Computing Director or an appointee of the Computing Director/Deputy Computing Director should minute the meeting. | #The Deputy Computing Director or an appointee of the Computing Director/Deputy Computing Director should minute the meeting. | ||
[[Category:Admin]] | |||
[[Category:Computing]] |
Latest revision as of 18:26, 26 September 2024
Computing Service
- For any website maintenance that may affect availability of the website, the member responsible for the work must ensure that the website retains at minimum the same degree of functionality after maintenance as prior to maintenance, otherwise rollback the change or contact the Computing Team.
- Any Computing Service that is not public-facing should be secured by an authentication mechanism.
- Anything that is exposed on the public internet should be secured by HTTPS.
Team
- Any member can request to join the computing team. Can join with director or deputy computing director.
- Computing Team members will have administrator privileges and dedicated accounts to the Computing Services where possible.
- The Computing Director and Deputy will have the responsibility of keeping an up-to-date list of members of the Computing Team. This will be accessible to any member of the society.
Roles
- The following roles are available within the computing team, separate from the committee position of Computing Director and non-committee, officer position of Deputy Computing Director. These roles are not part of YSTV’s committee or officers, but assist the Computing Director and Deputy Computing Director.
- Development Coordinator
- Attend Computing Meetings
- Provide apologies/notice to the Computing Director or Deputy Computing Director if they are unable to attend.
- Coordinate YSTV’s development work and projects, including website and software development.
- Work with the Systems Coordinator to coordinate our development operations, including build pipelines.
- Work with the Computing Director/Deputy on providing training and coordinate the use of our version control/git.
- Systems Coordinator
- Attend Computing Meetings.
- Provide apologies/notice to the Computing Director or Deputy Computing Director if they are unable to attend.
- Coordinate the maintenance of YSTV’s devices and network and any upgrades, as necessary.
- Coordinate the documentation of YSTV’s infrastructure and setup.
- Work with the Development Coordinator to coordinate our development operations, including build pipelines.
- Work with the Computing Director on the safety and security of our computer systems/networks.
- Website Coordinator
- Attend Computing Meetings.
- Provide apologies/notice to the Computing Director or Deputy Computing Director if they are unable to attend.
- Coordinate the running of YSTV’s web properties, ensuring they are up to date and providing assistance to other society members who need to access/edit them.
- Work with the Computing Director/Deputy on providing training and coordinate the use of our website upload system, and liaising with YSTV’s Head of Presentation.
- Production Coordinator
- Attend Computing Meetings.
- Provide apologies/notice to the Computing Director or Deputy Computing Director if they are unable to attend.
- Attend Production Meetings.
- Provide apologies/notice to the Computing Director or Production Director if they are unable to attend.
- Liaise with the Production Director and team on upcoming productions and their computing requirements.
- Ensure a competent member of the computing team is available for any production that requires it, with the assistance of the Computing Director/Deputy.
- Work with the Computing Director/Deputy on training and use of our vision mixing and livestream tech.
- Development Coordinator
- There is no limit on the number of roles you can fill (at the discretion of the Computing Director).
- One week of notice will be given for a role being open. During the open week, any member can express their interest in the role to the Computing Director.
- At the end of this week, one of the following will occur:
- If no member has come forward, the Computing Director may appoint someone (with their consent) at the next computing meeting.
- If one member has expressed interest, they can be appointed to the role by the Computing Director.
- If more than one person has expressed interest, a vote will be held at the next computing meeting with this being announced to the society for anyone who wants to attend.
- If you wish to step-down, you must give one week of notice to the Computing Director.
- If you are no longer a student at the University of York, you will automatically be deemed to have stepped-down.
- All roles open for their week notice in week 5 Semester 1 and appointments made in week 6.
- The Computing Director reserves the right to remove any of the roles or persons holding them.
Meetings
- Chaired by the Computing Director, if they are unavailable the Deputy Computing Director will chair.
- Both the Computing Director and the Deputy Computing Director are required to attend; apologies need to be sent if not attending.
- A computing meeting should be held at least once a term, ideally per-week if possible.
- Can be called by anyone on the computing team.
- Unless in the case of an emergency, advance notice of at least 24 hours must be given for the meeting.
- The Deputy Computing Director or an appointee of the Computing Director/Deputy Computing Director should minute the meeting.