Closed vmcj closed 3 months ago
The jury role is sufficient (and often personalized) for problem import. So I would not do this but encourage users to create a jury account before doing so.
We could check whether there's a team associated in the import script and ask for confirmation to proceed if not?
The jury role is sufficient (and often personalized) for problem import. So I would not do this but encourage users to create a jury account before doing so.
Sounds reasonable
We could check whether there's a team associated in the import script and ask for confirmation to proceed if not?
That should be doable and is a better option.
Reopening as the intent doesn't match the code.
Currently a jury member can't upload problems via the GUI (and neither via API see: https://github.com/DOMjudge/domjudge/blob/0e3f272bafc63cf58bb6ce1f2a07b7fb04d15a34/webapp/src/Controller/API/ProblemController.php#L57)
@meisterT what should be changed? My original question or should we let jury members allow to upload problems? For the last part I would say using API_Writer is the better choice and maybe create a custom role for bapctools
so a jury member can't break config easily and only via certain tools?
We already do this in
dev
instances, but for production we always need the team as we import the jury submissions.This issue is mostly to describe what would be the disadvantages.