From f612e3527bacdfc39f31ed85c7b775d091c05773 Mon Sep 17 00:00:00 2001
From: Landon Curt Noll <github-mail@asthe.com>
Date: Mon, 22 May 2023 13:49:39 -0700
Subject: [PATCH] add news of Mon May 22 13:26:56 PDT 2023

---
 index.html  | 78 ++++++++++++++++++++++++++++++++++++++++++++++++++++-
 status.json |  3 ++-
 2 files changed, 79 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index f04f45bfb..e97c728fb 100644
--- a/index.html
+++ b/index.html
@@ -69,6 +69,82 @@ 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>
@@ -101,7 +177,7 @@ Mikkola</A> (<I>@Virtaava@home.social</I>) we now maintain a
 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, 
+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>
diff --git a/status.json b/status.json
index 42bf8aa51..4901fa1a8 100644
--- a/status.json
+++ b/status.json
@@ -1,6 +1,7 @@
 {
     "no_comment" : "mandatory comment: because comments were removed from the original JSON spec",
+    "IOCCC_status_version" : "0.2 2023-05-22",
     "contest" : "closed",
     "status_date" : "Mon Jan 30 02:28:44 PST 2023",
-    "latest_news" : "Mon Jan 30 02:28:44 PST 2023"
+    "latest_news" : "Mon May 22 13:26:56 PDT 2023"
 }