Remove some completed items from todo file
This commit is contained in:
Cody Boone Ferguson committed
1 parent
7442da4341
commit
baa03fb274
1 file changed
+5
-68
+5
-68
@@ -1,5 +1,5 @@
|
||||
# A todo list of known things to check and/or do
|
||||
*Last updated: Tue 12 Dec 2023 14:00:37 UTC*
|
||||
*Last updated: Sat 23 Dec 2023 13:22:40 UTC*
|
||||
|
||||
This document is primarily for [Cody Boone
|
||||
Ferguson](/winners.html#Cody_Boone_Ferguson) as he (that is I :-) ) wanted a way
|
||||
@@ -14,29 +14,14 @@ It is hoped that this will be referenced and updated as this is an easy way to
|
||||
keep track of things that have been done already and what hasn't been done (in
|
||||
this file the case is mostly _NOT_ been done).
|
||||
|
||||
- Find entries with bugs as well INABIAF and add to [bugs.md](/bugs.md).
|
||||
As far as I am aware the ones that have not been checked are > 2011 (and two
|
||||
entries in 2011, vik and zucker) and possibly some of the earlier years. I
|
||||
([Cody Boone Ferguson](https://www.ioccc.org/winners.html#Cody_Boone_Ferguson)) have spent too
|
||||
much time when working on formatting the README.md files on finding problems
|
||||
out (and in some cases fixing or trying but not yet succeeding to fix an
|
||||
entry); if I did not do that I would be done with fixing the README.md files
|
||||
(format wise and mostly typos too). Of course when working on finding bugs
|
||||
it might necessitate updating the README.md file but that can be done at
|
||||
that time. I might or might not end up following this idea but I probably
|
||||
should so this needs to be noted.
|
||||
|
||||
- Resolve as many of the issues in [bugs.md](/bugs.md) with the exception of the
|
||||
INABIAF ones. This is likely not possible for all (one in particular comes to
|
||||
mind that abuses a bug in a now very old gcc version - this obviously cannot be
|
||||
fixed but I added an alt version that does what it used to do so it's fine) but
|
||||
many certainly can be - and actually most have been - fixed.
|
||||
|
||||
- Format fix remaining README.md files. As of **16 October 2023** the entries of
|
||||
years through 2013 and up through 2014/endoh1 have been checked. As for the
|
||||
`YYYY/README.md` files years up through 2001 have had a first pass but some
|
||||
things have to be done in those years. These things, such as dealing with old
|
||||
email addresses and such, can likely be done with the typo pass (see below).
|
||||
many certainly can be - and actually most have been - fixed. Another one crashes
|
||||
in macOS but this is almost certainly because of the version of perl installed.
|
||||
Another one crashes in macOS but this is almost certainly because of
|
||||
`mmap(2)`/JIT code with the Apple silicon chip etc.
|
||||
|
||||
- Typo fix ALL markdown files. For the README.md files years 1984-1989 have been
|
||||
done (along with the format fixes) except that YYYY/README.md files have not
|
||||
@@ -49,46 +34,6 @@ namely to do with email addresses that no longer exist. At this point it is not
|
||||
determined if this will be done with the typo pass (what should be the final
|
||||
pass) or not but it's very possible that it can be just to speed things along.
|
||||
|
||||
- Verify which README.md files have not been checked for correct formatting and
|
||||
fix any issues found.
|
||||
* This includes author information: not only at first column but making sure
|
||||
that the lines end with `\` so that the rendered output does not end up
|
||||
on one line only. Note that earlier spaces were being added to the end of
|
||||
the line but after discussion on GitHub it was decided it is preferable to
|
||||
have `\` instead.
|
||||
NOTE that this has been done already BUT it was not done manually so
|
||||
there are some lines that should not end in `\` including some in code
|
||||
blocks.
|
||||
* [Cody Boone
|
||||
Ferguson](https://www.ioccc.org/winners.html#Cody_Boone_Ferguson) has done
|
||||
many and has some kind of record of what he's done but these can be added
|
||||
later by having a list of years to check. However, as noted on 06 July 2023,
|
||||
all years will have to be checked again so this might not be as important
|
||||
except that the years not checked / fixed should only need one pass (but
|
||||
probably will have a second pass anyway just to make sure things are good as
|
||||
seeing things a second time is a good way to find additional errors).
|
||||
* NOTE that as of some days ago (today being 02 November 2023) the years
|
||||
1984-1989 have been checked for formatting and other issues including typos.
|
||||
Whether a quick final pass will be made is not determined yet.
|
||||
|
||||
- Remove addresses from older winning entries but (if known) keep country code
|
||||
and if known add it and the name to the respective JSON file in the
|
||||
[author](/author) subdirectory. As of half past 4 Pacific time on 22 April 2023
|
||||
only the years through 1986 have been done entirely. This should not take much
|
||||
time but I (Cody) am bored with it for now and would rather do other more
|
||||
important things. This will likely not be updated until after it's done (and
|
||||
when I remember to remove it - I expect that when I go for it I'll do it in one
|
||||
sitting or maybe a few sittings with a few brief breaks).
|
||||
|
||||
- NOTE: do this AFTER everything else is done! Verify that
|
||||
[2004/gavin](2004/gavin/)'s [img/fs.tar](2004/gavin/img/fs.tar) contains the
|
||||
same version of files as under [2004/gavin](2004/gavin/) itself. This should be
|
||||
verifiable by extracting the tarball in the entry's [img/](img/) subdirectory
|
||||
and then typing the below from the entry's main directory
|
||||
([2004/gavin](2004/gavin)), making sure no output is displayed:
|
||||
|
||||
diff -r . img/fs|grep -v 'Only in'
|
||||
|
||||
- Check all Makefiles for notes / warnings on compilation and see if they can be
|
||||
copied to _after_ the compilation as they're more likely to be seen this way. In
|
||||
some cases this will have to be done in the Makefile via `|| :` (that might be
|
||||
@@ -129,14 +74,6 @@ there.
|
||||
sure.
|
||||
|
||||
|
||||
- Remove WHERE CORRECT the references to those who fixed or provided alt code in
|
||||
entries in the respective README.md files. This cannot be done without examining
|
||||
each because some names are mentioned by the author. For instance I (Cody) can
|
||||
think of at least three where I have been mentioned explicitly by the author:
|
||||
one in 2018, one in 2019 and one in 2020.
|
||||
* NOTE: this _appears_ to be done as of some time back from this writing (02
|
||||
November 2023). This is being verified as each README.md file is checked.
|
||||
|
||||
- For the YYYY/README.md files where it refers to emailing the judges fixes
|
||||
instead change it to make pull requests. See the
|
||||
[1995/README.md](1995/README.md) file for example.
|
||||
|
||||
Reference in new issue
Block a user