Milestones
List view
We want the interface to be streamlined and ready for collecting lots of debate data by a couple weeks into Spring semester. There are a bunch of features we want to have done by then to make this happen. Things we want: 1) A built-in system for automatically scheduling new debates, which automates the tedious stuff which doesn't change (e.g., balancing load between debaters, trying to get debaters to debate a diversity of opponents while maintaining randomness, etc.) while allowing for control of the stuff that does (e.g., who is available and what is their capacity, what rules do we want, etc.). This may be a pre-scheduling system or some kind of matchmaking system. 2) Separate processes for debates with and without judge involvement. We need to decide how debates will end when there's no judge (e.g., fixed-length debates, or ending by mutual agreement between debaters) and create a separate data stream for offline judging (where, e.g., multiple judges can judge the same debate). 3) Built-in feedback forms, so we don't need to rely on people remembering to fill out separate Google forms, and so we have all of the data together in one place on the server. 4) General streamlining and usability improvements. And maybe more.
Overdue by 3 year(s)•Due by January 27, 2023•21/27 issues closed