Changed `bin/gen-status.sh` VERSION from "1.0 2024-03-09" to "1.1 2024-03-10". Changed `bin/status2html.sh` VERSION from "1.0 2024-03-09" to "1.1 2024-03-10". Improved for explanatory text added near the top of the `index.html` page by `bin/status2html.sh`. While `bin/status2html.sh` in intended as tool that is internally called only, we allowed for a 0 arg use for those who are simply curious as to what it does. Tested various _contest_status_ values with `bin/gen-status.sh`. This resulted in a forced change of _status_update_ in `status.json`. Removed extraneous whitespace from `bin/output-index-author.sh`. Performed `make www` to finalize all of the above, although a `make gen_status` followed by `make gen_sitemap` would have been sufficient.
4.0 KiB
format
The following JSON members are required to be present status.json.
no_comment
This is a mandatory comment for which we offer no comment other than this comment. :-)
The JSON member value must be the following JSON quoted string:
"mandatory comment: because comments were removed from the original JSON spec"
IOCCC_status_version
This is the version of format of the status.json file.
The JSON member value of is a JSON quoted string the form "version YYYY-MM-DD".
This document describes version "1.0 2024-03-09".
contest_status
The current status of the IOCCC.
The following JSON member value string may be one of the following JSON quoted strings:
"pending"
The IOCCC is not yet open, however there is a tentative scheduled date and time by which the IOCCC will open for submissions.
A preliminary IOCCC rules, guidelines, and tools have been posted. Comments and suggestions on these preliminary items are welcome. See the IOCCC news for details including the tentative scheduled opening date.
"open"
The IOCCC is open for submissions.
See the IOCCC news page for details on rules, guidelines, tools and deadlines.
Be sure to review the official IOCCC rules, guidelines, and tools for any changes that may have been made while the IOCCC was "pending".
"judging"
The IOCCC is closed to new submissions. The IOCCC judges are in the process of judging the submissions they received while the IOCCC was open.
Watch the @IOCCC mastodon feed for updates.
Once the IOCCC closes, the judges will:
-
Select the winning entries announce them on the @IOCCC mastodon feed.
-
Notify the authors of entries that won the IOCCC via email using their previously registered email address.
-
Announce who are authors of this year's winning IOCCC entries via the @IOCCC mastodon feed.
-
Upload the winning code to the Official IOCCC winner repo
-
Update the Official IOCCC web site, and in particular display this year's winning IOCCC entries at the top of the IOCCC winning entries page.
-
Update the IOCCC news page.
"closed"
The IOCCC is closed and is NOT accepting new submissions.
See the IOCCC winning entries page for the entires that have won the IOCCC.
NOTE: From time to time, winning IOCCC entries may have their write-ups updated, Makefiles improved and source code fixed. See IOCCC news for details.
Watch both the IOCCC status page and @IOCCC mastodon feed for information about future IOCCC openings.
news_update
This shows the latest modification date for the IOCCC news page.
The JSON member value is a JSON quoted string obtained from the date field
of the following ls(1) command:
TZ=UTC ls -D '%FT%T+00:00' -ld news.html
NOTE: The date and time are given with respect to UTC timezone.
Sorry: It is possible that for some reason, the IOCCC news page was modified without the content being changed. While we will try to minimize the cases where this happen, we apologize in advance (Sorry tm Canada 🇨🇦) when it does.
status_update
This shows the latest modification date status.json file.
The JSON member value is a JSON quoted string obtained from the date field
of the following ls(1) command:
TZ=UTC ls -D '%FT%T+00:00' -ld status.json
NOTE: The date and time are given with respect to UTC timezone.
Sorry: It is possible that for some reason, the status.json file was modified without the content being changed. While we will try to minimize the cases where this happen, we apologize in advance (Sorry tm Canada 🇨🇦) when it does.