Visions

• Extend the current features of Chaos to match what Microsoft/Google forms offers.

  • More question types (multiple choice, drop-down menu etc.)

  • More features for admins (email sending, interview scheduling)

• Better user experience for both applicants and interviewers.

  • certain changes to restrictions on questions

• Refactor and reorganise our Backend to make it more developer friendly.

  • Reconsider the use of Diesel ORM

• Become the replacement for google forms + spreadsheets

• Make recruitment less doomed

  • Make the process more streamlined and provide intuitive non-clunky UX that makes everything less painful

• Make people want to apply to subcoms because of our based af ui (thoughts on the landing page?)

Goals & Direction

Question Types

• multiple choice

• drop-down menu

• preference ordering

New interviewer features & quality of life

• Sending emails

• meeting scheduling

  • Applicants and interviewers should be able to give their availability (like when2meet/talloc), and there should be some way to organise interviews (or at least make it easier) - can we integrate this with the google calendar/zoom/jitsi APIs?

• automated system for applicant ranking (whether to implement is still under discussion)

• Question categories

• Subquestions?

• More flexible marking system, allowing marking for individual questions/categories and flexibly change weighting of them

• Applicant filtering

• Change how role-question association works

  • Right now, a question can be associated with any (non-zero) number of roles, and the applicant’s answer will be duplicated for that question across all roles

  • This is unintuitive, and there aren’t many situations where you need a question in a subset >1 of roles but not all of them

  • We want to instead have questions that belong to the entire campaign, and then questions for role

General Improvements and refactoring

• Better authentications

• Finish the process of moving images out of database

Refactoring of ORM

• Diesel the one we currently use generate a humongous headache for our fellow devs whenever we need to do a migration.

• Alternatives to Diesel should be thorougly examined and researched before actions taken (SeaORM is the current suggestion). If the ORM proven to be much more friendly, we would have to refactor the BE to use the new ORM.

• This is of lesser priority since the potential change required is substantial.

Other new features

• Exporting to CSV (in case things broken down )