Nicky Gerritsen

For the roles: I don't like adding all these roles...

> > For the roles: I don't like adding all these roles... > > I meant an internal role not one in the GUI, so instead of check for ROLE_JURY...

That is not what I'm suggesting. What I want to do is in this method: http://github.com/DOMjudge/domjudge/blob/main/webapp/src/Controller/Jury/ScoreboardController.php#L42-L42 set the `$jury` param only to true if you have the `ROLE_JURY`, otherwise set...

> > That is not what I'm suggesting. What I want to do is in this method: [http://github.com/DOMjudge/domjudge/blob/main/webapp/src/Controller/Jury/ScoreboardController.php#L42-L42](https://github.com/DOMjudge/domjudge/blob/main/webapp/src/Controller/Jury/ScoreboardController.php#L42-L42) set the `$jury` param only to true if you have the `ROLE_JURY`,...

A separate interface would also be fine. But I agree with that the jury should probably also see the public scoreboard. We even link to it from the jury scoreboard...

What is the actual usecase for seeing the scoreboard as a balloon runner? Just wondering.

Depending on how we do it (the clean way or the fast way) this is non trivial. I wonder if 'for fun' is a good argument, but I'm also not...

The API spec now has fields for compiler flags (and run stuff), which is probably the spec we want to go with.

https://ccs-specs.icpc.io/master/contest_api#languages see `compiler` and `runner`

Maybe only do it for external judgements? The analyst once aren't external.