Étienne Beaulé

I do think this PR is still pertinent as it would make it so I wouldn't have to override an unrelated method as I currently do.

I repeat.

The API also provides a standardized JSON format for breaking teams (`GET /v1/tournaments/{tournament_slug}/break-categories/{id}/break`) and speaker standings (`GET /v1/tournaments/{tournament_slug}/speakers/standings`).

I'd be interested in exploring venue allocation. There are many more possible objectives than what it seems here; to get everyone to walk the same distance on average. I think...

Could be simple to use the Hungarian algorithm to assign debates to venues. This would entail needing to set weights (preferences?) for the constraints. As the two objectives are pretty...

Yeah, subsets are not really necessary, and the effect would be similar to just having venues in many categories. I do think however that venue optimisation is more than just...

Removing from WUDC 2022 as it'll be online.

Maybe for the 2nd: `As People | As Teams`

Fixed with #2113 (15db67c63b1659528cd57498bb802a2055d002de)

Ranking annotators are what gets ordered; without them the order would be arbitrary. A better solution in my view would be to skip subrank annotators if inapplicable.