add news for 2024-05-30

This commit is contained in:
Landon Curt Noll committed 2024-05-30 13:48:15 -07:00
1 parent 21793c1ab2
commit 650849b523
2 files changed
+82 -11

No files matched your search

+42 -11
View File
@@ -388,7 +388,38 @@
major events such as the opening of a new IOCCC, or who won.</p>
<p>See “<a href="faq.html#try_mastodon">FAQ 6.12: What is Mastodon and why does IOCCC use it?</a>” for more
information on Mastodon.</p>
<h2 id="section">2024-04-30</h2>
<h2 id="section">2024-05-30</h2>
<p>A number of issues from minor fixes have been applied to the
<a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web site</a>
via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
<p>437 commits have been applied since 2024-04-20, bringing the total
number to 5260 commits to date. The
<a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a>
repo is now 5159 commits ahead of the [IOCCC
winner[(https://github.com/ioccc-src/winner) repo.</p>
<p>Multiple <strong>((top priority))</strong> issues have been resolved or completed.
Only one <strong>((top priority))</strong> <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/2006">issue
2006</a>
remains before we begin the final steps to perform the <strong>Great Fork
Merge</strong> when the <a href="https://www.ioccc.org/index.html">Official IOCCC web
site</a> will be updated.</p>
<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/2239">issue 2239</a>
TODO list has 10 out of 51 sub-tasks completed. That might not
seem like much progress, but keep in mind that some of those 10
tasks look many months and thousands of commits to complete.
Moreover, most of the remaining 41 TODO items are short “checkbox”
tasks. The final 31 TODO items are planned to be completed in about
a single day.</p>
<p>The <strong>IOCCC Submit server</strong> is in active development. We plan to
update the FAQ with screenshots from the IOCCC Submit server as
well as the <strong>IOCCC registration process</strong> prior to starting the
<strong>Great Fork Merge</strong>.</p>
<p>We have decided to not hold an <strong>IOCCC mock</strong> content, but instead
ask for beta testing of the new <strong>IOCCC registration process</strong> and
<strong>IOCCC Submit server</strong> when the have left alpha testing phase.
This will speed up the start date of IOCCC28.</p>
<p>It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the IOCCC.</p>
<h2 id="section-1">2024-04-30</h2>
<p>The web site now is viewing by mobile devices such as cell phones
and tablets. Devices with a screen resolution 1024 pixels and
narrower are given a <em>hamburger-style</em> menu icon in place of
@@ -410,7 +441,7 @@ files that are static (not generated <code>bin</code> tools) report </strong>no
warnings, nor info** messages, changes involving fixing invalid
links to local files have been corrected, and changes involving the
<em>topbar</em> are now HTML 5 conforming.</p>
<h2 id="section-1">2024-04-20</h2>
<h2 id="section-2">2024-04-20</h2>
<p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web site</a>
web site has undergone editorial review. Nearly all <a href="years.html">IOCCC winning entries</a>
compile on modern systems and many have <code>try.sh</code> scripts to help you run them.
@@ -428,10 +459,10 @@ glaring “<em>dancing bears</em>” and other frivolous web features.</p>
where the contents of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web site</a>
will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC web site</a>.</p>
<p>Stay tuned!</p>
<h2 id="section-2">2024-02-29</h2>
<h2 id="section-3">2024-02-29</h2>
<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>
<h2 id="section-3">2023-05-22</h2>
<h2 id="section-4">2023-05-22</h2>
<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>
<p>While you are free to look at the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a>,
please <strong>do not link to it</strong> as this repo and related web site will disappear once the main
@@ -487,7 +518,7 @@ that needs urgent fixing.
The <strong>IOCCCMOCK</strong> will us to beta-test the new IOCCC process without putting the hard work of those
who submit real IOCCC entries at risk.</p>
<p>Stay tuned!</p>
<h2 id="section-4">2023-01-30</h2>
<h2 id="section-5">2023-01-30</h2>
<p>We added to the
<a href="status.json">status.json</a> page,
a <em>“status_date”</em> JSON member whose value is the date
@@ -499,7 +530,7 @@ a <em>“latest_news”</em> JSON member whose value is the date
of the most recent news item.</p>
<pre><code> &quot;status_date&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;,
&quot;latest_news&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;</code></pre>
<h2 id="section-5">2022-12-18</h2>
<h2 id="section-6">2022-12-18</h2>
<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>
@@ -517,7 +548,7 @@ The details of such additional JSON members are <em>TBD</em>.</p>
Instead you will have to rely on the additional JSON information
and/or read the <a href="#news">IOCCC news</a>,
and/or follow us on Mastodon via <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
<h2 id="section-6">2022-11-29</h2>
<h2 id="section-7">2022-11-29</h2>
<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>
@@ -552,7 +583,7 @@ is made possible by volunteers,
and those who voluntarily
<a href="https://hub.fosstodon.org/support/">support</a> the cost of their server.</p>
<p>Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!</p>
<h2 id="section-7">2022-11-19</h2>
<h2 id="section-8">2022-11-19</h2>
<p>Source code has been released for version <strong>0.8.1 2022-11-19</strong> of the
<a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>,
a GitHub repo that includes the official iocccsize tool,
@@ -564,13 +595,13 @@ to upload the above mentioned compressed tarball: when the contest is open of co
judges will go through the motions (without judging the content) of an IOCCC:
testing the above mentioned tools and testing the submit server.</p>
<p>We are working on complete rebuild of this web site as well.</p>
<h2 id="section-8">2022-01-15</h2>
<h2 id="section-9">2022-01-15</h2>
<p>Source code has been released for version <strong>0.24 2022-01-15</strong> of the
<a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</a>,
a tool that is based on, and is containing, the official iocccsize tool,
will form a compressed tarball that a registered IOCCC contestant
will upload to the submit server (when the contest is open of course).</p>
<h2 id="section-9">2021-12-27</h2>
<h2 id="section-10">2021-12-27</h2>
<p><a href="judges.html">The Judges</a>
are continuing to work on re-tooling how we run the IOCCC.
We are writing tools under various repositories our
@@ -579,7 +610,7 @@ We are writing tools under various repositories our
Sorry for the delay, but we think you will appreciate the re-tooling
when it is completed.
Stay tuned!</p>
<h2 id="section-10">2021-10-21</h2>
<h2 id="section-11">2021-10-21</h2>
<p><a href="judges.html">The Judges</a>
are re-tooling how we run the IOCCC.
Our goal is to build a smoother, more rapid process centered around
+40
View File
@@ -9,6 +9,46 @@ See "[FAQ 6.12: What is Mastodon and why does IOCCC use it?](faq.html#try_mastod
information on Mastodon.
## 2024-05-30
A number of issues from minor fixes have been applied to the
[temp-test-ioccc web site](https://ioccc-src.github.io/temp-test-ioccc/)
via the [temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc) repo.
437 commits have been applied since 2024-04-20, bringing the total
number to 5260 commits to date. The
[temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc)
repo is now 5159 commits ahead of the [IOCCC
winner[(https://github.com/ioccc-src/winner) repo.
Multiple **((top priority))** issues have been resolved or completed.
Only one **((top priority))** [issue
2006](https://github.com/ioccc-src/temp-test-ioccc/issues/2006)
remains before we begin the final steps to perform the **Great Fork
Merge** when the [Official IOCCC web
site](https://www.ioccc.org/index.html) will be updated.
The [issue 2239](https://github.com/ioccc-src/temp-test-ioccc/issues/2239)
TODO list has 10 out of 51 sub-tasks completed. That might not
seem like much progress, but keep in mind that some of those 10
tasks look many months and thousands of commits to complete.
Moreover, most of the remaining 41 TODO items are short "checkbox"
tasks. The final 31 TODO items are planned to be completed in about
a single day.
The **IOCCC Submit server** is in active development. We plan to
update the FAQ with screenshots from the IOCCC Submit server as
well as the **IOCCC registration process** prior to starting the
**Great Fork Merge**.
We have decided to not hold an **IOCCC mock** content, but instead
ask for beta testing of the new **IOCCC registration process** and
**IOCCC Submit server** when the have left alpha testing phase.
This will speed up the start date of IOCCC28.
It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the IOCCC.
## 2024-04-30
The web site now is viewing by mobile devices such as cell phones