search

endoflife-date / endoflife.date

Informative site with EoL dates of everything
https://endoflife.date
MIT License
2.39k stars 733 forks source link

Project Roadmap #2108

Open captn3m0 opened 1 year ago

captn3m0 commented 1 year ago

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. https://github.com/endoflife-date/endoflife.date/issues/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 https://github.com/endoflife-date/release-data/issues/26 for example.
  2. Improve our existing releases.json file schema in the release-data repository to add more information. https://github.com/endoflife-date/release-data/issues/51
  3. Standardize the automation configuration format so it works the same across all types. See https://github.com/endoflife-date/release-data/issues/41 for example. Right now, adding multiple types might result in unexpected behaviour for example.
  4. https://github.com/endoflife-date/endoflife.date/issues/1868
  5. Automate checking for broken links. https://github.com/endoflife-date/endoflife.date/issues/1206
  6. Start validating frontmatter on all PRs, including PRs raised from forks. https://github.com/endoflife-date/endoflife.date/issues/1979
  7. https://github.com/endoflife-date/endoflife.date/issues/2071

Theme: Integration

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

  1. Document Known Users of the API
  2. Get our API from Alpha to Stable:

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 https://github.com/endoflife-date/endoflife.date/pull/1545, https://github.com/endoflife-date/endoflife.date/pull/1778 for example. Documentation is pending: https://github.com/endoflife-date/endoflife.date/issues/1917
  3. Integrate with the SBOM Ecosystem: https://github.com/endoflife-date/endoflife.date/issues/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). https://github.com/endoflife-date/endoflife.date/issues/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: https://github.com/endoflife-date/releases.json/pull/1
  6. EMail Notifications: https://github.com/endoflife-date/endoflife.date/issues/238
  7. Add RSS feeds for new releases and EOLs: https://github.com/endoflife-date/endoflife.date/issues/48

Theme: Usability

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

  1. Images for social sharing: https://github.com/endoflife-date/endoflife.date/issues/2007. https://github.com/endoflife-date/endoflife.date/issues/28
  2. https://github.com/endoflife-date/endoflife.date/issues/1963
  3. Add links to changelogs for all pages. https://github.com/endoflife-date/endoflife.date/issues/39
  4. https://github.com/endoflife-date/endoflife.date/issues/1187
  5. https://github.com/endoflife-date/endoflife.date/issues/404
  6. https://github.com/endoflife-date/endoflife.date/issues/367
  7. https://github.com/endoflife-date/endoflife.date/issues/166
  8. Add calendar feeds: https://github.com/endoflife-date/endoflife.date/issues/59
marcwrobel commented 1 year ago

We have a hell of a lot of work to do! :wink:

adriens commented 1 year ago

2023 will be a great year :sparkles: :muscle:

adriens commented 1 year ago

:grey_question: Why not organizing the roadmap as a GH Issue project ?

noqcks commented 1 year ago

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

Any interest in this?

adriens commented 1 year ago

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

captn3m0 commented 1 year ago

@noqcks It is planned, currently blocked on finalizing our schema for the release-data project: https://github.com/endoflife-date/release-data/issues/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 commented 1 year ago

Why not organizing the roadmap as a GH Issue project ?

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

flo7000 commented 2 months ago

Hello all, First, I want to thank you for the your work on this amazing project! We're planning to implement it in KQL-Queries in Defender to see who hasn't updated EOL software. Now I have a question regarding the CPE data: what's the status here? If you need resources here, I could do some things, because I want to learn more during my apprenticeship 😎

@captn3m0

captn3m0 commented 2 months ago

We're planning to implement it in KQL-Queries in Defender to see who hasn't updated EOL software.

Would be great if you could publish a blog post or tutorial around this.

CPE data: what's the status here?

PRs are welcome to improve our data. I was hoping to piggy-back on Repology to link to CPEs (same as our plan for PURLs) - see https://github.com/endoflife-date/endoflife.date/issues/5352. While this would take some time, PRs are welcome for adding CPE identifiers, especially to things that aren't tracked on Repology. This would include devices, operating systems etc.

captn3m0 commented 2 months ago

@flo7000 I've filed #5354 so we have an updated list of pages without identifiers available at https://deploy-preview-5354--endoflife-date.netlify.app/help/identifiers-needed/ (endoflife.date/help/identifiers-needed/ once this is merged).

flo7000 commented 2 months ago

Would be great if you could publish a blog post or tutorial around this.

I'll talk to my colleagues about that (next week), but I think they'll say yes - I'll keep you updated

And thank you for update regarding the CPE's, I have some questions, but I'll ask them in #5354

I have one "general" question about PRs: I haven't used github that much, which of the following do you recommend?

Or maybe something else?

captn3m0 commented 2 months ago

GitHub Desktop will anyway fork the repo in the background, and is probably easier if you're making lots of changes to a single file - the web UI is quite good enough for single line changes.