Are all products accepted on endoflife.date?

[marcwrobel]

During #1923 review, a good question was raised: are all products accepted on endoflife.date?

Let's take an example to illustrate that question. If I open a PR for a Java library I created, jbanking, will it be accepted ? Note that this library is not popular and is only used by a few dozen people in the world.

This particular case raises a few questions:

• Is there a limit to the kind of products accepted on endoflife.date?
• Should a product be popular to be accepted on endoflife.date? If yes, how do we measure the popularity? What are the rules (maybe with rules similar to what can be found on simple-icons?

Whatever the answer is, I think it should be documented in the project's contributing guide and maybe also in the New product suggestion.

[captn3m0]

I think having something similar to Wikipedia Notability guidelines makes sense. The most important criteria I would have is that it needs to be useful to end-users of the product.

Creating pages for libraries that nobody is checking EOL for, is not helpful. Neither is creating dummy pages for even semi-popular packages, which follow the usual conventions (only the latest release is supported).

A good metric would be to check search engine numbers for queries around the topic: (EOL iPhone, EOL Python, EOL {term}).

[captn3m0]

• We should err on the side of accepting user requests instead of saying no, especially if these requests come from end-users.
• If we can add automation that lets us update major releases as well, such as for nix where only one release is supported at any given time - we could potentially add lots more products without taking on much maintenance burden.