Update todo file

Removed an item that I already finished.

Merge two items that were related.

Added an item (does that mean I didn't remove an item?) for
2018/ferguson that has to be done after the other tasks are done and on
specific systems (was done for personal reasons at submission but since
the judges referred to it in their remarks I have kept it and will
continue to keep it).
This commit is contained in:
Cody Boone Ferguson committed 2024-01-31 06:02:39 -08:00
1 parent 55ca7f433f
commit c30387cce5
1 file changed
+23 -25
+23 -25
View File
@@ -1,30 +1,28 @@
# A todo list of known things to check and/or do
*Last updated: Thu 11 Jan 2024 16:42:28 UTC*
*Last updated: Wed 31 Jan 2024 12:22:09 UTC*
This document is primarily for [Cody Boone
Ferguson](/winners.html#Cody_Boone_Ferguson) as he (that is I :-) ) wanted a way
to keep track of things in a way that did not require the information getting
lost in the thousands of changes in the repo and because it might be too much to
add to the todo list in the issues themselves.
This document is for [Cody Boone Ferguson](/winners.html#Cody_Boone_Ferguson) as
he (that is I :-) ) wanted a way to keep track of things in a way that did not
require the information getting lost in the thousands of changes in the repo and
because it might be too much to add to the todo list in the issues themselves.
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
done (many times it's thought that a task was done only to find out it wasn't).
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).
Every so often this file is checked and updated to remove items and when
something needs to be done is thought of it is also updated unless it can be
done right then and there or it seems more appropriate to add to the issue (#3)
todo list.
- Typo fix ALL markdown files. For the README.md files the entries have all been
done (along with format fixes) but the YYYY/README.md files have not been
completed. See below item for details on that (several items in this file refer
to those).
- Go through all year README.md files: that is 1984/README.md, 1985/README.md and
so on. As of **Mon 16 Oct 11:22:52 UTC 2023** the following years have had a
first pass: 1984 through 2001. However there are changes that are required
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.
completed.
* Go through all year README.md files: that is 1984/README.md,
1985/README.md and so on. As of **Mon 16 Oct 11:22:52 UTC 2023** the
following years have had a first pass: 1984 through 2001. However there are
changes that might be required in those years too so a pass over all of them
will have to be done at the time the files are to be reviewed.
- Check the [GitHub issue #3 comment
1615962832](https://github.com/ioccc-src/temp-test-ioccc/issues/3#issuecomment-1615962832)
@@ -38,13 +36,13 @@ embedded into the README.md files themselves. An entry that the video file is
downloaded already is 2006/sykes1. There are others that I need to look at once
the rest of the entries are done, assuming that it's possible.
- Although I will have to do this when another issue is opened up I am aware of
some issues in 2020/ferguson1/.winner.json. I do not want to forget this,
however, so I am noting it here. A reference to a file in 2020/ferguson2 is in
1992/buzzard.2. This type of thing will have to be checked for all entries in
the new issue.
- Verify that all entries that should have (or could be benefited by) a try
script do in fact have one. Also verify (mostly in earlier years) consistency in
the way it is displayed and interactivity. The later years are probably done
better.
better. As of *Wed 31 Jan 2024 12:22:09 UTC* almost all of this is done: just
some of 2018 and then all of 2019 and 2020 have to be checked. It is very likely
that before the day is over 2018 will be done and possibly part of 2019 will be
done but this is currently unknown. The shellcheck updates is another issue
entirely.
- Test and fix as and if necessary 2018/ferguson/weasel.spec.