Project Roadmap

[captn3m0]

This issue documents the long-term thought process behind the endoflife.date project. All of the items in the roadmap are good places to contribute, but might need some experimentation and discussion. If you are interested in working on one of these, please create a new issue, or comment on the existing one which should be linked below.

Theme: Community

1. Get more contributors, make it easier for users to make contributions, especially for new projects
2. Document the project better, especially around the release-data project, to allow new contributors to easily write new scrapers.
3. Have a community townhall once a month to discuss issues, product requests, EOL ecosystem, our analytics, website updates, and maybe finances/governance.
4. Document processes for maintainers.
5. Have a style-guide to enforce a clear and consistent tone across the website.
6. Centralize contribution documentation #2054

Theme: Automation

Our automation is mainly to ensure the latest versions mentioned on the website are accurate at all times.

1. Add more projects under our Automation list. You can help by writing scripts that fetch release dates and version numbers from various upstream sources. See [PAN-OS] Subversions removed by automation release-data#26 for example.
2. Improve our existing releases.json file schema in the release-data repository to add more information. Update releases JSON format release-data#51
3. Standardize the automation configuration format so it works the same across all types. See Support Multiple regexes for git type release-data#41 for example. Right now, adding multiple types might result in unexpected behaviour for example.
4. Fix newlines for new release cycle report #1868
5. Automate checking for broken links. Broken Links #1206
6. Start validating frontmatter on all PRs, including PRs raised from forks. Validate Frontmatter / validate check is not mandatory for merging PRs #1979
7. Migrate products to NPM automation when it makes sense #2071

Theme: Integration

Integration is about empowering other projects that are using our API or dataset.

2. Document Known Users of the API
3. Get our API from Alpha to Stable:
   • API Versioning, [Feature] We need API version for endpoints #2066
   • Dealing with missing attributes, types
   • New endpoints like /latest
   • Exposing product information in our API
   • Creating README badges powered by our dataset. Support shields.io #2003

Theme: Ecosystem

This is about big-picture plans, that can hopefully push the supply chain security ecosystem forward.

1. Creating a SBOM Scanner that runs using Netlify Edge.
2. Embedding PURL and CPE data into our API, so as to increase scanning accuracy. See [purl] Initial work on linking to PURLs #1545, Add mongodb-server purl #1778 for example. Documentation is pending: Document purls key in the contribution guide #1917
3. Integrate with the SBOM Ecosystem: Integrate with the SBOM Ecosystem #763. Perhaps start by publishing a Grype-compatible feed that can be used to scan SBOMs.
4. Publish data in Promtheus format to allow usage directly in observability ecosystem (such as by setting up alerts for EOL dates). Prometheus exporter #975
5. Publish a specification for a releases.json format, which can be used by vendors to publish information about supported products, and releases. We have a v0 Draft up for this for feedback: RFC: Initial Draft releases.json#1
6. EMail Notifications: Get email notifications for specific tech at set intervals #238
7. Add RSS feeds for new releases and EOLs: Per-Tool RSS Feed Planning #48

Theme: Usability

Improve usability of the website itself, making it friendlier and easier to use.

1. Images for social sharing: Please implement the Open Graph protocol for products homepage #2007. Site Logo and Cards #28
2. Improve accessibility  #1963
3. Add links to changelogs for all pages. Link to changelogs and/or upgrade guides #39
4. [Feature Request] Dark Mode #1187
5. Allow changing order of columns  #404
6. Autofocus to search-input #367
7. Visual timeline #166
8. Add calendar feeds: Add support for ICS Files #59

[marcwrobel]

We have a hell of a lot of work to do! 😉

[adriens]

2023 will be a great year ✨ 💪

[adriens]

❔ Why not organizing the roadmap as a GH Issue project ?

[noqcks]

Is there any automation around automatically setting eol dates for products?

I was looking for something under _auto but couldn't find anything. I see that we have automation around automatically grabbing latest software versions, but I think programatically determining an EOL date could be possible too for a subset of projects.

Some of the more simple versioning policies like

• EOL support until 2 major versions are released
• EOL support x months from release

Any interest in this?

[adriens]

I know that projects are CI driven but have not yet used it

[captn3m0]

@noqcks It is planned, currently blocked on finalizing our schema for the release-data project: endoflife-date/release-data#51

This currently includes versions and release dates, but we want to add EOL dates, identifiers, and probably more. For the first pass, we'll probably just focus on scraping EOL information.

[captn3m0]

Why not organizing the roadmap as a GH Issue project ?

Maybe once we have issues created for most of them. This was easier.