Create SD Critical Deadlines Calendar (e.g. EOL dates)

[eloquence]

Copied from internal issue by @deeplow, original issue dated 2025-03-19

I sometimes find it hard to know who's keeping track of EOLs and other time committments we've made. It would be good if to have at least a shared calendar we could add this information to, so that when we notice a critical deadline.

Examples of critical deadlines:

• Server EOL
• Client templates EOL
• Qubes EOL
• sd-log removal (mid-April 2025)
• ...

Additionally, it would be useful to know who is responsible for each EOL monitoring or if we can delegate this to automation, but being able to see these and alerted for in a calendar would already be a good step.

[eloquence]

I would suggest this approach:

• Define EOLs we care about in a YAML file in this repository
• Stretch goal: Consume endoflife.date feeds like https://endoflife.date/api/v1/products/fedora/ where appropriate
• Use said YAML & source data to generate and commit an ICS file via GitHub Action, which people can subscribe to individually
• Stretch goal: Also use YAML & GHA to open GitHub issues at a configured time (if we're already tracking it, no harm - can just close).

Thoughts/opinions?

[eloquence]

@mig5 You might have thoughts on this one since I know infra is already tracking some EOLs, and I'm sure you're routinely dealing with this problem in other contexts as well.

[mig5]

@eloquence indeed I am looking at consuming the endoflife.date API at another organisation at the moment for a similar goal.

If you are after an even shorter-term solution than the ones you've suggested, the SD team could consider adding entries to the software-eol.yaml file in fpf-www-projects repo

Doing so will immediately mean those items are tracked via Icinga checks and will alert, at least, the infra team as the EOL dates approach (within 90 days it will enter 'warning' state, and 30 days it enters 'critical' state - see the test script ).

[eloquence]

Thanks, Mig - getting that quick win seems worth it. We're already tracking Debian, and don't know the Whonix/Qubes EOLs yet (Whonix-on-Qubes-4.2 will have a very short lifeline once Qubes 4.3 is out per https://www.whonix.org/wiki/About#Qubes_Hosts), so I've opened a PR to add Fedora and Ubuntu there for now.

[eloquence]

Working on the checker code in #24 (much of it initially LLM-generated via ChatGPT o3 in in this case, but using our "new Tor issues" workflow as a model; poking/testing everything as I go). Early comments welcome.