Landon Curt Noll
4ee4c731f7
While not strictly necessary, replacing the two ASCII tab characters in the markdown copyright comment makes it easier to detect problematic TAB indentation within markdown files. After this commit, only 90 markdown files have leading ASCII TAB characters. And again, while not strictly necessary, we can consider running expand on those 90 markdown files to see what effect that might have on the HTML files they produce. Replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters (the default action of the `expand(1)` tool) might have an negative effect on some HTML formatting where **hack-a-round** formatting was attempted to fix broken indentation caused by problematic ASCII TAB characters. Think of this as a baseline for evaluating leading TAB characters within markdown files. TODO: Consider either using `expand(1)` to replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters AND/OR modifying the appropriate `bin` tool to convert leading ASCII TAB characters into multiples of 8 ASCII SPACE characters.
5.0 KiB
format
The following JSON members are required to be present status.json.
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"
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".
The current status of the IOCCC.
The following JSON member value string may be one of the following JSON quoted strings:
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.
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".
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 and announce them on the @IOCCC mastodon feed.
-
Notify the authors of entries that won the IOCCC via email using their registered email address.
-
Announce who the authors are 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 website, 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 entries that have won the IOCCC.
NOTE: From time to time, winning IOCCC entries may have their write-ups updated,
Makefiles improved, source code fixed etc. See IOCCC news for details.
Watch both this IOCCC status page and the @IOCCC mastodon feed for information about future IOCCC openings.
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.
NOTE: 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.
This shows the latest modification date of 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.
NOTE: 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.
Jump to: top