Homepage: http://cms-dev.github.io/
🌍 Help translate CMS in your language using Weblate!
CMS, or Contest Management System, is a distributed system for running and (to some extent) organizing a programming contest.
CMS has been designed to be general and to handle many different types of contests, tasks, scorings, etc. Nonetheless, CMS has been explicitly build to be used in the 2012 International Olympiad in Informatics, held in September 2012 in Italy.
For end-users it's best to download the latest stable version of CMS, which can be found already packaged at http://cms-dev.github.io/.
This git repository, which contains the development version in its main branch, is intended for developers and everyone interested in contributing or just curious to see how the code works and wanting to hack on it.
To learn how to install and use CMS, please read the documentation, available at https://cms.readthedocs.org/.
If you have questions or need help troubleshooting some problem, contact us in the chat on Telegram, or write on the support mailing list [email protected], where no registration is required (you can see the archives on Google Groups).
To help with the troubleshooting, you can upload on some online pastebin the
relevant log files, that you can find in /var/local/log/cms/.
If you encountered a bug, please file an issue on GitHub following the instructions in the issue template.
Please don't file issues to ask for help, we are happy to help on the mailing list or on Telegram, and it is more likely somebody will answer your query sooner.
You can subscribe to [email protected] to receive announcements of new releases and other important news. Register on Google Groups.
For development queries, you can write to [email protected] and as before subscribe or see the archives on Google Groups.
CMS has been used in several official and unofficial contests. Please find an updated list at http://cms-dev.github.io/testimonials.html.
If you used CMS for a contest, selection, or a similar event, and want to publicize this information, we would be more than happy to hear from you and add it to that list.
If you (or your agent) believe that you found a security vulnerability in CMS, please follow these steps:
-
Ensure that the security issue can actually be reproduced.
-
Check that the vulnerability is compatible with CMS's threat model. In particular:
- A "vulnerability" caused by a configuration key that explicitly mentions needing modification is not a vulnerability.
- CMS assumes that the network that services will use for RPCs is trusted. Anything that can be triggered by sending RPCs only is not a vulnerability.
-
If you did (1) and (2), please open a GitHub Security Advisory under the "Security" tab.