cms-dev / cms-dev/cms

Divisions within a contest

Open
#1,353 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature_request
Dominant language
Python
Stars
1k
Forks
412
Avg merge
6d 10h
Merged PRs (30d)
3

Description

This one is quite a lot more niche than my other issues I think, but maybe still worth discussing :)

In the Estonian olympiad, we have a system where high-schoolers have 6 tasks available, and their score for the contest is the sum of their top 3 tasks. However, middle-schoolers (by default) only have the first 4 tasks, and all 4 count for their score.

We implemented this by adding a feature that allows hiding some tasks for some users (grouped into divisions), and later I also implemented the scoring rules (which used to just be excel formulas in the results spreadsheet) into CMS, allowing each division to have a different scoring mode. ("scoring mode" is already an overloaded term though.... need to think of better terminology). This also involved implementing the scoring rules in RWS, and allowing filtering the ranking to a specific division.

Would any part of this be a candidate for upstreaming? Or are our rules too weird? :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the existing division-based task visibility, per-division scoring, and division-filtered ranking work in CMS and RWS. First determine which parts are already implemented locally and whether the rules can be generalized beyond the Estonian olympiad example. Done would be a decided upstream scope, with terminology and affected components documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.