We invite you to join the IOCCC Discord Community via this link: https://discord.gg/Wa42Qujwnw
We released mkiocccentry toolkit version 2.4.4 2025-03-15.
+While you are NOT required to use this release in order to submit to IOCCC28, +we do RECOMMEND that you install and use it, because among other things, it provides:
+See the version 2.4.4 release notes for more details.
+We released mkiocccentry toolkit version 2.4.3 2025-03-11.
While you are NOT required to use this release in order to submit to IOCCC28, we do RECOMMEND that you install and use it, because among other things, it provides:
@@ -444,11 +452,10 @@ we do RECOMMEND that you install and use it, bmkiocccentry -x will force the overwriting of the submission directory it forms under workdirmkiocccentry -U uuid and mkiocccentry -u uuid_file let you set your usernameSee the version 2.4.3 release notes -for more details.
+See the version 2.4.3 release notes for more details.
Clarification: NUL bytes are ALLOWED in your submission prog.c and related C code.
Please mention in your remarks.md file if your C source contains NUL bytes.
The 40th anniversary of the IOCCC, IOCCC28, will be open for submissions from 2025-03-05 23:19:17.131107 UTC to 2025-06-05 04:03:02.010099 UTC.
Version 28.30 2025-03-03 of the IOCCC28 rules, @@ -468,13 +475,13 @@ and initial password by email. If you cannot find that email, contact the IOCCC Judges by email for help. We have given early registrants extra time (until 2025 Mar 12 UTC), to login and change their initial password.
-We have reached our code freeze milestone for the mkiocccentry repo and released a new version of the mkiocccentry toolkit!
Final testing is going well. We remain on track to open the IOCCC28 on 2025-03-05 23:19:17.131107 UTC.
In a few days, those registered for IOCCC28 will receive email with their username and initial password to submit their code.
We encourage those who wish to enter the IOCCC28 to registered for IOCCC28 today.
Consider joining the IOCCC discord community via this link: https://discord.gg/Wa42Qujwnw
-We have discovered an issue that needs to be resolved, followed by more testing after the code freeze. We also want to improve the IOCCC28 guidelines, and to simplify the write-up of the IOCCC28 rules.
@@ -482,7 +489,7 @@ and to simplify the write-up of the IOCCC28 rules. on 2024-12-29 23:58:13.213455 UTC, is now scheduled to be open from 2025-03-05 23:19:17.131107 UTC to 2025-06-05 04:03:02.010099 UTC. We apologize for this delay. -IMPORTANT DISCORD UPDATE: Due to a Discord bug/mis-feature, those who joined the IOCCC Discord server recently lost their access soon afterwards and have to re-join. @@ -492,7 +499,7 @@ Fans of the IOCCC, hopeful IOCCC28 contestants, and past winner are all encouraged to stop by and say hello.
To join, click this link: https://discord.gg/Wa42Qujwnw.
-The IOCCC now has a Discord server!
Click the link to join the IOCCC Discord server.
Fans of the IOCCC, hopeful IOCCC28 contestants, and past winners of the IOCCC
@@ -508,14 +515,14 @@ on 2024-12-29 23:58:13.213455 UTC, is now scheduled to be
We have just released version 2.3 of the mkiocccentry repo.
This repo 2.3 release includes important improvements (over repo release 2.1) to the mkiocccentry(1) tool
as well as a critical fix for installing on BSD based systems.
Please download version 2.3 of the mkiocccentry repo, and compile the mkiocccentry tool set. You may also wish to install this code. See also the mkiocccentry FAQ for more information.
-The IOCCC Rule 13 no longer discourages the
use of UTF-8 in C source. Since the days of -std=gnu17 compilers,
UTF-8 characters do not impose a compiler problem. The related guideline
@@ -526,7 +533,7 @@ modifications as means to tell the submitter that their submission was received.
All of the import IOCCC dates within the IOCCC rules have been moved into the “Important IOCCC dates” section.
-After a 4 year effort by a number of people, with over 6168+ commits, the Great Fork Merge has been completed @@ -554,7 +561,7 @@ and status.json has been updated to reflect this new s
Proposed and tentative IOCCC rules and IOCCC guidelines have been released.
See FAQ Section 0 for more information on how to enter.
-We continue to make good progress on the temp-test-ioccc website via the temp-test-ioccc repo.
@@ -584,7 +591,7 @@ not having to look at them more than once on a whole, other than possible entries that have to be added at the end, like the example below.Once the submit server server is ready another FAQ will be added and that entry can be looked at alone.
-A number of issues from minor fixes have been applied to the temp-test-ioccc website via the temp-test-ioccc repo.
@@ -619,7 +626,7 @@ ask for beta testing of the new IOCCC registration process and 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.
-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 hamburger-style menu icon in place of
@@ -641,7 +648,7 @@ files that are static (not generated bin tools) report no
warnings, nor info** messages, changes involving fixing invalid
links to local files have been corrected, and changes involving the
topbar are now HTML 5 conforming.
Nearly all of the temp-test-ioccc website
website has undergone editorial review. Nearly all IOCCC winning entries
compile on modern systems and many have try.sh scripts to help you run them.
@@ -659,10 +666,10 @@ glaring “dancing bears” and other frivolous web features.
Stay tuned!
-We continue to make good progress on website. In the temp-test-ioccc GitHub repo we have made nearly 4600 changes to date!
All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the bin directory.
-We have been busy preparing for an important / significant update to this website. In the temp-test-ioccc GitHub repo we have made nearly 2645 changes to date.
While you are free to look at the temp-test-ioccc GitHub repo, please do not link to it as this repo and related website will disappear once the main @@ -718,7 +725,7 @@ that needs urgent fixing. The IOCCCMOCK will us to beta-test the new IOCCC process without putting the hard work of those who submit real IOCCC entries at risk.
Stay tuned!
-We added to the status.json page, a “status_date” JSON member whose value is the date @@ -730,7 +737,7 @@ a “latest_news” JSON member whose value is the date of the most recent news item.
"status_date" : "Mon Jan 30 02:28:44 PST 2023",
"latest_news" : "Mon Jan 30 02:28:44 PST 2023"As per the suggestion of Toni Mikkola (@Virtaava@home.social) we now maintain a status.json page on this website.
@@ -748,7 +755,7 @@ The details of such additional JSON members are TBD. Instead you will have to rely on the additional JSON information and/or read the IOCCC news, and/or follow us on Mastodon via @ioccc@fosstodon.org. -We are planning to abandon our IOCCC Twitter feed in favor of our new IOCCC Mastodon feed.
@@ -783,7 +790,7 @@ is made possible by volunteers, and those who voluntarily support the cost of their server.Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!
-Source code has been released for version 0.8.1 2022-11-19 of the mkiocccentry repo, a GitHub repo that includes the official iocccsize tool, @@ -795,13 +802,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.
We are working on complete rebuild of this website as well.
-Source code has been released for version 0.24 2022-01-15 of the mkiocccentry tool, 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).
-The Judges are continuing to work on re-tooling how we run the IOCCC. We are writing tools under various repositories our @@ -810,7 +817,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!
-The Judges are re-tooling how we run the IOCCC. Our goal is to build a smoother, more rapid process centered around diff --git a/news.md b/news.md index 5df2587bd..ff7fd0dd5 100644 --- a/news.md +++ b/news.md @@ -20,6 +20,18 @@ We invite you to join the **IOCCC Discord Community** via this link: [https://di +## 2025-03-15 + +We released [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry) **version 2.4.4 2025-03-15**. + +While you are **NOT** required to use this release in order to submit to **IOCCC28**, +we do **RECOMMEND** that you **install and use** it, because among other things, it provides: + +* Set locale to **C**, the **official locale** of the **IOCCC**. + +See the [version 2.4.4 release notes](https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.4) for more details. + + ## 2025-03-12 We released [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry) **version 2.4.3 2025-03-11**. @@ -32,8 +44,7 @@ we do **RECOMMEND** that you **install and use** it, because among other things, * `mkiocccentry -x` will force the overwriting of the submission directory it forms under `workdir` * `mkiocccentry -U uuid` and `mkiocccentry -u uuid_file` let you set your username -See the [version 2.4.3 release notes](https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.3) -for more details. +See the [version 2.4.3 release notes](https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.3) for more details. **Clarification**: **NUL bytes** are **ALLOWED** in your submission `prog.c` and related C code. diff --git a/next/guidelines.html b/next/guidelines.html index cc22853e2..48af7c740 100644 --- a/next/guidelines.html +++ b/next/guidelines.html @@ -464,7 +464,7 @@ writing by contacting the judges.
Yes Virginia, that is a hint!
+ +Jump to: top