diff --git a/index.html b/index.html new file mode 100644 index 000000000..bbf03aed1 --- /dev/null +++ b/index.html @@ -0,0 +1,371 @@ + + +
+ + + + + +
+
+Please visit +www.ioccc.org +for the official IOCCC web. +
+Please do NOT bookmark nor link to this +experimental web site: +
+https://ioccc-src.github.io/temp-test-ioccc/ ++
+When this experiment is finished, this site will go away! +
+This test web tree is part of the +temp-test-ioccc GitHub repo: +
+https://github.com/ioccc-src/temp-test-ioccc ++
+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 +temp-test-ioccc GitHub repo. +
[ The judges |
+IOCCC home page |
+How to enter |
+FAQ |
+Contacting the IOCCC
+
+IOCCC news |
+People who have won |
+Winning entries ]
The source winners of the 27th IOCCC have been released. Congratulations!
+ +The IOCCC is currently CLOSED.
+ +Right now, you CANNOT register as a contestant with the IOCCC,
+nor can you submit an entry because the IOCCC is yet NOT open.
+
+
Please see the watch the IOCCC news below for information on the next IOCCC. + +
You may also check on the status.json for the current status of the IOCCC. + + +
+
+We also added to the +status.json page, +a "latest_news" JSON member whose value is the date +of the most recent news item. +
+For example: +
++ "status_date" : "Mon Jan 30 02:28:44 PST 2023", + "latest_news" : "Mon Jan 30 02:28:44 PST 2023" +
+In addition to the IOCCC-style easter egg, you may count on +the JSON status page having a JSON member with name of "contest" +that will have a value of either "closed" or "open". +When a future IOCCC is announced or the IOCCC is currently open, +the JSON member with name of "contest" will change from +"closed" to "open". +
+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 TBD. +
+When an open IOCCC closes, we won't instantaneously update the +status.json page. +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. +
+Our Mastodon username is: @ioccc@fosstodon.org. +
+Please note: As of the date of this posting, our account was just setup, +so there isn't much to read there, yet. ++
+In the future we plan to use Mastodon as our official announcement platform. +This will include announcing: +
+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 NOT required to enter the IOCCC, but nevertheless is encouraged. +Proving a Mastodon username will be entirely optional. +
+Non-mastodon users can follow the IOCCC postings via: +fosstodon.org/@ioccc. +
+If you do not yet have a Mastodon account, you may obtain a free mastodon account via: +joinmastodon.org. +
+If you do have / obtain a Mastodon account, please do us a favor and +follow the IOCCC at: +
+@ioccc@fosstodon.org ++The IOCCC wishes to thank the good folk running the +fosstodon.org +Mastodon hub. +Their technology focused +Fosstodon Hub +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! +
+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. +
+Once we reach version 1.0, we plan to invite the public to test and comment. +
+We plan to hold in 2023, what we will call IOCCCMOCK, 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. +
+We are working on complete rebuild of this web site as well. +
+We plan to hold IOCCC28 in 2023. +Sorry for the delay, but we think you will appreciate the re-tooling +when it is completed. +Stay tuned! +
+For example, when we announce the winners, +we will do so by committing their code to the +Winning entries +of the IOCCC repo, so that people will be able immediately +view the winning source. +
+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, +we plan to hold IOCCC28 in 2023 instead of 2021. +Sorry for the delay, but we think you will appreciate the re-tooling +when it is completed. +
+Stay tuned for how you may be able to help in the IOCCC redesign for IOCCC28! +
Older news has been archived, but is not currently available
+ +![]() |
+© Copyright 1984-2020,
+Leo Broukhis, Simon Cooper, Landon Curt Noll
+- All rights reserved |
++ |