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

update FAQ and news as per new mkiocccentry release

Browse Source 
Added news based on the recent
[release 2.4.3 2025-03-11](https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.3)
of the [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry).

Updated the FAQ with additional information about the above mentioned release.

Fixed use of double blank lines in `faq.md` so that they:

- precede all markdown headings
- precede and follow all "Jump to top" lines

Added missing "Jump to top" lines.

Fixed Section 2 internal link.

Performed `make www gen_status gen_sitemap timestamp` to update the website.
This commit is contained in:
Landon Curt Noll committed 2025-03-12 21:04:37 -07:00
1 parent 6e844aa543
commit 06f26f2220
7 files changed
+234 -59
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

faq.html
+5 -3
View File
@@ -458,7 +458,7 @@
<li><strong>Q 1.9</strong>: <a class="normal" href="#uuid">How can I avoid re-entering my UUID to mkiocccentry?</a></li>
<li><strong>Q 1.10</strong>: <a class="normal" href="#submission_dir">How can I avoid having to move or delete my submission directory for the same workdir?</a></li>
</ul>
<h2 id="ioccc-judging-process">2. <a href="#judging_proceess">IOCCC Judging process</a></h2>
<h2 id="ioccc-judging-process">2. <a href="#judging_process">IOCCC Judging process</a></h2>
<ul>
<li><strong>Q 2.0</strong>: <a class="normal" href="#questions">What is the best way to ask a question about the IOCCC rules, guideline and tools?</a></li>
<li><strong>Q 2.1</strong>: <a class="normal" href="#feedback">How can I comment or make a suggestion on IOCCC rules, guidelines and tools?</a></li>
@@ -586,6 +586,7 @@
<div id="enter_questions">
<h2 id="section-0-entering-the-ioccc-the-bare-minimum-you-need-to-know">Section 0: Entering the IOCCC: the bare minimum you need to know</h2>
</div>
<p>Jump to: <a href="#">top</a></p>
<div id="enter">
<div id="step_0">
<div id="step_1">
@@ -955,7 +956,7 @@ and <a href="next/rules.html#rule17">Rule 17</a> itself.</p>
<p>Do remember that if your submission requires different filenames, then you
<strong>MUST</strong> make a <strong>COPY</strong> of them in your <code>Makefile</code>. See also <a href="next/rules.html#rule11">Rule
11</a>.</p>
Jump to: <a href="#">top</a>
<p>Jump to: <a href="#">top</a></p>
<hr style="width:50%;text-align:left;margin-left:0">
<hr style="width:50%;text-align:left;margin-left:0">
<div id="submitting_help">
@@ -1896,7 +1897,7 @@ entries that do not win on their web page for everyone to see.</p>
<div id="mkiocccentry_details">
<h2 id="section-3-the-mkiocccentry-toolkit-finer-details">Section 3: The mkiocccentry toolkit: finer details</h2>
</div>
Jump to: <a href="#">top</a>
<p>Jump to: <a href="#">top</a></p>
<div id="mkiocccentry_process">
<h3 id="q-3.0-what-is-the-mkiocccentry1-process-and-what-sort-of-checks-does-it-perform">Q 3.0: What is the <code>mkiocccentry(1)</code> process and what sort of checks does it perform?</h3>
</div>
@@ -6503,6 +6504,7 @@ announced in the early years of the IOCCC.</p>
<h3 id="q-11.6-i-do-not-understand-the-ioccc-can-you-explain-it-to-me">Q 11.6: I do not understand the IOCCC, can you explain it to me?</h3>
</div>
<p>Please see the <a href="about.html">About the IOCCC page</a> for more details.</p>
<p>Jump to: <a href="#">top</a></p>
<!--
Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.
faq.md
+167 -28
View File
File diff suppressed because it is too large. Load diff
news.html
+35 -21
View File
@@ -434,7 +434,21 @@ for more information on Mastodon.</p>
<h3 id="ioccc-discord-community">IOCCC Discord Community</h3>
<p>We invite you to join the <strong>IOCCC Discord Community</strong> via this link: <a href="https://discord.gg/Wa42Qujwnw">https://discord.gg/Wa42Qujwnw</a></p>
<h1 id="news">News</h1>
<h2 id="section">2025-03-05</h2>
<h2 id="section">2025-03-12</h2>
<p>We released <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry toolkit</a> <strong>version 2.4.3 2025-03-11</strong>.</p>
<p>While you are <strong>NOT</strong> required to use this release in order to submit to <strong>IOCCC28</strong>,
we do <strong>RECOMMEND</strong> that you <strong>install and use</strong> it, because among other things, it provides:</p>
<ul>
<li><code>mkiocccentry(1)</code> and <code>txzchk(1)</code> now search for other toolkit tools using <code>$PATH</code></li>
<li><code>mkiocccentry(1)</code> and <code>chkentry(1)</code> are now less strict with most <code>iocccsize(1)</code> warnings</li>
<li><code>mkiocccentry -x</code> will force the overwriting of the submission directory it forms under <code>workdir</code></li>
<li><code>mkiocccentry -U uuid</code> and <code>mkiocccentry -u uuid_file</code> let you set your username</li>
</ul>
<p>See the <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.3">version 2.4.3 release notes</a>
for more details.</p>
<p><strong>Clarification</strong>: <strong>NUL bytes</strong> are <strong>ALLOWED</strong> in your submission <code>prog.c</code> and related C code.</p>
<p>Please mention in your <code>remarks.md</code> file if your C source contains <strong>NUL bytes</strong>.</p>
<h2 id="section-1">2025-03-05</h2>
<p>The <a href="faq.html#ioccc_start">40th anniversary of the IOCCC</a>, <strong>IOCCC28</strong>, will be <strong>open</strong> for
submissions from <strong>2025-03-05 23:19:17.131107 UTC</strong> to <strong>2025-06-05 04:03:02.010099 UTC</strong>.</p>
<p>Version <strong>28.30 2025-03-03</strong> of the <a href="next/rules.html">IOCCC28 rules</a>,
@@ -454,13 +468,13 @@ and initial password by email. If you cannot find that email, contact the
<a href="contact.html#if-you-really-need-to-send-email-the-ioccc-judges">IOCCC Judges by email</a>
for help. We have given early registrants extra time (until <strong>2025 Mar 12 UTC</strong>), to login
and change their initial password.</p>
<h2 id="section-1">2025-02-28</h2>
<h2 id="section-2">2025-02-28</h2>
<p>We have reached our <strong>code freeze</strong> milestone for the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a> and released a new version of the <a href="faq.html#mkiocccentry">mkiocccentry toolkit</a>!</p>
<p>Final testing is going well. We remain on track to open the <strong>IOCCC28</strong> on <strong>2025-03-05 23:19:17.131107 UTC</strong>.</p>
<p>In a few days, those <a href="https://www.ioccc.org/next/register.html">registered for IOCCC28</a> will receive email with their username and initial password to <a href="https://submit.ioccc.org">submit their code</a>.</p>
<p>We encourage those who wish to enter the <strong>IOCCC28</strong> to <a href="https://www.ioccc.org/next/register.html">registered for IOCCC28</a> today.</p>
<p>Consider joining the IOCCC discord community via this link: <a href="https://discord.gg/Wa42Qujwnw">https://discord.gg/Wa42Qujwnw</a></p>
<h2 id="section-2">2025-02-12</h2>
<h2 id="section-3">2025-02-12</h2>
<p>We have discovered an issue that needs to be resolved, followed by more testing
after the code freeze. We also want to improve the <a href="next/guidelines.html">IOCCC28 guidelines</a>,
and to simplify the write-up of the <a href="next/rules.html">IOCCC28 rules</a>.</p>
@@ -468,7 +482,7 @@ and to simplify the write-up of the <a href="next/rules.html">IOCCC28 rules</a>.
on <strong>2024-12-29 23:58:13.213455 UTC</strong>, is now scheduled to be <strong>open</strong>
from <strong>2025-03-05 23:19:17.131107 UTC</strong> to <strong>2025-06-05 04:03:02.010099 UTC</strong>.
We apologize for this delay.</p>
<h2 id="section-3">2025-01-28</h2>
<h2 id="section-4">2025-01-28</h2>
<p><strong>IMPORTANT DISCORD UPDATE</strong>: Due to a Discord bug/mis-feature, those
who joined the <a href="https://discord.gg/Wa42Qujwnw">IOCCC Discord server</a>
recently lost their access soon afterwards and have to re-join.
@@ -478,7 +492,7 @@ Fans of the IOCCC, hopeful <strong>IOCCC28</strong> contestants, and past winner
are all encouraged to stop by and say hello.</p>
<p>To join, click this link:
<a href="https://discord.gg/Wa42Qujwnw">https://discord.gg/Wa42Qujwnw</a>.</p>
<h2 id="section-4">2025-01-25</h2>
<h2 id="section-5">2025-01-25</h2>
<p>The IOCCC now has a <a href="https://discord.gg/Wa42Qujwnw">Discord server</a>!
Click the link to join the <a href="https://discord.gg/Wa42Qujwnw">IOCCC Discord server</a>.
Fans of the IOCCC, hopeful <strong>IOCCC28</strong> contestants, and past winners of the IOCCC
@@ -494,14 +508,14 @@ on <strong>2024-12-29 23:58:13.213455 UTC</strong>, is now scheduled to be <stro
from <strong>2025-02-19 23:19:17.130705 UTC</strong> to <strong>2025-05-19 23:29:31.374143
UTC</strong>. We will update the <a href="next/rules.html">IOCCC rules</a> and
<a href="next/guidelines.html">IOCCC guidelines</a> accordingly, before the contest opens.</p>
<h2 id="section-5">2024-12-31</h2>
<h2 id="section-6">2024-12-31</h2>
<p>We have just released <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3">version 2.3 of the mkiocccentry repo</a>.
This repo 2.3 release includes important improvements (over repo release 2.1) to the <code>mkiocccentry(1)</code> tool
as well as a critical fix for installing on BSD based systems.</p>
<p>Please download <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3">version 2.3 of the mkiocccentry repo</a>,
and compile the <a href="faq.html#mkiocccentry">mkiocccentry tool set</a>. You may also wish to install this code.
See also the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/FAQ.md">mkiocccentry FAQ</a> for more information.</p>
<h2 id="section-6">2024-12-30</h2>
<h2 id="section-7">2024-12-30</h2>
<p>The IOCCC <a href="next/rules.html#rule13">Rule 13</a> no longer discourages the
use of UTF-8 in C source. Since the days of <code>-std=gnu17</code> compilers,
UTF-8 characters do not impose a compiler problem. The related guideline
@@ -512,7 +526,7 @@ modifications as means to tell the submitter that their submission was received.
<p>All of the import IOCCC dates within the <a href="next/rules.html">IOCCC rules</a>
have been moved into the “<a href="next/rules.html#dates">Important IOCCC dates</a>”
section.</p>
<h2 id="section-7">2024-12-28</h2>
<h2 id="section-8">2024-12-28</h2>
<h3 id="good-news-everyone--">Good News Everyone! :-)</h3>
<p>After a 4 year effort by a <a href="thanks-for-help.html">number of people</a>,
with over 6168+ commits, the <strong>Great Fork Merge</strong> has been completed
@@ -540,7 +554,7 @@ and <a href="status.json">status.json</a> has been updated to reflect this new s
<p>Proposed and tentative <a href="next/rules.html">IOCCC rules</a> and <a href="next/guidelines.html">IOCCC guidelines</a>
have been released.</p>
<p>See <a href="quick-start.html#enter_questions">FAQ Section 0</a> for more information on how to enter.</p>
<h2 id="section-8">2024-06-08</h2>
<h2 id="section-9">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>
@@ -570,7 +584,7 @@ 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-9">2024-05-30</h2>
<h2 id="section-10">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>
@@ -605,7 +619,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-10">2024-04-30</h2>
<h2 id="section-11">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
@@ -627,7 +641,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-11">2024-04-20</h2>
<h2 id="section-12">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.
@@ -645,10 +659,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-12">2024-02-29</h2>
<h2 id="section-13">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-13">2023-05-22</h2>
<h2 id="section-14">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
@@ -704,7 +718,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-14">2023-01-30</h2>
<h2 id="section-15">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
@@ -716,7 +730,7 @@ 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-15">2022-12-18</h2>
<h2 id="section-16">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&amp;rpar">@home.social&amp;rpar</span>;</a>
we now maintain a <a href="status.json">status.json</a> page on this website.</p>
@@ -734,7 +748,7 @@ 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-16">2022-11-29</h2>
<h2 id="section-17">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>
@@ -769,7 +783,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-17">2022-11-19</h2>
<h2 id="section-18">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,
@@ -781,13 +795,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-18">2022-01-15</h2>
<h2 id="section-19">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-19">2021-12-27</h2>
<h2 id="section-20">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
@@ -796,7 +810,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-20">2021-10-21</h2>
<h2 id="section-21">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
+20
View File
@@ -20,6 +20,26 @@ We invite you to join the **IOCCC Discord Community** via this link: [https://di
</div>
## 2025-03-12
We released [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry) **version 2.4.3 2025-03-11**.
While you are **NOT** required to use this release in order to submit to **IOCCC28**,
we do **RECOMMEND** that you **install and use** it, because among other things, it provides:
* `mkiocccentry(1)` and `txzchk(1)` now search for other toolkit tools using `$PATH`
* `mkiocccentry(1)` and `chkentry(1)` are now less strict with most `iocccsize(1)` warnings
* `mkiocccentry -x` will force the overwriting of the submission directory it forms under `workdir`
* `mkiocccentry -U uuid` and `mkiocccentry -u uuid_file` let you set your username
See the [version 2.4.3 release notes](https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.3)
for more details.
**Clarification**: **NUL bytes** are **ALLOWED** in your submission `prog.c` and related C code.
Please mention in your `remarks.md` file if your C source contains **NUL bytes**.
## 2025-03-05
The [40th anniversary of the IOCCC](faq.html#ioccc_start), **IOCCC28**, will be **open** for
sitemap.xml
+5 -5
View File
@@ -15414,11 +15414,11 @@
</url>
<url>
<loc>https://www.ioccc.org/faq.html</loc>
<lastmod>2025-03-05T17:49:07+00:00</lastmod>
<lastmod>2025-03-13T03:37:32+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/faq.md</loc>
<lastmod>2025-03-05T17:49:07+00:00</lastmod>
<lastmod>2025-03-13T03:37:26+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/inc/index.html</loc>
@@ -15458,11 +15458,11 @@
</url>
<url>
<loc>https://www.ioccc.org/news.html</loc>
<lastmod>2025-03-08T05:38:40+00:00</lastmod>
<lastmod>2025-03-13T03:00:48+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/news.md</loc>
<lastmod>2025-03-08T05:38:40+00:00</lastmod>
<lastmod>2025-03-13T03:00:38+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/README.html</loc>
@@ -15478,7 +15478,7 @@
</url>
<url>
<loc>https://www.ioccc.org/status.json</loc>
<lastmod>2025-03-08T05:41:00+00:00</lastmod>
<lastmod>2025-03-13T03:00:54+00:00</lastmod>
</url>
<url>
<loc>https://www.ioccc.org/thanks-for-help.html</loc>
status.html
+1 -1
View File
@@ -434,7 +434,7 @@
&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;open&quot;,
&quot;news_update&quot; : &quot;2025-03-08T05:38:40+00:00&quot;,
&quot;news_update&quot; : &quot;2025-03-13T03:00:38+00:00&quot;,
&quot;status_update&quot; : &quot;2025-03-05T18:15:23+00:00&quot;
}</code></pre>
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" : "open",
"news_update" : "2025-03-08T05:38:40+00:00",
"news_update" : "2025-03-13T03:00:38+00:00",
"status_update" : "2025-03-05T18:15:23+00:00"
}