Allow a grace period before removal of unmaintained software that is known to be working

[awesome-selfhosted]

Allow a grace period before removal of unmaintained software that is known to be working

[nodiscc]

I agree that some projects (unmaintained but simple enough and still working, e.g awesome-selfhosted/awesome-selfhosted#4120) should benefit from a longer "grace period" during which the awesome-lint job does not list them in the unmaintained projects report.

This mechanism/"ignore list" should be implemented in https://github.com/nodiscc/hecat/. The question remains, of how we would expect the configuration of such an "ignore"/grace period to look like in the module configuration

I don't think we want to permanently add a project to this ignore list, since it would be good to be reminded to revisit them after a while. So a simple ignore_list: ['project1', 'project2', 'writing' ] might not do the trick.

It may be more appropriate to use a dictionary like

grace_periods: # do not issue warning or errors for projects listed here (source_code_url), until the specified date
  - url: https://github.com/josephernest/writing # working despite no updates, https://github.com/awesome-selfhosted/awesome-selfhosted-data/issues/72
    until: 2024-08-22
  - url: https://github.com/another/project
    until: 2023-12-31

Other ideas welcome

[Ki-er]

The grace period would be a better idea long term, hence so that they are checked upon and can be extended again if working and removed if not. The dictionary would be a good layout, and easy to contribute to as well.

I wonder if it is possible to put the dictionary in another file and refer to it, so that the list doesn't grow to be unwieldy.