This repository has been archived by the owner on Dec 30, 2024. It is now read-only.
forked from ioccc-src/winner
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add news event 2024-12-28 to the news
Announce the result of the **Great Fork Merge** and the IOCCC28 dates!
- Loading branch information
Showing
5 changed files
with
82 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -432,7 +432,33 @@ <h3 id="please-follow-the-ioccc-on-mastodon">Please follow the <a href="https:// | |
FAQ on “<a href="faq.html#try_mastodon">Mastodon</a>” | ||
for more information on Mastodon.</p> | ||
<h1 id="news">News</h1> | ||
<h2 id="section">2024-06-08</h2> | ||
<h2 id="section">2024-12-28</h2> | ||
<h3 id="good-news-everyone--">Good News Everyone! :-)</h3> | ||
<p>After a 4 year effort by a <a href="thanks-for-help.html">number of people</a>, | ||
with over 6168+ commits, the <strong>Great Fork Merge</strong> has been completed | ||
and the <a href="index.html">Official IOCCC web site</a> has been updated!</p> | ||
<p>A significant number of improvements has been made to the | ||
<a href="years.html">IOCCC winning entries</a>. | ||
A number of fixes and improvements involve the ability of reasonable modern | ||
Unix/Linux systems to be able to compile and even run them. | ||
See <a href="faq.html#compiling">FAQ Section 4</a> for | ||
information on how to compile. | ||
See the <a href="faq.html#changes">FAQ Section 8</a> | ||
for details on changes made to the entries.</p> | ||
<p>We hope you enjoy the new and improved | ||
<a href="index.html">Official IOCCC web site</a>. | ||
This web site is backed by the | ||
<a href="https://github.com/ioccc-src/winner">IOCCC winner repo</a>. | ||
See <a href="faq.html#help">FAQ Section 9</a> for | ||
how you help <a href="faq.html#fix_website">improve / fix the we site</a>, | ||
or fix <a href="bugs.html">known bugs in IOCCC winning entries</a>.</p> | ||
<h3 id="ioccc28-is-starting">IOCCC28 is starting!</h3> | ||
<p>The IOCCC28, the <a href="faq.html#ioccc_start">40th anniversary of the IOCCC</a> is now | ||
scheduled to run from <strong>2024-12-29 23:58:13.213455 UTC</strong> to <strong>2025-04-01 23:29:31.374143 UTC</strong>!!!.</p> | ||
<p>Proposed and tentative <a href="next/rules.html">IOCCC rules</a> and <a href="next/guidelines.html">IOCCC guidelines</a> | ||
have been released.</p> | ||
<p>See <a href="faq.html#enter_questions">FAQ Section 0</a> for more information on how to enter.</p> | ||
<h2 id="section-1">2024-06-08</h2> | ||
<p>We continue to make good progress on the | ||
<a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a> | ||
via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p> | ||
|
@@ -462,7 +488,7 @@ <h2 id="section">2024-06-08</h2> | |
entries that have to be added at the end, like the example below.</p> | ||
<p>Once the <em>submit server</em> server is ready another FAQ will be added and that | ||
entry can be looked at alone.</p> | ||
<h2 id="section-1">2024-05-30</h2> | ||
<h2 id="section-2">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 website</a> | ||
via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p> | ||
|
@@ -497,7 +523,7 @@ <h2 id="section-1">2024-05-30</h2> | |
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-2">2024-04-30</h2> | ||
<h2 id="section-3">2024-04-30</h2> | ||
<p>The website 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 | ||
|
@@ -519,7 +545,7 @@ <h2 id="section-2">2024-04-30</h2> | |
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-3">2024-04-20</h2> | ||
<h2 id="section-4">2024-04-20</h2> | ||
<p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a> | ||
website 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. | ||
|
@@ -537,10 +563,10 @@ <h2 id="section-3">2024-04-20</h2> | |
where the contents of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a> | ||
will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC website</a>.</p> | ||
<p>Stay tuned!</p> | ||
<h2 id="section-4">2024-02-29</h2> | ||
<h2 id="section-5">2024-02-29</h2> | ||
<p>We continue to make good progress on website. 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-5">2023-05-22</h2> | ||
<h2 id="section-6">2023-05-22</h2> | ||
<p>We have been busy preparing for an important / significant update to this website. 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 website will disappear once the main | ||
|
@@ -596,7 +622,7 @@ <h2 id="section-5">2023-05-22</h2> | |
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-6">2023-01-30</h2> | ||
<h2 id="section-7">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 | ||
|
@@ -608,7 +634,7 @@ <h2 id="section-6">2023-01-30</h2> | |
of the most recent news item.</p> | ||
<pre><code> "status_date" : "Mon Jan 30 02:28:44 PST 2023", | ||
"latest_news" : "Mon Jan 30 02:28:44 PST 2023"</code></pre> | ||
<h2 id="section-7">2022-12-18</h2> | ||
<h2 id="section-8">2022-12-18</h2> | ||
<p>As per the suggestion of <a href="https://fosstodon.org/@[email protected]">Toni Mikkola | ||
(<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social&rpar">@home.social&rpar</span>;</a> | ||
we now maintain a <a href="status.json">status.json</a> page on this website.</p> | ||
|
@@ -626,7 +652,7 @@ <h2 id="section-7">2022-12-18</h2> | |
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-8">2022-11-29</h2> | ||
<h2 id="section-9">2022-11-29</h2> | ||
<p>We are planning 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> | ||
|
@@ -661,7 +687,7 @@ <h2 id="section-8">2022-11-29</h2> | |
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-9">2022-11-19</h2> | ||
<h2 id="section-10">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, | ||
|
@@ -673,13 +699,13 @@ <h2 id="section-9">2022-11-19</h2> | |
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 website as well.</p> | ||
<h2 id="section-10">2022-01-15</h2> | ||
<h2 id="section-11">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-11">2021-12-27</h2> | ||
<h2 id="section-12">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 | ||
|
@@ -688,7 +714,7 @@ <h2 id="section-11">2021-12-27</h2> | |
Sorry for the delay, but we think you will appreciate the re-tooling | ||
when it is completed. | ||
Stay tuned!</p> | ||
<h2 id="section-12">2021-10-21</h2> | ||
<h2 id="section-13">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 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters