cms-dev
[IOI fork parity] Notice task type
implementation: https://github.com/ioi-2024/cms/commit/2af71ca8e052a574273b4a186a801706be373860
I am not sure this is the best way to implement notices... @gollux, any thoughts on this?
What are task notices exactly? I have a rough idea, but it would be great to spell it out and have a precise list of software requirements for their implementation.
e.g. is it just a task-specific PDF (or maybe contest-specific?) that we want to expose to users? Most likely there is a better way than creating a dummy task.
it's a contest-specific PDF that needs to be translated. here's the 2023 IOI notice for example: https://ioi2023.hu/wp-content/uploads/2023/08/d1-notice-ISC.pdf
OK, what if we allowed the Attachment entity to be connected to a Contest? (instead of just to a Task)
attachments can't be translated. notices are much more like statements than attachments, so imo it would be more logical to allow statements to be attached to contests instead of tasks if we wanted to implement it like this.
Agreed, we probably should implement it as statement-like objects attached to contests.
Just noting that we didn't have a Notice at IOI 2024 and won't have one this year either. A similar document is published weeks before the IOI, much like the Contest Rules. Additionally, the same document will be included in the contestant VM as a static HTML file. So I believe this isn't a high priority - though you're of course welcome to decide whether you'd like to work on a long-term solution for supporting such a feature in CMS :)
Given that I am not aware of a real use case for this, I will close the issue for now.