systematic checks

[pachadotdev]

Hi @wibeasley !

I had a hard week and I'm checking the task view now, please feel free to check this in forthcoming days.

So far, my method to keep the list of pkgs in good shape is:

1. Use ctv to inspect the file
2. Check for any package removed from CRAN
3. If the package is on GH, link to it, but 1st email the author and ask about the pkg continuity
4. If the GH repo is maintained, push changes pointing to a GH link
5. If the GH repo is abandoned (+1 yr without changes or follow ups on issues), then I remove the pkg from the list
6. 1-5 go to a log where I manually annotate the changes and the reason why I made the change

Do you have any other ideas in mind? This is a process that I don't want to automate, the communication with authors is key.

[wibeasley]

thanks for the reminder about 6. I'll add some stuff from our recent additions & modifications.