matiasilva / gsb-ticketing Goto Github PK

See TODO in Ticket model

One of the formatting modules is not understanding that it's formatting a Django template and therefore indents things incorrectly and breaks the page. See the signup.html template.

We use ZohoMail and all the DNS records have been set up, no work needed here. The only thing to do is:

• clean up all mailboxes (a lot of email from 2020)
• reset passwords
• make passwords available to new committee
• ask exec about who should get an email address

On launch night, we need to enforce quotas for certain ticket types. These should also be restricted by user status, ie. alums should have 100 tickets reserved for them, of which 40 are Queue Jump.

The use of the word robust is related to race conditions, which can occur with counters (if we choose to do that). Django has an "F" class that solves this.

This ensures nobody else apart from us can request data

Hosted in the matiasilva/gsb-web repo. Needs a lick of paint, information updating and uploading to Netlify. Perhaps for now we could put some big teaser up.

This will help us roll back if our platform fails. Also just good to know who edited who and when.

View all tickets purchased
View any pending alumni/non-raven requests
Be able to respond to pending requests

This can use python-social-auth or Django's native auth module. Might as well use the former since I've put so much work into plumbing the pipeline.

Only machines on the CUDN have access to Lookup, so test on SRCF.

Use python-social-auth to successfully log users in. A custom pipeline stage needs to ask the users to confirm their full names and emails.

is_own enforces that users can only have one ticket for themselves (ie where the fields are greyed out with their name) but it should also enforce that they cannot buy a ticket type that is not is_own if they don't already have a ticket!