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

add news.html, move how-to-enter.md into faq.md

Browse Source 
Moved news from index.html to news.html.

Moved how-to-enter.md into FAQ 2.6.

Moved FAQ 0.2 to FAQ 2.5.
This commit is contained in:
Landon Curt Noll committed 2023-11-29 16:49:37 -08:00
1 parent 987fcca624
commit b6beda55a9
4 files changed
+502 -418
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

faq.md
+79 -63
View File
@@ -3,7 +3,6 @@
## Section 0 - [History of the IOCCC](#faq0)
- [0.0 - How did the IOCCC get started?](#faq0_0)
- [0.1 - Why are some years missing IOCCC winners?](#faq0_1)
- [0.2 - Why do some IOCCC winners receive the Grand Prize or Best of Show award?](#faq0_2)
## Section 1 - [Submitting entries to a new IOCCC](#faq1)
- [1.0 - How do I submit my entry to the IOCCC?](#faq1_0)
@@ -18,6 +17,8 @@
- [2.2 - Why don't you publish non-winners?](#faq2_2)
- [2.3 - How much time does it take to judge the contest?](#faq2_3)
- [2.4 - How many judging rounds do you have?](#faq2_4)
- [2.5 - Why do some IOCCC winners receive the Grand Prize or Best of Show award?](#faq2_5)
- [2.6 - How are IOCCC winners announced?](#faq2_6)
## Section 3 - [Compiling and running IOCCC winners](#faq3)
- [3.0 - What Makefile are available to build or clean up IOCCC winners?](#faq3_0)
@@ -150,79 +151,30 @@ The pause during the 2021-2023 period was due to the IOCCC judges developing too
make is much more likely for the IOCCC to be held in a yearly basis later on.
### <a name="faq0_2"></a>FAQ 0.2: Why do some IOCCC winners receive the Grand Prize or Best of Show award?
In some years, the IOCCC judges discover a truly amazing IOCCC winner that
stands out among all of the other IOCCC entries received that year.
For such an IOCCC winner, the IOCCC judges award a "Grand Prize"
or "Best of Show award.
In 1984-1987, the grand prize winners are:
- [1984/mullender](years.html#1984_mullender)
- [1985/shapiro](years.html#1985_shapiro)
- [1986/wall](years.html#1986_wall)
- [1987/lievaart](years.html#1987_lievaart)
Starting from 1988, the entry we liked the most in that year is called
"Best of Show". Here are the "Best of Show" entries:
- [1988/applin](years.html#1988_applin)
- [1989/jar.2](years.html#1989_jar.2)
- [1990/theorem](years.html#1990_theorem)
- [1991/brnstnd](years.html#1991_brnstnd)
- [1992/vern](years.html#1992_vern)
- [1996/august](years.html#1996_august)
- [1998/banks](years.html#1998_banks)
- [2000/jarijyrki](years.html#2000_jarijyrki)
- [2020/carlini](years.html#2020_carlini)
In 1993, 1994 and 1995 the judges were unable to select a clear overall
winner. So to give a nod to the entry that had the highest approval ranking
from the judges, they used the following awards:
- [1993/rince](years.html#1993_rince) - Most Well Rounded
- [1994/shapiro](years.html#1994_shapiro) - Most Well Rounded
- [1995/leo](years.html#1995_leo) - Best Use of Obfuscation
These could be considered the 'best entry' for those years with 1 or
more other entries that came in close behind.
## <a name="faq1"></a>Section 1: Submitting entries to a new IOCCC
### <a name="faq1_0"></a><a name="submit"></a>FAQ 1.0: How do I submit my entry to the IOCCC?
0) check to see of the IOCCC is open
0. Verify that for submissions.
Check the [status.json](https://www.ioccc.org/status.json) URL and
check the [IOCCC news](https://www.ioccc.org/index.html#news) to
Check the [status.json](status.json) URL and
check the [IOCCC news](news.html#news) to
see of the IOCCC is open.
You may only submit your entries to the IOCCC when the IOCCC is **OPEN**.
You may only register for the IOCCC
and you may only submit your entries to the IOCCC when the IOCCC is **OPEN**.
1) register for the IOCCC
1. Register for the IOCCC
```
XXX - instructions TBD - XXX
```
Once you have been registered, you will receive an email message for how to
prepare your entries for submission, and how to upload the compressed tarballs
to our submission portal.
2) obtain the latest mkiocccentry toolkit
2. Obtain the latest mkiocccentry toolkit
If you do not have an mkiocccentry tool directory:
@@ -240,13 +192,13 @@ git fetch
git rebase
```
3) Make the mkiocccentry toolkit
3. Make the mkiocccentry toolkit
```sh
make clobber all
```
4) run the mkiocccentry tool to form your entry tarball
4. Run the mkiocccentry tool to form your entry tarball
```sh
./mkiocccentry work_dir prog.c Makefile remarks.md [file ...]
@@ -270,7 +222,7 @@ remarks.md Remarks about your entry in markdown format
NOTE: It is *NOT* necessary to install the tools to use them as you can run
the tools from the top of the _mkiocccentry repo_ directory just fine.
5) upload your entry to the IOCCC submit server
5. upload your entry to the IOCCC submit server
```
XXX - instructions TBD - XXX
@@ -575,6 +527,70 @@ when usually report when the IOCCC judges start near final judging rounds, and
sometimes we also report when we enter what we believe is the final judging round, so you may guess that we have at least 3 rounds. :-) The actual number of rounds is certainly more than 3.
### <a name="faq2_5"></a>FAQ 2.5: Why do some IOCCC winners receive the Grand Prize or Best of Show award?
In some years, the IOCCC judges discover a truly amazing IOCCC winner that
stands out among all of the other IOCCC entries received that year.
For such an IOCCC winner, the IOCCC judges award a "Grand Prize"
or "Best of Show award.
In 1984-1987, the grand prize winners are:
- [1984/mullender](years.html#1984_mullender)
- [1985/shapiro](years.html#1985_shapiro)
- [1986/wall](years.html#1986_wall)
- [1987/lievaart](years.html#1987_lievaart)
Starting from 1988, the entry we liked the most in that year is called
"Best of Show". Here are the "Best of Show" entries:
- [1988/applin](years.html#1988_applin)
- [1989/jar.2](years.html#1989_jar.2)
- [1990/theorem](years.html#1990_theorem)
- [1991/brnstnd](years.html#1991_brnstnd)
- [1992/vern](years.html#1992_vern)
- [1996/august](years.html#1996_august)
- [1998/banks](years.html#1998_banks)
- [2000/jarijyrki](years.html#2000_jarijyrki)
- [2020/carlini](years.html#2020_carlini)
In 1993, 1994 and 1995 the judges were unable to select a clear overall
winner. So to give a nod to the entry that had the highest approval ranking
from the judges, they used the following awards:
- [1993/rince](years.html#1993_rince) - Most Well Rounded
- [1994/shapiro](years.html#1994_shapiro) - Most Well Rounded
- [1995/leo](years.html#1995_leo) - Best Use of Obfuscation
These could be considered the 'best entry' for those years with 1 or
more other entries that came in close behind.
### <a name="faq2_6"></a>FAQ 2.6: How are IOCCC winners announced?
Once the [IOCCC](https://www.ioccc.org/index.html#enter) closes, the judges
will select the [winning entries](https://www.ioccc.org/years.html) announce them
on the [@IOCCC mastodon feed](https://fosstodon.org/@ioccc), notify the winners
via email using their previously registered email address, and upload the
winning code to the [winner repo](https://github.com/ioccc-src/winner)
which in turn will cause them to be displayed on the [IOCCC winning entries
page](https://www.ioccc.org/years.html).
## <a name="faq3"></a>Section 3: Compiling and running IOCCC winners
how-to-enter.md
-21
View File
@@ -1,21 +0,0 @@
# How to submit to the IOCCC
## Submit to the IOCCC
0. Verify that the [IOCCC is open](https://www.ioccc.org/index.html#enter) for
submissions.
1. If the IOCCC is open, you need to register as a contestant. See [how to
enter](https://www.ioccc.org/index.html#enter) for how to register.
2. Once you have been registered, you will receive an email message for how to
prepare your entries for submission, and how to upload the compressed tarballs
to our submission portal.
3. Once the [IOCCC](https://www.ioccc.org/index.html#enter) closes, the judges
will select the [winning entries](https://www.ioccc.org/years.html) announce them
on the [@IOCCC mastodon feed](https://fosstodon.org/@ioccc), notify the winners
via email using their previously registered email address, and upload the
winning code to the [winner repo](https://github.com/ioccc-src/winner)
which in turn will cause them to be displayed on the [IOCCC winning entries
page](https://www.ioccc.org/years.html).
index.html
+9 -334
View File
@@ -48,17 +48,17 @@ then consider making pull requests against the
<A HREF="judges.html">The judges</A> |
<B>IOCCC home page</B> |
<A HREF="faq.html">FAQ</A> |
<A HREF="index.html#enter">How to enter</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
<BR><BR>
<A HREF="index.html#news">IOCCC news</A> |
<A HREF="winners.html">People who have won</A> |
<A HREF="years.html">Winning entries</A>
<A HREF="contact.html">Contacting the IOCCC</A> |
<A HREF="news.html#news">IOCCC news</A>
<BR><BR>
<A HREF="bugs.md">Known Bugs &amp; (Mis)features</A> |
<A HREF="how-to-help.md">How to fix an IOCCC winner</A> |
<A HREF="thanks-for-fixes.md">Thanks for the fixes</A> |
<A HREF="www-history.md">A bit of web site history</A>
<A HREF="news.html#news">IOCCC news</A> |
<BR><BR>
<A HREF="index.html#news">IOCCC news</A> |
<A HREF="winners.html">People who have won</A> |
<A HREF="years.html">Winning entries</A>
</CENTER>
<P>
@@ -70,12 +70,10 @@ then consider making pull requests against the
<P>Right now, you <B>CANNOT register</B> as a contestant with the IOCCC,<BR>
nor can you submit an entry because the <B>IOCCC</B> is yet <B>NOT open</B>.
<P>Please see the watch the <A HREF="index.html#news">IOCCC news</A> below for information on the next <B>IOCCC</B>.
<P>Please see the watch the <A HREF="news.html#news">IOCCC news</A> below for information on the next <B>IOCCC</B>.
<P>You may also check on the <A HREF="status.json">status.json</A> for the current status of the <B>IOCCC</B>.
Additional details in the <A HREF="how-to-enter.md">how to enter</A> may be of further help.
<A NAME="goals"></A>
<HR>
@@ -107,330 +105,7 @@ to darken &lt; fuscus, dark.] -obfuscation n. obfuscatory adj<BR>
<A NAME="news"></A>
<H2>IOCCC news</H2>
<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 GitHiub repo</A>,
we have made nearly 2000 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 GitHiub 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 GitHiub repo</A>
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 2000+ changes in the <A HREF="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHiub repo</A>
include diverse things such as:
<P>
<UL>
<LI> Moving IOCCC winners 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/winners.html">winners.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>,
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>
<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>
<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>
<!--
<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="&#109;&#97;&#105;l&#x74;&#111;&#58;&#113;&#46;&#x32;&#x30;2&#x31;&#x40;&#x69;&#x6F;&#x63;&#x63;&#x63;&#46;&#111;&#x72;&#x67;">&#x71;&#46;&#x32;0&#50;&#49;&#x40;&#x69;&#x6F;&#x63;cc&#46;&#111;&#x72;&#x67;</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>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<A HREF="news.html#news">IOCCC news has moved to news.html</A>.
<HR>
news.html
+414
View File
@@ -0,0 +1,414 @@
<!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">
<CENTER><a HREF="2011/zucker/hint.html"><IMG ALT="IOCCC" SRC="png/ioccc.png"></a><br><FONT SIZE="1">Logo by winner <a href="2011/zucker/hint.html">Matt Zucker</a></font></CENTER><BR>
<CENTER><FONT SIZE="6"><I>The International Obfuscated C Code
Contest </I></FONT></CENTER><BR>
<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 nor 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>
<P>
<CENTER>
<A HREF="judges.html">The judges</A> |
<A HREF="index.hml">IOCCC home page</A> |
<A HREF="faq.html">FAQ</A> |
<A HREF="index.html#enter">How to enter</A> |
<A HREF="contact.html">Contacting the IOCCC</A>
<BR><BR>
<A HREF="bugs.md">Known Bugs &amp; (Mis)features</A> |
<A HREF="how-to-help.md">How to fix an IOCCC winner</A> |
<A HREF="thanks-for-fixes.md">Thanks for the fixes</A> |
<B>IOCCC news</B>
<BR><BR>
<A HREF="index.html#news">IOCCC news</A> |
<A HREF="winners.html">People who have won</A> |
<A HREF="years.html">Winning entries</A>
</CENTER>
<HR>
<A NAME="news"></A>
<H2>IOCCC news</H2>
<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 GitHiub repo</A>,
we have made nearly 2000 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 GitHiub 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 GitHiub repo</A>
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 2000+ changes in the <A HREF="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHiub repo</A>
include diverse things such as:
<P>
<UL>
<LI> Moving IOCCC winners 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/winners.html">winners.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>,
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>
<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>
<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>
<!--
<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="&#109;&#97;&#105;l&#x74;&#111;&#58;&#113;&#46;&#x32;&#x30;2&#x31;&#x40;&#x69;&#x6F;&#x63;&#x63;&#x63;&#46;&#111;&#x72;&#x67;">&#x71;&#46;&#x32;0&#50;&#49;&#x40;&#x69;&#x6F;&#x63;cc&#46;&#111;&#x72;&#x67;</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>
<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>
<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>
<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>
<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>
<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>
<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>
<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><A REL="license" HREF="https://creativecommons.org/licenses/by-sa/3.0/"><IMG ALT="Creative Commons License" STYLE="border-width:0" SRC="/png/by-sa-3.0-88x31.png"></A></TD>
<TD><P>&copy; Copyright 1984-2023,
<A HREF="/judges.html">Leo Broukhis, Landon Curt Noll</A>
- All rights reserved<BR>
This work is licensed under a <A REL="license" HREF="https://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</A>.</P></TD>
<TD>&nbsp;
</TR></TABLE>
<!-- Start WWW validator - v2.0 -->
<P>
<A HREF="http://validator.w3.org/check/referer"><IMG border="0"
SRC="/valid-html401.png"
ALT="Valid HTML 4.01!" HEIGHT="31" WIDTH="88"></A>
</P>
<!-- End WWW validator - v2.0 -->
</BODY>
</HTML>