build remaining top level web pages
The level judges.html, news.html, and index.html pages were converted to markdown. The `bin/gen-top-md2html.sh` tool was adjusted to build HTML from judges.md, news.md, and index.md. Modified the `bin/gen-top-md2html.sh` tool to build `bin/index.html` from `bin/README.md`. Modified the `bin/gen-top-md2html.sh` tool to build `inc/index.html` from `inc/README.md`. In `bin/gen-top-md2html.sh` changed VERISON from "1.0 2024-02-24" to "1.1 2024-02-28". Ran `gen_top_md2html` to perform the above.
This commit is contained in:
1 parent
21c3e89a2f
commit
0f8a0a3af9
10 files changed
+1788
-554
No files matched your search
@@ -1,412 +1,341 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
|
||||
<LINK REL="shortcut icon" HREF="/ioccc.ico">
|
||||
<link rel="stylesheet" type="text/css" href="tmp/old-ioccc.css">
|
||||
<META name="description" content="International Obfuscated C Code Contest">
|
||||
<META name="keywords" content="International, Obfuscated, C, c, IOCCC,ioccc, obfuscated, Obfuscate, obfuscate, Landon Curt Noll, chongo, Leonid A. Broukhis, leob">
|
||||
<TITLE>News from The International Obfuscated C Code Contest</TITLE>
|
||||
</HEAD>
|
||||
<BODY TEXT="#000000">
|
||||
<!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-md2html.sh -->
|
||||
<!-- The HTML was converted from markdown by the tool: bin/md2html.sh -->
|
||||
<!-- -->
|
||||
<!-- START: this line starts content from: inc/head.default.html -->
|
||||
|
||||
<CENTER><a HREF="2011/zucker/README.md"><IMG ALT="IOCCC" SRC="png/ioccc.png"></a><br><FONT SIZE="1">Logo by winner <a href="2011/zucker/README.md">Matt Zucker</a></font></CENTER><BR>
|
||||
<CENTER><FONT SIZE="6"><I>The International Obfuscated C Code
|
||||
Contest </I></FONT></CENTER><BR>
|
||||
<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>
|
||||
|
||||
<HR>
|
||||
<CENTER><FONT SIZE="6"><I>THIS IS AN EXPERIMENTAL IOCCC WEB SITE </I></FONT></CENTER>
|
||||
<P>
|
||||
<H2>IMPORTANT: This is NOT the official IOCCC web site!</H2>
|
||||
<P>
|
||||
Please visit
|
||||
<A HREF="https://www.ioccc.org/index.html">www.ioccc.org</A>
|
||||
for the official IOCCC web.
|
||||
<P>
|
||||
Please do <B>NOT</B> bookmark or link to this
|
||||
<A HREF="https://ioccc-src.github.io/temp-test-ioccc/">experimental web site</A>:
|
||||
<BLOCKQUOTE>
|
||||
<A HREF="https://ioccc-src.github.io/temp-test-ioccc/">https://ioccc-src.github.io/temp-test-ioccc/</A>
|
||||
</BLOCKQUOTE>
|
||||
<P>
|
||||
When this experiment is finished, this site <B>will go away</B>!
|
||||
<P>
|
||||
This test web tree is part of the
|
||||
<A HREF="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</A> GitHub repo:
|
||||
<BLOCKQUOTE>
|
||||
<A HREF="https://github.com/ioccc-src/temp-test-ioccc">https://github.com/ioccc-src/temp-test-ioccc</A>
|
||||
</BLOCKQUOTE>
|
||||
<P>
|
||||
This web site will be undergoing major changes, so expect many broken links, typos and other problems.
|
||||
If you wish to recommend changes (understanding that things may be rapidly changing out from under your copy),
|
||||
then consider making pull requests against the
|
||||
<A HREF="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</A> GitHub repo.
|
||||
<HR>
|
||||
<!-- END: this line ends content from: inc/head.default.html -->
|
||||
<!-- START: this line starts content from: inc/body.default.html -->
|
||||
|
||||
<P>
|
||||
<CENTER>
|
||||
<A HREF="index.html">IOCCC home page</A> |
|
||||
<A HREF="years.html">Winning entries</A> |
|
||||
<A HREF="authors.html">People who have won</A>
|
||||
<BR><BR>
|
||||
<A HREF="news.html">IOCCC News</a> |
|
||||
<A HREF="faq.html#submit">How to enter the IOCCC</A> |
|
||||
<A HREF="faq.html">FAQ</A>
|
||||
<BR><BR>
|
||||
<A HREF="bugs.md">Known Bugs & (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 winner info</A> |
|
||||
<A HREF="thanks-for-help.md">Thanks for the help</A>
|
||||
<BR><BR>
|
||||
<A HREF="judges.html">The judges</A> |
|
||||
<A HREF="contact.html">Contacting the IOCCC</A>
|
||||
</CENTER>
|
||||
<body>
|
||||
|
||||
<HR>
|
||||
<!-- END: this line ends content from: inc/body.default.html -->
|
||||
<!-- START: this line starts content from: inc/header.default.html -->
|
||||
|
||||
<A NAME="news"></A>
|
||||
<H2>IOCCC news</H2>
|
||||
<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>
|
||||
|
||||
<UL>
|
||||
<LI TYPE=none><B>2023-05-22</B>
|
||||
<UL><LI TYPE=square>
|
||||
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.
|
||||
<BLOCKQUOTE>
|
||||
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 <B>do not link to it</B> as this repo and related web site will disappear once the main
|
||||
<A HREF="https://github.com/ioccc-src/winner">IOCCC winner repo</A> has been updated.
|
||||
<P>
|
||||
Also be aware that the <A HREF="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</A>
|
||||
<!-- 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 & (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.
|
||||
<P>
|
||||
Once we are ready to update the <A HREF="https://github.com/ioccc-src/winner">IOCCC winner repo</A>
|
||||
and its associated <A HREF="https://www.ioccc.org/index.html">www.ioccc.org</A> web site,
|
||||
we will post a news article warning of the pending change that is about to arrive.
|
||||
</BLOCKQUOTE>
|
||||
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> Fixing lots and lots of typos
|
||||
<LI> Fixing Makefiles and code to allow for nearly all winners to be compiled on modern systems
|
||||
<LI> Reworking the Makefiles to use a consistent set of rules
|
||||
<LI> Reworking the Makefiles to compile under gcc and clang
|
||||
<LI> Replacing the various hint files with a README.md markdown that is more consistent across IOCCC years
|
||||
<LI> Setting up a system whereby authors of IOCCC entries may update their own contact information via a GitHub pull request
|
||||
<LI> Setting up to generate the top level <A HREF="https://www.ioccc.org/years.html">years.html</A> file via a tool
|
||||
<LI> Setting up to generate the top level <A HREF="https://www.ioccc.org/authors.html">authors.html</A> file via a tool
|
||||
<LI> etc.
|
||||
</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>
|
||||
In regards to the next IOCCC. We <B>do plan to hold a 28th IOCCC</B>. However before we do that, we plan
|
||||
to hold what will be called <B>IOCCCMOCK</B>, 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>
|
||||
We are working on an improved <B>IOCCC submit server</B>
|
||||
that will allow those who submit entires to be informed about the status of their submission.
|
||||
This <B>IOCCC submit server</B> will be beta tested in the <B>IOCCCMOCK</B>.
|
||||
<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
|
||||
<B>announcement of the winners of an IOCCC will be done by posting the winning code via a GitHub commit.</B>
|
||||
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>
|
||||
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 <B>go live</B>. For this reason, we plan to beta-test the process by holding an <B>IOCCCMOCK</B>.
|
||||
The <B>IOCCCMOCK</B> will be like a regular IOCCC except that the judges <B>will not</B> judge the code.
|
||||
Instead, people will be invited to submit a simple <I>"Hello, world!"</I> style program.
|
||||
Awards will be given to those who:
|
||||
<P>
|
||||
<UL>
|
||||
<LI> submit the best pull requests that fix a bug
|
||||
<LI> submit the best pull requests that fix a typo
|
||||
<LI> make the best suggestions for improvements
|
||||
<LI> have the most fun / make us laugh
|
||||
<LI> etc.
|
||||
</UL>
|
||||
<P>
|
||||
The <B>IOCCCMOCK</B> will allow is to restart the beta-test contest should a major problem be discovered
|
||||
that needs urgent fixing.
|
||||
The <B>IOCCCMOCK</B> will us to beta-test the new IOCCC process without putting the hard work of those
|
||||
who submit real IOCCC entries at risk.
|
||||
<P>
|
||||
Stay tuned!
|
||||
</UL>
|
||||
</UL>
|
||||
|
||||
<UL>
|
||||
<LI TYPE=none><B>2023-01-30</B>
|
||||
<UL><LI TYPE=square>
|
||||
We added to the
|
||||
<A HREF="status.json">status.json</A> page,
|
||||
a <I>"status_date"</I> JSON member whose value is the date
|
||||
of the most recent <A HREF="status.json">status.json</A> modification,
|
||||
in <I>date(1)</I> format.
|
||||
<P>
|
||||
We also added to the
|
||||
<A HREF="status.json">status.json</A> page,
|
||||
a <I>"latest_news"</I> JSON member whose value is the date
|
||||
of the most recent news item.
|
||||
<P>
|
||||
For example:
|
||||
<BLOCKQUOTE><PRE>
|
||||
"status_date" : "Mon Jan 30 02:28:44 PST 2023",
|
||||
"latest_news" : "Mon Jan 30 02:28:44 PST 2023"
|
||||
</PRE></BLOCKQUOTE>
|
||||
</UL>
|
||||
</UL>
|
||||
|
||||
<UL>
|
||||
<LI TYPE=none><B>2022-12-18</B>
|
||||
<UL><LI TYPE=square>
|
||||
As per the suggestion of <A HREF="https://fosstodon.org/@Virtaava@home.social">Toni
|
||||
Mikkola</A> (<I>@Virtaava@home.social</I>) we now maintain a
|
||||
<A HREF="status.json">status.json</A> page on this web site.
|
||||
<P>
|
||||
In addition to the IOCCC-style <I>easter egg</I>, you may count on
|
||||
the JSON status page having a JSON member with name of <B>"contest"</B>
|
||||
that will have a value of either <B>"closed"</B> or <B>"open"</B>.
|
||||
When a future <B>IOCCC</B> is announced or the IOCCC is currently open,
|
||||
the JSON member with name of <B>"contest"</B> will change from
|
||||
<B>"closed"</B> to <B>"open"</B>.
|
||||
<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 <I>TBD</I>.
|
||||
<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 <B>@ioccc@fosstodon.org</B>.
|
||||
</UL>
|
||||
</UL>
|
||||
|
||||
<UL>
|
||||
<LI TYPE=none><B>2022-11-29</B>
|
||||
<UL><LI TYPE=square>
|
||||
We are plan to abandon our
|
||||
<A HREF="https://twitter.com/ioccc">IOCCC Twitter feed</A>
|
||||
in favor of our new
|
||||
<A REL="me" HREF="https://fosstodon.org/@ioccc">IOCCC Mastodon</A> feed.
|
||||
<P>
|
||||
Our Mastodon username is: <B>@ioccc@fosstodon.org</B>.
|
||||
<BLOCKQUOTE>
|
||||
Please note: As of the date of this posting, our account was just setup,
|
||||
so there isn't much to read there, yet.
|
||||
</BLOCKQUOTE>
|
||||
<P>
|
||||
In the future we plan to use Mastodon as our official announcement platform.
|
||||
This will include announcing:
|
||||
<UL>
|
||||
<LI> IOCCC news updates
|
||||
<LI> Start of a new IOCCC
|
||||
<LI> Updates on the IOCCC judging process
|
||||
<LI> Who won the IOCCC
|
||||
<LI> et<B>C</B>. :-)
|
||||
</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 <B>NOT</B> required to enter the IOCCC, but nevertheless is encouraged.
|
||||
Proving a Mastodon username will be entirely <B>optional</B>.
|
||||
<P>
|
||||
Non-mastodon users can follow the IOCCC postings via:
|
||||
<A HREF="https://fosstodon.org/@ioccc">fosstodon.org/@ioccc</A>.
|
||||
<P>
|
||||
If you do not yet have a Mastodon account, you may obtain a <B>free mastodon account via</B>:
|
||||
<A HREF="https://joinmastodon.org">joinmastodon.org</A>.
|
||||
<P>
|
||||
If you do have / obtain a Mastodon account, <B>please do us a favor and
|
||||
follow the IOCCC at:</B>
|
||||
<BLOCKQUOTE>
|
||||
<B>@ioccc@fosstodon.org</B>
|
||||
</BLOCKQUOTE>
|
||||
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>
|
||||
Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!
|
||||
</UL>
|
||||
</UL>
|
||||
|
||||
<UL>
|
||||
<LI TYPE=none><B>2022-11-19</B>
|
||||
<UL><LI TYPE=square>
|
||||
Source code has been released for version <B>0.8.1 2022-11-19</B> 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>
|
||||
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>
|
||||
Once we reach version 1.0, we plan to invite the public to test and comment.
|
||||
<P>
|
||||
We plan to hold in 2023, what we will call <B>IOCCCMOCK</B>, 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>
|
||||
We are working on complete rebuild of this web site as well.
|
||||
</UL><BR>
|
||||
|
||||
<LI TYPE=none><B>2022-01-15</B>
|
||||
<UL><LI TYPE=square>
|
||||
Source code has been released for version <B>0.24 2022-01-15</B> of the
|
||||
<A HREF="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</A>,
|
||||
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">"status_date"</span> <span class="er">:</span> <span class="er">"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",</span></span>
|
||||
<span id="cb2-2"><a href="#cb2-2" aria-hidden="true" tabindex="-1"></a><span class="er">"latest_news"</span> <span class="er">:</span> <span class="er">"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"</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'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).
|
||||
</UL><BR>
|
||||
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>
|
||||
|
||||
<LI TYPE=none><B>2021-12-27</B>
|
||||
<UL><LI TYPE=square>
|
||||
<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>
|
||||
<B>We plan to hold IOCCC28 in 2023.</B>
|
||||
Sorry for the delay, but we think you will appreciate the re-tooling
|
||||
when it is completed.
|
||||
Stay tuned!
|
||||
</UL><BR>
|
||||
<!-- 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 -->
|
||||
|
||||
<A NAME="IOCCC28-in-2022"></A>
|
||||
<LI TYPE=none><B>2021-10-21</B>
|
||||
<UL><LI TYPE=square>
|
||||
<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>
|
||||
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>
|
||||
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,
|
||||
<B>we plan to hold IOCCC28 in 2023 instead of 2021</B>.
|
||||
Sorry for the delay, but we think you will appreciate the re-tooling
|
||||
when it is completed.
|
||||
<P>
|
||||
<B>Stay tuned for how you may be able to help in the IOCCC redesign for IOCCC28!</B>
|
||||
</UL><BR>
|
||||
<!-- END: this line ends content from: inc/after-content.default.html -->
|
||||
<!-- START: this line starts content from: inc/end-rightcolumn.default.html -->
|
||||
|
||||
<!--
|
||||
<LI TYPE=none><B>2021-01-04</B>
|
||||
<UL><LI TYPE=square>Email to <B>IOCCC</B>, via this email address:
|
||||
<BLOCKQUOTE><B><A HREF="mailto:q.2021@ioccc.org">q.2021@ioccc.org</A></B></BLOCKQUOTE>
|
||||
with the following two words (separated by a space) somewhere in the subject of your email:
|
||||
<BLOCKQUOTE><B>IOCCC 2021</B></BLOCKQUOTE>
|
||||
works again.
|
||||
We apologize for the Email outage of the past few days.
|
||||
</UL><BR>
|
||||
</div>
|
||||
|
||||
<LI TYPE=none><B>2021-01-02</B>
|
||||
<UL><LI TYPE=square>A temporary side effect of our move to using
|
||||
<A HREF="https://github.com/ioccc-src/winner">GitHub</A>,
|
||||
Email to/from <B>*@ioccc.org</B> has been disabled.
|
||||
We expect restore Email service in a few days.
|
||||
When we do, we will announce restoration of Email service here.
|
||||
</UL><BR>
|
||||
<!-- END: this line ends content from: inc/end-rightcolumn.default.html -->
|
||||
<!-- START: this line starts content from: inc/end-row.default.html -->
|
||||
|
||||
<LI TYPE=none><B>2020-12-31</B>
|
||||
<UL><LI TYPE=square>Released the
|
||||
<A HREF="/years.html#2020">winners of the 27<sup>th</sup> IOCCC</A>.
|
||||
<LI TYPE=square>Moved the <B>IOCCC</B> source tree and web site to
|
||||
<A HREF="https://github.com/ioccc-src/winner">GitHub</A>.
|
||||
</UL><BR>
|
||||
</div>
|
||||
|
||||
<LI TYPE=none><B>2020-07-25</B>
|
||||
<UL><LI TYPE=square>The <A HREF="2020/whowon.html">winners of the 27<sup>th</sup> IOCCC</A> have been announced. Congratulations!
|
||||
</UL><BR>
|
||||
<!-- END: this line ends content from: inc/end-row.default.html -->
|
||||
<!-- START: this line starts content from: inc/footer.default.html -->
|
||||
|
||||
<LI TYPE=none><B>2020-03-22</B>
|
||||
<UL><LI TYPE=square>Due to current world events, we are extending the 27<sup>th</sup> IOCCC until 2020-May-15 06:26:49 UTC
|
||||
<LI TYPE=square>The <a href="https://submit.ioccc.org">submission tool</a> will now be active until 2020-May-15 06:26:49 UTC
|
||||
</UL><BR>
|
||||
<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>
|
||||
|
||||
<LI TYPE=none><B>2019-10-13</B>
|
||||
<UL><LI TYPE=square>The <A HREF="years.html#2019">source code</A> for the winners of the 26<sup>th</sup> IOCCC has been released.
|
||||
<LI TYPE=square>The 27<sup>th</sup> IOCCC will be open from <B>2019-Dec-26 06:01:41 UTC</B> (Boxing Day)<br>to <B>2020-Mar-15 06:26:49 UTC</B> (Ides of March).
|
||||
<LI TYPE=square>The <a href="https://submit.ioccc.org">submission tool</a> will be available around <B>2020-Jan-15 15:15:15 UTC</B>.
|
||||
<LI TYPE=square>Draft <A HREF="2020/rules.txt">Rules</A>, <A HREF="2020/guidelines.txt">Guidelines</A> and <A HREF="2020/iocccsize.c">IOCCC size tool</A> for the 27<sup>th</sup> IOCCC are available.
|
||||
</UL><BR>
|
||||
<!-- END: this line ends content from: inc/footer.default.html -->
|
||||
<!-- START: this line starts content from: inc/bottom.default.html -->
|
||||
|
||||
<LI TYPE=none><B>2019-06-16</B>
|
||||
<UL><LI TYPE=square>Due to some delays, we now plan to publish source and annotations in early July 2019.
|
||||
</UL><BR>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
<LI TYPE=none><B>2019-05-11</B>
|
||||
<UL><LI TYPE=square>The <A HREF="2019/whowon.html">winners of the 26<sup>th</sup> IOCCC</A> have been announced. Congratulations!
|
||||
</UL><BR>
|
||||
|
||||
<LI TYPE=none><B>2019-03-16</B>
|
||||
<UL><LI TYPE=square>The 26<sup>th</sup> IOCCC is now closed and Judging has commenced.
|
||||
</UL><BR>
|
||||
|
||||
<LI TYPE=none><B>2018-12-26</B>
|
||||
<UL><LI TYPE=square>The 26<sup>th</sup> IOCCC will be open from <B>2018-Dec-26 16:06:69</B> to <B>2019-Mar-15 00:86:07</B>.
|
||||
<LI TYPE=square>The <a href="https://submit.ioccc.org">submission tool</a> will be available around <B>2019-Jan-15 15:15:15 UTC</B>.
|
||||
<LI TYPE=square>Draft <A HREF="2019/rules.txt">Rules</A>, <A HREF="2019/guidelines.txt">Guidelines</A> and <A HREF="2019/iocccsize.c">IOCCC size tool</A> are available.
|
||||
</UL><BR>
|
||||
|
||||
<LI TYPE=none><B>2018-05-06</B>
|
||||
<UL><LI TYPE=square>The <A HREF="years.html#2018">source code</A> for the winners of the 25<sup>th</sup> IOCCC has been released.
|
||||
</UL><BR>
|
||||
|
||||
<LI TYPE=none><B>2018-04-01</B>
|
||||
<UL><LI TYPE=square>The <A HREF="2018/whowon.html">winners of the 25<sup>th</sup> IOCCC</A> have been announced. Congratulations!
|
||||
<LI TYPE=square>We plan to publish source and annotations in the next 30 days
|
||||
</UL><BR>
|
||||
|
||||
<LI TYPE=none><B>2018-02-16</B>
|
||||
<UL><LI TYPE=square>Due to a scheduling conflict with one of the <A HREF="judges.html">IOCCC judges</A>, the 25<sup>th</sup> IOCCC end date is now the Ides of March.
|
||||
<LI TYPE=square>Please <a href="https://submit.ioccc.org">submit</a> your entries by 2018-Mar-15 03:08:07 UTC.
|
||||
<LI TYPE=square>Updated: The 25<sup>th</sup> IOCCC will be open from <B>2017-Dec-29 05:38:51 UTC</B> to <B>2018-Mar-15 03:08:07 UTC</B>.
|
||||
</UL><BR>
|
||||
|
||||
<LI TYPE=none><B>2018-01-19</B>
|
||||
<UL><LI TYPE=square>There is a delay in making the <a href="https://submit.ioccc.org">submission tool</a> available. Please retry on <B>2018-Jan-21 23:09:09 UTC</B>.
|
||||
</UL><BR>
|
||||
-->
|
||||
</UL>
|
||||
|
||||
<P>Older news has been archived, but is not currently available.</P>
|
||||
|
||||
<HR>
|
||||
|
||||
<table><tr>
|
||||
<td><img alt="Creative Commons CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0 International License"
|
||||
style="border-width:0" width="88" height="31" src="png/by-sa.88x31.png" /></td>
|
||||
<td>© Copyright 1984-2023,
|
||||
<a href="judges.html">Landon Curt Noll and Leonid A. Broukhis.</a> - All rights reserved.<br><br>
|
||||
This work is licensed under the
|
||||
<a href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative
|
||||
Commons CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0 International License</a>.<br><br>
|
||||
If you do use this work in some form, the
|
||||
<a href="judges.html">IOCCC judges</a> would appreciate (but does not require)
|
||||
if you were to <a href="contact.html">send us a note about your use</a>.</td>
|
||||
</tr></table>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
<!-- END: this line ends content from: inc/bottom.default.html -->
|
||||
Reference in new issue
Block a user