Topic: Documenting support lifecycles of open source projects.
While the project itself is https://github.com/endoflife-date/endoflife.date/, I don’t think I can cover a lot about the project in a 10 minute talk. Instead I’d like to cover the release recommendations that we provide to projects.
If your open-source project makes consistent releases, and offers some sort of support lifecycle (say last 2 major releases are supported, or you support only the latest Python release) - documenting these becomes extremely important, especially for the folks responsible for using your project securely.
The talk will cover best practices around documenting your release cadence, processes, EOL dates, versioning schemes, and various gotchas. There will be lots of examples to showcase what is good vs bad (and why).
The talk comes out of my experience of creating endoflife.date as an open-source community project, and documenting the lifecycles and EOL dates of more than 100 products.