ioccc/news.html

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<!-- START: two lines up starts content from: inc/top.default.html -->
<!-- -->
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- !!! DO NOT MODIFY THIS FILE - This file is generated by a tool !!! -->
<!-- !!! DO NOT MODIFY THIS FILE - This file is generated by a tool !!! -->
<!-- !!! DO NOT MODIFY THIS FILE - This file is generated by a tool !!! -->
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- -->
<!-- END: this line ends content from: inc/top.default.html -->
<!-- -->
<!-- The original markdown content was formed by the tool: bin/gen-top-html.sh -->
<!-- The HTML was converted from markdown by the tool: bin/md2html.sh -->
<!-- -->
<!-- START: this line starts content from: inc/head.default.html -->

<head>
<link rel="stylesheet" href="./ioccc.css">
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
<title>The International Obfuscated C Code Contest</title>
<meta name="description" content="News and notices of the IOCCC">
<meta name="keywords" content="IOCCC, IOCCC news, news">
</head>

<!-- END: this line ends content from: inc/head.default.html -->
<!-- START: this line starts content from: inc/body.default.html -->

<body>

<!-- END: this line ends content from: inc/body.default.html -->
<!-- START: this line starts content from: inc/header.default.html -->

<div class="header">
  <img src="./png/ioccc.png" alt="IOCCC image by Matt Zucker" width=300 height=110>
  <h1>The International Obfuscated C Code Contest</h1>
  <h2>IOCCC News</h2>
</div>

<!-- END: this line ends content from: inc/header.default.html -->
<!-- START: this line starts content from: inc/begin-row.default.html -->

<div class="row">

<!-- END: this line ends content from: inc/begin-row.default.html -->
<!-- START: this line starts content from: inc/begin-leftcolumn.default.html -->

  <div class="leftcolumn">

<!-- END: this line ends content from: inc/begin-leftcolumn.default.html -->
<!-- START: this line starts content from: inc/sidenav.default.html -->

    <div class="sidenav">
      <a href="#content">Jump to contents</a>
    </div>
    <hr>
    <div class="sidenav">
      <a href="./index.html">IOCCC Home</a>
      <a href="./years.html">Winning Entries</a>
      <a href="./authors.html">People who have won</a>
    </div>
    <hr>
    <div class="sidenav">
      <a href="./news.html">IOCCC News</a>
      <a href="./faq.html#submit">How to enter the IOCCC</a>
      <a href="./faq.html">FAQ</a>
    </div>
    <hr>
    <div class="sidenav">
      <a href="./bugs.html">Bugs &amp; (mis)features</a>
      <a href="./faq.html#fix_an_entry">Fixing IOCCC entries</a>
      <a href="./faq.html#fix_web_site">Fixing the web site</a>
      <a href="./faq.html#fix_author">Fixing author info</a>
      <a href="./thanks-for-help.html">Thanks for the help</a>
    </div>
    <hr>
    <div class="sidenav">
      <a href="./judges.html">The IOCCC Judges</a>
      <a href="./contact.html">Contacting the IOCCC</a>
    </div>
    <hr>
    <div class="sidenav">
      <a href="#top">Jump to top</a>
    </div>

<!-- END: this line ends content from: inc/sidenav.default.html -->
<!-- START: this line starts content from: inc/end-leftcolumn.default.html -->

  </div>

<!-- END: this line ends content from: inc/end-leftcolumn.default.html -->
<!-- START: this line starts content from: inc/begin-rightcolumn.default.html -->

  <div class="rightcolumn">

<!-- END: this line ends content from: inc/begin-rightcolumn.default.html -->
<!-- START: this line starts content from: inc/before-content.default.html -->

    <a name="content"></a>

<!-- END: this line ends content from: inc/before-content.default.html -->
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->

<h1 id="section">2023-02-29</h1>
<p>We continue to make good progress on web site. 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>
<h1 id="section-1">2023-05-22</h1>
<p>We have been busy preparing for an important / significant update to
this web site. 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>
<pre><code>While you are free to look at the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc),
please **do not link to it** as this repo and related web site will disappear once the main
[IOCCC winner repo](https://github.com/ioccc-src/winner) has been updated.

Also be aware that the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc)
is undergoing rapid changes.  There are broken links and other things in mid-change.

Once we are ready to update the [IOCCC winner repo](https://github.com/ioccc-src/winner)
and its associated [www.ioccc.org](index.html) web site,
we will post a news article warning of the pending change that is about to arrive.</code></pre>
<p>These 2645+ changes in the <a
href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc
GitHub repo</a> include diverse things such as:</p>
<ul>
<li>Moving IOCCC entries into their own separate directories</li>
<li>Fixing lots and lots of typos</li>
<li>Fixing Makefiles and code to allow for nearly all winners to be
compiled on modern systems</li>
<li>Reworking the Makefiles to use a consistent set of rules</li>
<li>Reworking the Makefiles to compile under gcc and clang</li>
<li>Replacing the various hint files with a README.md markdown that is
more consistent across IOCCC years</li>
<li>Setting up a system whereby authors of IOCCC entries may update
their own contact information via a GitHub pull request</li>
<li>Setting up to generate the top level <a
href="years.html">years.html</a> file via a tool</li>
<li>Setting up to generate the top level <a
href="authors.html">authors.html</a> file via a tool</li>
<li>etc.</li>
</ul>
<p>We have lots more to do. Our work is not finished. We just wanted to
let you know that we are making good progress.</p>
<p>In regards to the next IOCCC. We <strong>do plan to hold a 28th
IOCCC</strong>. However before we do that, we plan to hold what will be
called <strong>IOCCCMOCK</strong>, a beta-test IOCCC where we plan to
test the new <a
href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</a>,
a tool that will package submissions to the IOCCC.</p>
<p>We are working on an improved <strong>IOCCC submit server</strong>
that will allow those who submit entires to be informed about the status
of their submission. This <strong>IOCCC submit server</strong> will be
beta tested in the <strong>IOCCCMOCK</strong>.</p>
<p>We are working on a method to rapidly post the winners of an IOCCC.
No longer will winners be subject to a long delay between announcing
that they have won and their code being made available. No longer will
procrastination delay the public seeing the winning code. Instead the
<strong>announcement of the winners of an IOCCC will be done by posting
the winning code via a GitHub commit.</strong> Any corrections,
improvement, typo fixes and other fixes will be applied to the winners
via GitHub pull requests: by the authors and/or other interested 3rd
parties.</p>
<p>All the above represent one of the most significant (and useful)
changes to the IOCCC since it started back in 1984. While we are doing
lots of testing, we are sure that issues, mis-features and even bugs
will be uncovered when we <strong>go live</strong>. For this reason, we
plan to beta-test the process by holding an <strong>IOCCCMOCK</strong>.
The <strong>IOCCCMOCK</strong> will be like a regular IOCCC except that
the judges <strong>will not</strong> judge the code. Instead, people
will be invited to submit a simple <em>“Hello, world!”</em> style
program. Awards will be given to those who:</p>
<ul>
<li>submit the best pull requests that fix a bug</li>
<li>submit the best pull requests that fix a typo</li>
<li>make the best suggestions for improvements</li>
<li>have the most fun / make us laugh</li>
<li>etc.</li>
</ul>
<p>The <strong>IOCCCMOCK</strong> will allow is to restart the beta-test
contest should a major problem be discovered 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>
<h1 id="section-2">2023-01-30</h1>
<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 of the most
recent <a href="status.json">status.json</a> modification, in
<em>date(1)</em> format.</p>
<p>We also added to the <a href="status.json">status.json</a> page, a
<em>“latest_news”</em> JSON member whose value is the date of the most
recent news item.</p>
<div class="sourceCode" id="cb2"><pre
class="sourceCode json"><code class="sourceCode json"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="er">&quot;status_date&quot;</span> <span class="er">:</span> <span class="er">&quot;Mon</span> <span class="er">Jan</span> <span class="er">30</span> <span class="er">02:28:44</span> <span class="er">PST</span> <span class="er">2023&quot;,</span></span>
<span id="cb2-2"><a href="#cb2-2" aria-hidden="true" tabindex="-1"></a><span class="er">&quot;latest_news&quot;</span> <span class="er">:</span> <span class="er">&quot;Mon</span> <span class="er">Jan</span> <span class="er">30</span> <span class="er">02:28:44</span> <span class="er">PST</span> <span class="er">2023&quot;</span></span></code></pre></div>
<h1 id="section-3">2022-12-18</h1>
<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 web
site.</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, the
JSON member with name of <strong>“contest”</strong> will change from
<strong>“closed”</strong> to <strong>“open”</strong>.</p>
<p>Additional JSON members be added describing the contest such as the
IOCCC contest number, open date, close date, timezone, etc. The details
of such additional JSON members are <em>TBD</em>.</p>
<p>When an open IOCCC closes, we won’t instantaneously update the <a
href="status.json">status.json</a> page. 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>
<h1 id="section-4">2022-11-29</h1>
<p>We are plan 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>
<pre><code>Please note: As of the date of this posting, our account was just setup,
so there isn&#39;t much to read there, yet.</code></pre>
<p>In the future we plan to use Mastodon as our official announcement
platform. This will include announcing:</p>
<ul>
<li>IOCCC news updates</li>
<li>Start of a new IOCCC</li>
<li>Updates on the IOCCC judging process</li>
<li>Who won the IOCCC</li>
<li>et<strong>C</strong>. :-)</li>
</ul>
<p>When registering for a new IOCCC, we will no longer ask for an
optional twitter handle. Instead, you will be asked if you wish to
provide a Mastodon username when you submit your IOCCC entry. Use of
Mastodon is <strong>NOT</strong> required to enter the IOCCC, but
nevertheless is encouraged. Proving a Mastodon username will be entirely
<strong>optional</strong>.</p>
<p>Non-mastodon users can follow the IOCCC postings via: <a
href="https://fosstodon.org/@ioccc">fosstodon.org/<span class="citation"
data-cites="ioccc">@ioccc</span></a>.</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>
<p>The IOCCC wishes to thank the good folk running the <a
href="https://hub.fosstodon.org/about/">fosstodon.org</a> Mastodon hub.
Their technology focused <a href="https://hub.fosstodon.org">Fosstodon
Hub</a> 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>
<h1 id="section-5">2022-11-19</h1>
<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, and a tool will
form a compressed tarball of their entry.</p>
<p>We are working on a submit server that will allow a registered IOCCC
contestant to upload the above mentioned compressed tarball: when the
contest is open of course.</p>
<p>Once we reach version 1.0, we plan to invite the public to test and
comment.</p>
<p>We plan to hold in 2023, what we will call
<strong>IOCCCMOCK</strong>, a trial IOCCC contest where the 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 web site as well.</p>
<h1 id="section-6">2022-01-15</h1>
<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>
<h1 id="section-7">2021-12-27</h1>
<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 <a href="https://github.com/ioccc-src">IOCCC GitHub
organization site</a>.</p>
<p><strong>We plan to hold IOCCC28 in 2023.</strong> Sorry for the
delay, but we think you will appreciate the re-tooling when it is
completed. Stay tuned!</p>
<h1 id="section-8">2021-10-21</h1>
<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 <a href="https://github.com/ioccc-src/winner">GitHub</a>.</p>
<p>For example, when we announce the winners, we will do so by
committing their code to the <a href="/years.html">Winning entries</a>
of the IOCCC repo, so that people will be able immediately view the
winning source.</p>
<p>We plan to refactor and modernize the IOCCC web site. We also plan to
build a new and improved way to submit entries the next IOCCC. As a
result of all this work we need to do, <strong>we plan to hold IOCCC28
in 2023 instead of 2021</strong>. Sorry for the delay, but we think you
will appreciate the re-tooling when it is completed.</p>
<p><strong>Stay tuned for how you may be able to help in the IOCCC
redesign for IOCCC28!</strong></p>

<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- START: this line starts content from: inc/after-content.default.html -->

<!-- END: this line ends content from: inc/after-content.default.html -->
<!-- START: this line starts content from: inc/end-rightcolumn.default.html -->

  </div>

<!-- END: this line ends content from: inc/end-rightcolumn.default.html -->
<!-- START: this line starts content from: inc/end-row.default.html -->

</div>

<!-- END: this line ends content from: inc/end-row.default.html -->
<!-- START: this line starts content from: inc/footer.default.html -->

<div class="footer">
  <hr>
  <h2>Coda</h2>
  <p><a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2Flocation.html">Nu HTML check this web page</a></p>
  <p><a href="#top">Jump to top</a> <a href="#content">Jump to Content</a> <a href="#inventory">Jump to Inventory</a></p>
</div>

<!-- END: this line ends content from: inc/footer.default.html -->
<!-- START: this line starts content from: inc/bottom.default.html -->

</body>
</html>

<!-- END: this line ends content from: inc/bottom.default.html -->