mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improve bin/status2html.sh, update news + status

Browse Source 
For the improvements to the script, besides a typo, a link to the FAQ
(for submitting entries) has been added and a link to the GitHub issues
page (the new issue page) has been added in the case where an unknown
status appears in the status.json file.

The news update is that more progress has been made in that one of the
longer files to check for invalid links is done (thanks file) and that
two long files are left but that instead of looking at those two first
the other html files will be looked at first as it's quite possible that
both will have to be updated in some way or another as the other files
are being edited. Indeed this has happened numerous times already. This
way will save time and prevent having to look at those files a second
time. It also notes that some of the top level html files have also been
reviewed (see below) and a link was fixed (added a <div id="news"> for a
link that was linked to). I am fairly certain that I also fixed some
formatting problems and some links were fixed as well.

The status.md/status.html file has been updated with some links added,
more div blocks (for each section describing the status.json file),
which are used, slight formatting updates and possibly some other things
as well. As for some of the links we might say that it's 'statuses all
the way down' :-)

With this commit I am happy to report that some other top level files
have also been verified for invalid links:

	judges.html
	news.html
	status.html

As the news.html file will be updated it is entirely possible that some
fixes will have to be made but the links up to and including 08 June
2024 (unless more changes are made today of course) need not be checked
again.

More top level html files (which include those in next/ and other
subdirectories that are not of the entries) also have to be checked but
these should also go relatively quickly.

Regenerated status.json file as the news has been updated.
This commit is contained in:
Cody Boone Ferguson committed 2024-06-08 09:24:16 -07:00
1 parent 3a125b9fc2
commit 7e63c97ab1
6 files changed
+205 -103
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

bin/status2html.sh
+6 -3
View File
@@ -20,6 +20,8 @@
#
# Copyright (c) 2024 by Landon Curt Noll. All Rights Reserved.
#
# ... with minor improvements made in June 2024 by Cody Boone Ferguson.
#
# Permission to use, copy, modify, and distribute this software and
# its documentation for any purpose and without fee is hereby granted,
# provided that the above copyright, this permission notice and text
@@ -450,17 +452,18 @@ esac
;;
closed) echo "# The IOCCC is closed"
echo
echo "The IOCCC is **NOT** accepting new submissions at this time. See the" \
echo "The IOCCC is **NOT** accepting [new submissions](faq.html#submit) at this time. See the" \
"[IOCCC winning entries page](years.html) for the entries that have won the IOCCC."
echo
echo "Watch both [the IOCCC status page](status.html) and the" \
echo "Watch both [this IOCCC status page](status.html) and the" \
"[@IOCCC mastodon feed](https://fosstodon.org/@ioccc) for information about future IOCCC openings."
;;
*) echo "# The IOCCC status is unknown"
echo
echo "The IOCCC status is an unexpected status value: $CONTEST_STATUS"
echo
echo "This is a **BUG**, not a feature. Feel free to report it!"
echo "This is a **BUG**, not a feature. Feel free to report it!" 1>&2
echo "See the [GitHub issues page](https://github.com/ioccc-src/temp-test-ioccc/issues/new/choose}." 1>&2
;;
esac
echo
news.html
+53 -22
View File
@@ -383,20 +383,51 @@
<!-- BEFORE: 1st line of markdown file: news.md -->
<h1 id="for-more-news-try-mastodon">For more news, try mastodon</h1>
<h3 id="please-follow-the-ioccc-on-mastodon">Please follow** the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h3>
<h3 id="please-follow-the-ioccc-on-mastodon">Please follow the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h3>
<p>We use Mastodon to make minor announcements, in addition to announcing
major events such as the opening of a new IOCCC, or who won.</p>
<p>See “<a href="faq.html#try_mastodon">FAQ 6.12: What is Mastodon and why does IOCCC use it?</a>” for more
information on Mastodon.</p>
<h2 id="section">2024-05-30</h2>
<h1 id="news">News</h1>
<h2 id="section">2024-06-08</h2>
<p>We continue to make good progress on the
<a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
<p>One of the <a href="thanks-for-help.html">largest html
files</a> has
been checked for broken links which leaves two longer files to go. These two
files are the <a href="bugs.html">bugs.html</a>
file and the <a href="faq.html">FAQ</a>.</p>
<p>However, where it was thought that those two files would be looked at before the
other html files, it has been decided that they will be done after the other
files as it is very possible that some things in these two files will have to be
changed or added as the other files are reviewed for broken links.</p>
<p>As of today, 08 June 2024, the top level html files are being looked at, with at
least three done already (<a href="judges.html">judges.html</a>, <a href="news.html">news.html</a> and
<a href="status.html">status.html</a>). This should not take more than a few days if things
go as planned, as these files are small and should be relatively quick and easy
to check for broken links. Of course, some of these, like the
<a href="news.html">news.html</a> and possibly <a href="status.html">status.html</a> will likely have to be
checked again but as for <a href="news.html">news.html</a> the dates up to and including <em>08
June 2024</em> have been checked for invalid links so that only new news updates
will have to be checked.</p>
<p>Once those are done the html files of all the entries will be looked at. As
those are being reviewed it the <a href="bugs.html">bugs.html</a> might very well be
updated and the <a href="faq.html">FAQ</a> might be as well. This is why, as noted above,
we have decided to review these files last, in order to save time and effort in
not having to look at them more than once on a whole, other than possible
entries that have to be added at the end, like the example below.</p>
<p>Once the <em>submit server</em> server is ready another FAQ will be added and that
entry can be looked at alone.</p>
<h2 id="section-1">2024-05-30</h2>
<p>A number of issues from minor fixes have been applied to the
<a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
<p>437 commits have been applied since 2024-04-20, bringing the total
number to 5260 commits to date. The
<a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a>
repo is now 5159 commits ahead of the [IOCCC
winner[(https://github.com/ioccc-src/winner) repo.</p>
repo is now 5159 commits ahead of the <a href="https://github.com/ioccc-src/winner">IOCCC
winner</a> repo.</p>
<p>Multiple <strong>((top priority))</strong> issues have been resolved or completed.
Only one <strong>((top priority))</strong> issue, <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/2006">issue
2006</a>
@@ -409,7 +440,7 @@ there are two more before we can look at the other files.</p>
<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/2239">issue 2239</a>
TODO list has 10 out of 51 sub-tasks completed. That might not
seem like much progress, but keep in mind that some of those 10
tasks look many months and thousands of commits to complete.
tasks took many months and thousands of commits to complete.
Moreover, most of the remaining 41 TODO items are short “checkbox”
tasks. The final 31 TODO items are planned to be completed in about
a single day.</p>
@@ -423,7 +454,7 @@ ask for beta testing of the new <strong>IOCCC registration process</strong> and
This will speed up the start date of IOCCC28.</p>
<p>It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the
IOCCC.</p>
<h2 id="section-1">2024-04-30</h2>
<h2 id="section-2">2024-04-30</h2>
<p>The website now is viewing by mobile devices such as cell phones
and tablets. Devices with a screen resolution 1024 pixels and
narrower are given a <em>hamburger-style</em> menu icon in place of
@@ -445,7 +476,7 @@ files that are static (not generated <code>bin</code> tools) report </strong>no
warnings, nor info** messages, changes involving fixing invalid
links to local files have been corrected, and changes involving the
<em>topbar</em> are now HTML 5 conforming.</p>
<h2 id="section-2">2024-04-20</h2>
<h2 id="section-3">2024-04-20</h2>
<p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
website has undergone editorial review. Nearly all <a href="years.html">IOCCC winning entries</a>
compile on modern systems and many have <code>try.sh</code> scripts to help you run them.
@@ -463,10 +494,10 @@ glaring “<em>dancing bears</em>” and other frivolous web features.</p>
where the contents of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC website</a>.</p>
<p>Stay tuned!</p>
<h2 id="section-3">2024-02-29</h2>
<h2 id="section-4">2024-02-29</h2>
<p>We continue to make good progress on website. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 4600 changes to date!</p>
<p>All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the <a href="bin/index.html">bin</a> directory.</p>
<h2 id="section-4">2023-05-22</h2>
<h2 id="section-5">2023-05-22</h2>
<p>We have been busy preparing for an important / significant update to this website. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 2645 changes to date.</p>
<p>While you are free to look at the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a>,
please <strong>do not link to it</strong> as this repo and related website will disappear once the main
@@ -522,7 +553,7 @@ that needs urgent fixing.
The <strong>IOCCCMOCK</strong> will us to beta-test the new IOCCC process without putting the hard work of those
who submit real IOCCC entries at risk.</p>
<p>Stay tuned!</p>
<h2 id="section-5">2023-01-30</h2>
<h2 id="section-6">2023-01-30</h2>
<p>We added to the
<a href="status.json">status.json</a> page,
a <em>“status_date”</em> JSON member whose value is the date
@@ -534,11 +565,11 @@ a <em>“latest_news”</em> JSON member whose value is the date
of the most recent news item.</p>
<pre><code> &quot;status_date&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;,
&quot;latest_news&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;</code></pre>
<h2 id="section-6">2022-12-18</h2>
<p>As per the suggestion of <a href="https://fosstodon.org/@Virtaava@home.social">Toni Mikkola</a>
(_<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social_">@home.social_</span>) we now maintain a
<a href="status.json">status.json</a> page on this website.</p>
<p>In addition to the IOCCC-style <em>easter egg</em>, you may count on
<h2 id="section-7">2022-12-18</h2>
<p>As per the suggestion of <a href="https://fosstodon.org/@Virtaava@home.social">Toni Mikkola
(<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social">@home.social</span>)</a>
we now maintain a <a href="status.json">status.json</a> page on this website.</p>
<p>In addition to the IOCCC-style <em>Easter egg</em>, you may count on
the JSON status page having a JSON member with name of <strong>“contest”</strong>
that will have a value of either <strong>“closed”</strong> or <strong>“open”</strong>.
When a future <strong>IOCCC</strong> is announced or the IOCCC is currently open,
@@ -552,8 +583,8 @@ The details of such additional JSON members are <em>TBD</em>.</p>
Instead you will have to rely on the additional JSON information
and/or read the <a href="#news">IOCCC news</a>,
and/or follow us on Mastodon via <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
<h2 id="section-7">2022-11-29</h2>
<p>We are plan to abandon our
<h2 id="section-8">2022-11-29</h2>
<p>We are planning to abandon our
<a href="https://twitter.com/ioccc">IOCCC Twitter feed</a>
in favor of our new <a href="https://fosstodon.org/@ioccc">IOCCC Mastodon</a> feed.</p>
<p>Our Mastodon username is: <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
@@ -577,7 +608,7 @@ Proving a Mastodon username will be entirely <strong>optional</strong>.</p>
<p>If you do not yet have a Mastodon account, you may obtain a <strong>free mastodon account via</strong>:
<a href="https://joinmastodon.org">joinmastodon.org</a>.</p>
<p>If you do have / obtain a Mastodon account, <strong>please do us a favor and follow the IOCCC at</strong>:</p>
<pre><code> **@ioccc@fosstodon.org**</code></pre>
<pre><code> @ioccc@fosstodon.org</code></pre>
<p>The IOCCC wishes to thank the good folk running the
<a href="https://hub.fosstodon.org/about/">fosstodon.org</a>
Mastodon hub.
@@ -587,7 +618,7 @@ is made possible by volunteers,
and those who voluntarily
<a href="https://hub.fosstodon.org/support/">support</a> the cost of their server.</p>
<p>Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!</p>
<h2 id="section-8">2022-11-19</h2>
<h2 id="section-9">2022-11-19</h2>
<p>Source code has been released for version <strong>0.8.1 2022-11-19</strong> of the
<a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>,
a GitHub repo that includes the official iocccsize tool,
@@ -599,13 +630,13 @@ to upload the above mentioned compressed tarball: when the contest is open of co
judges will go through the motions (without judging the content) of an IOCCC:
testing the above mentioned tools and testing the submit server.</p>
<p>We are working on complete rebuild of this website as well.</p>
<h2 id="section-9">2022-01-15</h2>
<h2 id="section-10">2022-01-15</h2>
<p>Source code has been released for version <strong>0.24 2022-01-15</strong> of the
<a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</a>,
a tool that is based on, and is containing, the official iocccsize tool,
will form a compressed tarball that a registered IOCCC contestant
will upload to the submit server (when the contest is open of course).</p>
<h2 id="section-10">2021-12-27</h2>
<h2 id="section-11">2021-12-27</h2>
<p><a href="judges.html">The Judges</a>
are continuing to work on re-tooling how we run the IOCCC.
We are writing tools under various repositories our
@@ -614,7 +645,7 @@ We are writing tools under various repositories our
Sorry for the delay, but we think you will appreciate the re-tooling
when it is completed.
Stay tuned!</p>
<h2 id="section-11">2021-10-21</h2>
<h2 id="section-12">2021-10-21</h2>
<p><a href="judges.html">The Judges</a>
are re-tooling how we run the IOCCC.
Our goal is to build a smoother, more rapid process centered around
news.md
+50 -9
View File
@@ -1,6 +1,6 @@
# For more news, try mastodon
### Please follow** the [IOCCC on Mastodon](https://fosstodon.org/@ioccc)
### Please follow the [IOCCC on Mastodon](https://fosstodon.org/@ioccc)
We use Mastodon to make minor announcements, in addition to announcing
major events such as the opening of a new IOCCC, or who won.
@@ -8,6 +8,47 @@ major events such as the opening of a new IOCCC, or who won.
See "[FAQ 6.12: What is Mastodon and why does IOCCC use it?](faq.html#try_mastodon)" for more
information on Mastodon.
<div id="news">
# News
</div>
## 2024-06-08
We continue to make good progress on the
[temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/)
via the [temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc) repo.
One of the [largest html
files](thanks-for-help.html) has
been checked for broken links which leaves two longer files to go. These two
files are the [bugs.html](bugs.html)
file and the [FAQ](faq.html).
However, where it was thought that those two files would be looked at before the
other html files, it has been decided that they will be done after the other
files as it is very possible that some things in these two files will have to be
changed or added as the other files are reviewed for broken links.
As of today, 08 June 2024, the top level html files are being looked at, with at
least three done already ([judges.html](judges.html), [news.html](news.html) and
[status.html](status.html)). This should not take more than a few days if things
go as planned, as these files are small and should be relatively quick and easy
to check for broken links. Of course, some of these, like the
[news.html](news.html) and possibly [status.html](status.html) will likely have to be
checked again but as for [news.html](news.html) the dates up to and including _08
June 2024_ have been checked for invalid links so that only new news updates
will have to be checked.
Once those are done the html files of all the entries will be looked at. As
those are being reviewed it the [bugs.html](bugs.html) might very well be
updated and the [FAQ](faq.html) might be as well. This is why, as noted above,
we have decided to review these files last, in order to save time and effort in
not having to look at them more than once on a whole, other than possible
entries that have to be added at the end, like the example below.
Once the _submit server_ server is ready another FAQ will be added and that
entry can be looked at alone.
## 2024-05-30
@@ -19,7 +60,7 @@ via the [temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc) repo.
number to 5260 commits to date. The
[temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc)
repo is now 5159 commits ahead of the [IOCCC
winner[(https://github.com/ioccc-src/winner) repo.
winner](https://github.com/ioccc-src/winner) repo.
Multiple **((top priority))** issues have been resolved or completed.
Only one **((top priority))** issue, [issue
@@ -34,7 +75,7 @@ there are two more before we can look at the other files.
The [issue 2239](https://github.com/ioccc-src/temp-test-ioccc/issues/2239)
TODO list has 10 out of 51 sub-tasks completed. That might not
seem like much progress, but keep in mind that some of those 10
tasks look many months and thousands of commits to complete.
tasks took many months and thousands of commits to complete.
Moreover, most of the remaining 41 TODO items are short "checkbox"
tasks. The final 31 TODO items are planned to be completed in about
a single day.
@@ -205,11 +246,11 @@ of the most recent news item.
## 2022-12-18
As per the suggestion of [Toni Mikkola](https://fosstodon.org/@Virtaava@home.social)
(_@Virtaava@home.social_) we now maintain a
[status.json](status.json) page on this website.
As per the suggestion of [Toni Mikkola
&#x28;@Virtaava@home.social&#x29;](https://fosstodon.org/@Virtaava@home.social)
we now maintain a [status.json](status.json) page on this website.
In addition to the IOCCC-style _easter egg_, you may count on
In addition to the IOCCC-style _Easter egg_, you may count on
the JSON status page having a JSON member with name of **"contest"**
that will have a value of either **"closed"** or **"open"**.
When a future **IOCCC** is announced or the IOCCC is currently open,
@@ -229,7 +270,7 @@ and/or follow us on Mastodon via **@ioccc@fosstodon.org**.
## 2022-11-29
We are plan to abandon our
We are planning to abandon our
[IOCCC Twitter feed](https://twitter.com/ioccc)
in favor of our new [IOCCC Mastodon](https://fosstodon.org/@ioccc) feed.
@@ -263,7 +304,7 @@ If you do not yet have a Mastodon account, you may obtain a **free mastodon acco
If you do have / obtain a Mastodon account, **please do us a favor and follow the IOCCC at**:
```
**@ioccc@fosstodon.org**
@ioccc@fosstodon.org
```
The IOCCC wishes to thank the good folk running the
status.html
+42 -35
View File
@@ -384,14 +384,14 @@
<!-- START: this line starts content generated by: bin/status2html.sh -->
<h1 id="the-ioccc-is-closed">The IOCCC is closed</h1>
<p>The IOCCC is <strong>NOT</strong> accepting new submissions at this time. See the <a href="years.html">IOCCC winning entries page</a> for the entries that have won the IOCCC.</p>
<p>Watch both <a href="status.html">the IOCCC status page</a> and the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span> mastodon feed</a> for information about future IOCCC openings.</p>
<p>The IOCCC is <strong>NOT</strong> accepting <a href="faq.html#submit">new submissions</a> at this time. See the <a href="years.html">IOCCC winning entries page</a> for the entries that have won the IOCCC.</p>
<p>Watch both <a href="status.html">this IOCCC status page</a> and the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span> mastodon feed</a> for information about future IOCCC openings.</p>
<h1 id="status.json">status.json</h1>
<pre><code> {
&quot;no_comment&quot; : &quot;mandatory comment: because comments were removed from the original JSON spec&quot;,
&quot;IOCCC_status_version&quot; : &quot;1.0 2024-03-09&quot;,
&quot;contest_status&quot; : &quot;closed&quot;,
&quot;news_update&quot; : &quot;2024-05-31T22:33:29+00:00&quot;,
&quot;news_update&quot; : &quot;2024-06-08T16:23:00+00:00&quot;,
&quot;status_update&quot; : &quot;2024-04-30T22:51:32+00:00&quot;
}</code></pre>
@@ -402,73 +402,80 @@
<!-- BEFORE: 1st line of markdown file: status.md -->
<h1 id="format">format</h1>
<p>The following JSON members are required to be present <a href="status.json">status.json</a>.</p>
<p>The following <strong>JSON</strong> members are required to be present <a href="status.json">status.json</a>.</p>
<h2 id="no_comment">no_comment</h2>
<p>This is a <strong>mandatory</strong> comment for which we offer no comment other
than this comment. :-)</p>
<p>The JSON member value must be the following JSON quoted string:</p>
<p>The <strong>JSON</strong> member value must be the following <strong>JSON</strong> quoted string:</p>
<pre><code> &quot;mandatory comment: because comments were removed from the original JSON spec&quot;</code></pre>
<div id="IOCCC_status_version">
<h2 id="ioccc_status_version">IOCCC_status_version</h2>
</div>
<p>This is the version of format of the <a href="status.json">status.json</a> file.</p>
<p>The JSON member value of is a JSON quoted string the form “<em>version YYYY-MM-DD</em>”.</p>
<p>The <strong>JSON</strong> member value of is a <strong>JSON</strong> quoted string the form “<em>version YYYY-MM-DD</em>”.</p>
<p>This document describes version “<strong>1.0 2024-03-09</strong>”.</p>
<h2 id="contest_status">contest_status</h2>
<p>The current status of the IOCCC.</p>
<p>The following JSON member value string may be one of the following JSON quoted strings:</p>
<p>The current status of the <a href="index.html">IOCCC</a>.</p>
<p>The following <strong>JSON</strong> member value string may be one of the following <strong>JSON</strong> quoted strings:</p>
<h4 id="pending">“<strong>pending</strong>”</h4>
<p>The IOCCC is not yet open, however there is a tentative scheduled
date and time by which the IOCCC will open for submissions.</p>
<p>A preliminary IOCCC rules, guidelines, and tools have been posted.
<p>The <a href="index.html">IOCCC</a> is not yet <a href="#open">open</a>, however there is a tentative scheduled
date and time by which the <a href="index.html">IOCCC</a> will open for submissions.</p>
<p>A preliminary <a href="index.html">IOCCC</a> rules, guidelines, and tools have been posted.
Comments and suggestions on these preliminary items are welcome.
See the <a href="news.html">IOCCC news</a> for details including the tentative
scheduled opening date.</p>
<h4 id="open">“<strong>open</strong>”</h4>
<p>The IOCCC is open for submissions.</p>
<p>The <a href="index.html">IOCCC</a> is <a href="#open">open</a> for <a href="faq.html#submit">submissions</a>.</p>
<p>See the <a href="news.html">IOCCC news</a> page for details on rules, guidelines, tools and deadlines.</p>
<p>Be sure to review the official IOCCC rules, guidelines, and tools
for any changes that may have been made while the IOCCC was “<strong>pending</strong>”.</p>
<p>Be sure to review the official <a href="index.html">IOCCC</a> rules, guidelines, and tools
for any changes that may have been made while the <a href="index.html">IOCCC</a> was “<strong>pending</strong>”.</p>
<h4 id="judging">“<strong>judging</strong>”</h4>
<p>The IOCCC is closed to new submissions. The <a href="judges.html">IOCCC judges</a>
are in the process of judging the submissions they received while
the IOCCC was open.</p>
<p>The <a href="index.html">IOCCC</a> is <a href="#closed">closed</a> to new submissions. The <a href="judges.html">IOCCC judges</a>
are in the process of judging the <a href="faq.html#faq2_0">submissions</a> they received while
the <a href="index.html">IOCCC</a> was open.</p>
<p>Watch the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span> mastodon feed</a> for updates.</p>
<p>Once the <a href="index.html">IOCCC</a> closes, the judges will:</p>
<p>Once the <a href="index.html">IOCCC</a> <a href="#closed">closes</a>, the judges will:</p>
<ul>
<li><p>Select the <a href="years.html">winning entries</a> announce them on the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span>
<li><p>Select the <a href="years.html">winning entries</a> and announce them on the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span>
mastodon feed</a>.</p></li>
<li><p>Notify the authors of entries that won the IOCCC via email using their previously
registered email address.</p></li>
<li><p>Announce who are authors of this year’s winning IOCCC entries via the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span> mastodon
<li><p>Notify the <a href="authors.html">authors</a> of entries that won the <a href="index.html">IOCCC</a>
via email using their registered email address.</p></li>
<li><p>Announce who the <a href="authors.html">authors</a> are of this year’s <a href="years.html">winning IOCCC
entries</a> via the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span> mastodon
feed</a>.</p></li>
<li><p>Upload the winning code to the <a href="https://github.com/ioccc-src/winner">Official IOCCC winner repo</a></p></li>
<li><p>Upload the winning code to the <a href="https://github.com/ioccc-src/winner">Official IOCCC winner
repo</a>.</p></li>
<li><p>Update the <a href="index.html">Official IOCCC website</a>, and in particular
display this year’s winning IOCCC entries at the top of the <a href="years.html">IOCCC
display this year’s <a href="years.html">winning IOCCC entries</a> at the top of the <a href="years.html">IOCCC
winning entries page</a>.</p></li>
<li><p>Update the <a href="news.html">IOCCC news</a> page.</p></li>
</ul>
<h4 id="closed">“<strong>closed</strong>”</h4>
<p>The IOCCC is closed and is <strong>NOT</strong> accepting new submissions.</p>
<p>See the <a href="years.html">IOCCC winning entries page</a> for the entries that have won the IOCCC.</p>
<p><strong>NOTE</strong>: From time to time, winning IOCCC entries may have their write-ups updated,
Makefiles improved and source code fixed. See <a href="news.html">IOCCC news</a> for details.</p>
<p>Watch both <a href="status.html">the IOCCC status page</a> and <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span>
mastodon feed</a> for information about future IOCCC openings.</p>
<p>The <a href="index.html">IOCCC</a> is closed and is <strong>NOT</strong> accepting <a href="faq.html#submit">new
submissions</a>.</p>
<p>See the <a href="years.html">IOCCC winning entries page</a> for the entries that have won
the <a href="index.html">IOCCC</a>.</p>
<p><strong>NOTE</strong>: From time to time, <a href="years.html">winning IOCCC entries</a> may have their write-ups updated,
<code>Makefiles</code> improved, source code fixed etc. See <a href="news.html">IOCCC news</a> for details.</p>
<p>Watch both <a href="status.html">this IOCCC status page</a> and the <a href="https://fosstodon.org/@ioccc"><span class="citation" data-cites="IOCCC">@IOCCC</span>
mastodon feed</a> for information about future
<a href="index.html">IOCCC</a> <a href="#open">openings</a>.</p>
<h2 id="news_update">news_update</h2>
<p>This shows the latest modification date for the <a href="news.html">IOCCC news</a> page.</p>
<p>The JSON member value is a JSON quoted string obtained from the date field
<p>The <strong>JSON</strong> member value is a <strong>JSON</strong> quoted string obtained from the date field
of the following <code>ls(1)</code> command:</p>
<pre><code> TZ=UTC ls -D &#39;%FT%T+00:00&#39; -ld news.html</code></pre>
<p><strong>NOTE</strong>: The date and time are given with respect to <strong>UTC</strong> timezone.</p>
<p><strong>Sorry</strong>: It is possible that for some reason, the <a href="news.html">IOCCC news</a> page
<p><strong>NOTE</strong>: It is possible that for some reason, the <a href="news.html">IOCCC news</a> 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.</p>
<h2 id="status_update">status_update</h2>
<p>This shows the latest modification date <a href="status.json">status.json</a> file.</p>
<p>The JSON member value is a JSON quoted string obtained from the date field
<p>This shows the latest modification date of <a href="status.json">status.json</a> file.</p>
<p>The <strong>JSON</strong> member value is a <strong>JSON</strong> quoted string obtained from the date field
of the following <code>ls(1)</code> command:</p>
<pre><code> TZ=UTC ls -D &#39;%FT%T+00:00&#39; -ld status.json</code></pre>
<p><strong>NOTE</strong>: The date and time are given with respect to <strong>UTC</strong> timezone.</p>
<p><strong>Sorry</strong>: It is possible that for some reason, the <a href="status.json">status.json</a> file
<p><strong>NOTE</strong>: It is possible that for some reason, the <a href="status.json">status.json</a> 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.</p>
<hr style="width:10%;text-align:left;margin-left:0">
status.json
+1 -1
View File
@@ -2,6 +2,6 @@
"no_comment" : "mandatory comment: because comments were removed from the original JSON spec",
"IOCCC_status_version" : "1.0 2024-03-09",
"contest_status" : "closed",
"news_update" : "2024-05-31T22:33:29+00:00",
"news_update" : "2024-06-08T16:23:00+00:00",
"status_update" : "2024-04-30T22:51:32+00:00"
}
status.md
+53 -33
View File
@@ -1,80 +1,93 @@
# format
The following JSON members are required to be present [status.json](status.json).
The following **JSON** members are required to be present [status.json](status.json).
<div id="no_comment">
## no_comment
</div>
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:
The **JSON** member value must be the following **JSON** quoted string:
``` <!---json-->
"mandatory comment: because comments were removed from the original JSON spec"
```
<div id="IOCCC_status_version">
## IOCCC_status_version
</div>
This is the version of format of the [status.json](status.json) file.
The JSON member value of is a JSON quoted string the form "_version YYYY-MM-DD_".
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**".
<div id="contest_status">
## contest_status
</div>
The current status of the IOCCC.
The current status of the [IOCCC](index.html).
The following JSON member value string may be one of the following JSON quoted strings:
The following **JSON** member value string may be one of the following **JSON** quoted strings:
<div id="pending">
#### "**pending**"
</div>
The IOCCC is not yet open, however there is a tentative scheduled
date and time by which the IOCCC will open for submissions.
The [IOCCC](index.html) is not yet [open](#open), however there is a tentative scheduled
date and time by which the [IOCCC](index.html) will open for submissions.
A preliminary IOCCC rules, guidelines, and tools have been posted.
A preliminary [IOCCC](index.html) rules, guidelines, and tools have been posted.
Comments and suggestions on these preliminary items are welcome.
See the [IOCCC news](news.html) for details including the tentative
scheduled opening date.
<div id="open">
#### "**open**"
</div>
The IOCCC is open for submissions.
The [IOCCC](index.html) is [open](#open) for [submissions](faq.html#submit).
See the [IOCCC news](news.html) 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**".
Be sure to review the official [IOCCC](index.html) rules, guidelines, and tools
for any changes that may have been made while the [IOCCC](index.html) was "**pending**".
<div id="judging">
#### "**judging**"
</div>
The IOCCC is closed to new submissions. The [IOCCC judges](judges.html)
are in the process of judging the submissions they received while
the IOCCC was open.
The [IOCCC](index.html) is [closed](#closed) to new submissions. The [IOCCC judges](judges.html)
are in the process of judging the [submissions](faq.html#faq2_0) they received while
the [IOCCC](index.html) was open.
Watch the [@IOCCC mastodon feed](https://fosstodon.org/@ioccc) for updates.
Once the [IOCCC](index.html) closes, the judges will:
Once the [IOCCC](index.html) [closes](#closed), the judges will:
* Select the [winning entries](years.html) announce them on the [@IOCCC
* Select the [winning entries](years.html) and announce them on the [@IOCCC
mastodon feed](https://fosstodon.org/@ioccc).
* Notify the authors of entries that won the IOCCC via email using their previously
registered email address.
* Notify the [authors](authors.html) of entries that won the [IOCCC](index.html)
via email using their registered email address.
* Announce who are authors of this year's winning IOCCC entries via the [@IOCCC mastodon
* Announce who the [authors](authors.html) are of this year's [winning IOCCC
entries](years.html) via the [@IOCCC mastodon
feed](https://fosstodon.org/@ioccc).
* Upload the winning code to the [Official IOCCC winner repo](https://github.com/ioccc-src/winner)
* Upload the winning code to the [Official IOCCC winner
repo](https://github.com/ioccc-src/winner).
* Update the [Official IOCCC website](index.html), and in particular
display this year's winning IOCCC entries at the top of the [IOCCC
display this year's [winning IOCCC entries](years.html) at the top of the [IOCCC
winning entries page](years.html).
* Update the [IOCCC news](news.html) page.
@@ -82,22 +95,27 @@ winning entries page](years.html).
#### "**closed**"
The IOCCC is closed and is **NOT** accepting new submissions.
The [IOCCC](index.html) is closed and is **NOT** accepting [new
submissions](faq.html#submit).
See the [IOCCC winning entries page](years.html) for the entries that have won the IOCCC.
See the [IOCCC winning entries page](years.html) for the entries that have won
the [IOCCC](index.html).
**NOTE**: From time to time, winning IOCCC entries may have their write-ups updated,
Makefiles improved and source code fixed. See [IOCCC news](news.html) for details.
**NOTE**: From time to time, [winning IOCCC entries](years.html) may have their write-ups updated,
`Makefiles` improved, source code fixed etc. See [IOCCC news](news.html) for details.
Watch both [the IOCCC status page](status.html) and [@IOCCC
mastodon feed](https://fosstodon.org/@ioccc) for information about future IOCCC openings.
Watch both [this IOCCC status page](status.html) and the [@IOCCC
mastodon feed](https://fosstodon.org/@ioccc) for information about future
[IOCCC](index.html) [openings](#open).
<div id="news_update">
## news_update
</div>
This shows the latest modification date for the [IOCCC news](news.html) page.
The JSON member value is a JSON quoted string obtained from the date field
The **JSON** member value is a **JSON** quoted string obtained from the date field
of the following `ls(1)` command:
``` <!---ls-->
@@ -106,16 +124,18 @@ of the following `ls(1)` command:
**NOTE**: The date and time are given with respect to **UTC** timezone.
**Sorry**: It is possible that for some reason, the [IOCCC news](news.html) page
**NOTE**: It is possible that for some reason, the [IOCCC news](news.html) 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.
<div id="status_update">
## status_update
</div>
This shows the latest modification date [status.json](status.json) file.
This shows the latest modification date of [status.json](status.json) file.
The JSON member value is a JSON quoted string obtained from the date field
The **JSON** member value is a **JSON** quoted string obtained from the date field
of the following `ls(1)` command:
``` <!---ls-->
@@ -124,7 +144,7 @@ of the following `ls(1)` command:
**NOTE**: The date and time are given with respect to **UTC** timezone.
**Sorry**: It is possible that for some reason, the [status.json](status.json) file
**NOTE**: It is possible that for some reason, the [status.json](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.