Update todo.md - add entries, modify others

todo.md

@@ -1,5 +1,5 @@
 # A todo list of known things to check and/or do
-*Last updated: Wed 31 May 2023 09:52:55 UTC*
+*Last updated: Thu  6 Jul 2023 11:24:42 UTC*
 
 More things will likely be added over time and as items are done they _should
 be_ removed from the list IF AND ONLY IF (!!) we are _absolutely certain_ it is
@@ -30,6 +30,14 @@ fixed) but many certainly can be (and have been) fixed.
 - Check for typos in README.md files. Most years have been done. I (Cody) need
 to check the late 80s through mid 1990s plus the last two entries in 2011 and
 the following years. At the same time the formatting is being fixed.
+    * UPDATE on 06 July 2023: some while back I noticed that _ALL_ years will
+    have to be checked again but most of the years checked through 2011 (I think
+    it is but I have this vague memory I did a couple more years - that will be
+    checked when I return to this item) can be checked more quickly.
+    * UPDATE on 06 July 2023: see below list under the item _Verify which
+    README.md files have not been checked for correct formatting_ as well.
+    * UPDATE on 06 July 2023: note that this does NOT include the
+    `YYYY/README.md` files! See the below item for that.
 
 - Go through all year README.md files that is 1984/README.md, 1985/README.md and
 so on. As of *Sun 30 Apr 2023 13:45:52 UTC* the following years have been
@@ -38,15 +46,22 @@ finished: 1984, 1985, 1986, 2004, 2005.
 - Verify which README.md files have not been checked for correct formatting and
 fix any issues.
     * This includes author information: not only at first column but making sure
-    that the lines end with spaces so that the rendered output does not end up
+    that the lines end with `<br>` so that the rendered output does not end up
-    on one line only.
+    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 `<br>` instead.
     * [Cody Boone Ferguson](/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.
+    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: as of 03 May 2023 years up through most of 2011 have been checked
     except that a few years I am pretty sure I did not check typos (I'd say about
-    1987 or 1988 through 1995 should be rechecked for typos).  It's very likely
+    1987 or 1988 through 1995 should be rechecked for typos) (but see above item
-    I won't keep this updated until it's finished but I wanted to note it now.
+    in this list). It's very likely I won't keep this updated until it's
+    finished but I wanted to note it now.
     * NOTE: a while back (as of 31 May 2023) Cody noticed that some of the files
     he already checked could be improved wrt formatting so he'll have to have a
     quick look at the previously edited files; some he has done already but the
@@ -55,17 +70,19 @@ fix any issues.
     (presumably with complete changes made :-) ).
 
 - Remove addresses from older winning entries but (if known) keep country code +
-add country code to winners.csv. As of half past 4 Pacific time on 22 April 2023
+add country code and name to the respective JSON file in the [author](/author)
-only the years through 1986 have been done entirely. This should not take much
+subdirectory. As of half past 4 Pacific time on 22 April 2023 only the years
-time but I (Cody) am bored with it for now and would rather do other more
+through 1986 have been done entirely. This should not take much time but I
-important things.  This will likely not be updated until after it's done (and
+(Cody) am bored with it for now and would rather do other more important things.
-when I remember to remove it - I expect that when I go for it I'll do it in one
+This will likely not be updated until after it's done (and when I remember to
-sitting or maybe a few sittings with a few brief breaks).
+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).
 
-- Verify that [2004/gavin](2004/gavin/)'s [img/fs.tar](2004/gavin/img/fs.tar)
+- NOTE: do this AFTER everything else is done! Verify that
-contains the same version of files as under [2004/gavin](2004/gavin/) itself.
+[2004/gavin](2004/gavin/)'s [img/fs.tar](2004/gavin/img/fs.tar) contains the
-This should be verifiable by extracting the tarball in the entry's [img/](img/)
+same version of files as under [2004/gavin](2004/gavin/) itself.  This should be
-subdirectory and then typing the below from the entry's main directory
+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'
@@ -75,7 +92,7 @@ even more like its original form. I have some ideas here but it might involve
 some discussion too. See 22 May 2023 commits for the improvements already made.
 
 - Check all Makefiles for notes / warnings on compilation and see if they can be
-moved to _after_ the compilation as they're more likely to be seen this way. In
+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
 good to have in the Makefiles anyway so that additional rules / targets are
 run) or else they'll have to be put above the compilation.
@@ -84,5 +101,10 @@ run) or else they'll have to be put above the compilation.
     important use of this is that some entries won't compile with clang due to
     defects but the alternate version will. Whether this is a good idea is TBD
     but it's noted here as a reminder to be discussed.
+    * Update on 06 July 2023: note that in some cases the `|| :` _**CANNOT**_ be
+    added to the rule because the following rules require that the previous
+    rules run successfully.
 
-
+- Check the [GitHub issue #3 comment
+1615962832](https://github.com/ioccc-src/temp-test-ioccc/issues/3#issuecomment-1615962832)
+for links about the todo items wrt the [FAQ](/faq.md).