Officer Automation

[EarthenSky]

This is a big project that will revolve around re-writing the automation system for exec access to github, bitwarden, google drive, and more! This also requires a system for permissions management.

This depends on the admin dashboard existing & the elections system to work as well.

Initial Tasks

• sketch out how the exec cycle, including elections will work, and what the roles of the DoA, SysAdmin, Pres, and VP are in the system.
• create subsystems that would implement the above sketch

Tasks

• Store Executive info in table #16
• Create a basic admin dashboard which lists current and past executive and their info #17
• Create an MVP for the admin dashboard csss-site-frontend#10
• media api #18
• create frontend page for executives to input their info csss-site-frontend#8
• public exec info page csss-site-frontend#9
• store info about all users #19
• [Feature] move old sites from csss-site to the frontend csss-site-frontend#2

Future Tasks

• control access of users to github #20
• control access of execs to google drive #21
• control access of execs to bitwarden #22
• control acces of execs to discord #23
• Control Executive transitions #24
• Transfer historical data where possible

Elections Subsystem

• TODO: this

Far Future Tasks

• TODO: figure out what tasks are left before we can switch new.sfucsss.org to sfucsss.org
  • once everything is working, switch over one at a time. Start by having them be in superposition, where both exist at the same time. Then switch once there are no bugs.

[EarthenSky]

Our main system diagram for the backend https://drive.google.com/file/d/13NqygQkSgtT0qhlgOgL7CQ4mvWH3OwQI/view?usp=sharing

[modernNeo]

and just think, I had to implement this shit all myself with little to no prior web-dev experience 😛 interested to see how yall tackle it 😂