Event scheduling utility

[trungams]

Feature/Enhancement Description

One of my initial intentions when this website was started is to provide a common platform for local speedcubers to create, announce and manage meetups or small unofficial competitions, and ultimately WCA competitions. It would be amazing if we can integrate OAuth from WCA for user verification, too.

Tasklists Suggestion

• [x] Design a user model. Only logged in users can create and manage events
• [x] Integrate WCA's OAuth system for logging in/out
• [x] Design an event model. We also need to categorize our events (e.g: cubers meetup, unofficial competition, WCA competition, etc)
• [ ] Back-end views
• [ ] Provide a front-end for it

Additional Comments

[trungams]

Note: remember to reconfig mysql on the deployment server, to avoid the django models behaving weirdly

[kutycoi123]

• If a paid event is not full, all users who want to register for this event must complete the registration by paying the fee. If the event is full, users can submit registration without paying, however, this registration will be considered as pending. Once there are available slots, pending registrations have to be paid within an amount of time to be accepted.

[trungams]

Note: changes should be made in branch issue-10 before merging to master

[trungams]

@kutycoi123

• An event can, and should have multiple organizers, along with WCA delegates.
• What are is_chargeable and is_open in CubingEvent?
• Would it make sense to also have a schedule field for each event? It can simply be a user uploaded pdf (or permalink to the pdf).
• Since we're not doing payment yet, should we just exclude all the fee related fields in our models?
• A registration, besides user information, should also store some info regarding the competition, i.e what events is the user participating in, guest, special requests, additional comment.

[kutycoi123]

• is_chargeable: This field is set False for any unofficial events and True for wca events for which users need to pay
• is_open: True if event is still open, false if event is closed or coming soon? This field doesn't help much so we can remove it.
• Yes we should have fields for something like prizes, schedule, policy and so on.
• Yes we can exclude all fee related fields for now.
• Agree! All information regarding the competition or event should also be included in registration.

[kutycoi123]

• Hosts for unofficial event like meetup, offline, etc, can be anyone who wants to host the event. However, for official WCA event, hosts must be WCA delegates.
• In CubingEvent, I added info_url field which will be a link to file containing all other information about event
• In Completed_Registration and Pending_Registration, I added some more fields to provide more information about a registration.
• In Person, I deleted two fields is_valid_to_create_unofficial(official)_event and added isDelegate which can be helpful to check if a person can host a WCA event or not.

[trungams]

• The current model in our website is called Cuber. I'll change it to Person to be more generic, and we can create a Delegate model to subclass it too.
• I mean a competition can have many individual organizers. Delegates need not be a organizer/host, their responsibility at official events is usually supervising, so I'm suggesting we have separate organizers and delegate fields in an event. Both require ManyToMany relationship with another table in our database. The latter can be null for casual offlines/meetups.
• Is the design for events based off WCA's competition model? I feel like we're missing something important. Seeing this page for example: https://www.worldcubeassociation.org/competitions/HoChiMinhLetsCube2019. It contains way more information than what we're having right now (prizes, schedule, registration requirements, etc). Tbf we can just use a text field for those kind of info, even for schedule, which is just simply a url

[trungams]

The other 3 are good

[kutycoi123]

• Organizer doesn't need to be a person. For example, organizer for Hanoi Open 2018 was Rubik Ocean which is not a particular person, so it might get a Text field.
• WCA has a lot more information because it has more complicated models and relationships to maintain details of all events, rounds, prizes, etc, related with competitions. For us, I think we should keep it simple by having a url storing the files or a direct link to wca competition page.

[trungams]

• Agreed. But we should somehow let the organizer manage events (contents, registrations) without having a WCA account?
• Just had a look at some competitions which handle registrations on a different site rather than WCA, and yeah they seem to put info on WCA page as well. I guess we can follow them.

[trungams]

For reference: https://www.worldcubeassociation.org/competitions/AjaxWinter2019. It links to the registration page at http://www.canadiancubing.com/Events/AW2019

[kutycoi123]

• In that case, we should provide users two different way to create an account on our page. First way is through OAuth api, second is to create an acc without wca id. We need to add constraints for people who use latter method, like these people can only create or attend unofficial events.

[trungams]

Guess I can't avoid password authentication :frowning_face: In this case we need to modify the Person model, adding a username and password field. And maybe every user will have an option to connect with their WCA account?

[kutycoi123]

• Exactly, when users signup, we allowed them to either connect with their wca id or just create an account with password and connect with wca id later on. So basically, we provide two methods for signup and login, users can use either or both of them.

[trungams]

But for consistency, should we require login with password for both cases? It's just that the ones who connect with their WCA accounts don't have to fill in their personal information when signing up

[kutycoi123]

• I think we should have 2 models: WcaCuber and NonWcaCuber
• Users who have account with wca id can only login using wca id => WcaCuber
• Users who don't have wca id can only login using their own usernames and passwords => NonWcaCuber
• After users link their accounts with wca id, they will not be able to use their passwords and be forced to login using wca id. => NonWcaCuber -> WcaCuber

[trungams]

Not entirely sure if you can enforce that. Imo users should have the rights to login however they want.

[trungams]

Stuck on my other project :cry: will try to push some model prototype today

[trungams]

Looks like we will need to separate our view into modules but I'll do it once we finish this issue