captn3m0
3 months ago
The list of services makes it look like you’re using endoflife.date as the data source, which I kept under MIT, and requires attribution. We’re happy to support every usecase, but please provide attribution :)
(Bitcoin-core stands out very much).
Edit: their backend service source does mention endoflife.date as the source, but it is hidden away in the developer docs (https://gitlab.com/dcentrica/metaport/metaport-server/-/blob...)
> By default, Metaport uses the API provided by endoflife.date, but alternative backends can be used instead. The following instructions are relevant to Metaport CE in self-managed setups.
If you're building a complete SaaS product on top of an open-source database maintained by volunteers, please credit them better, or support us: https://github.com/sponsors/endoflife-date
theruss
3 months ago
Thank you for this. A recurring contribution has now been setup the credits will be improved. There isn't yet a SaaS until the product is validated, until then, Metaport is on-prem only through the OSS community edition where dev.md is built into the docs site as well: https://docs.metaport.sh/en/dev/.
captn3m0
3 months ago
Thanks a lot, I've added Metaport to our list of known users: https://github.com/endoflife-date/endoflife.date/wiki/Known-...
theruss
3 months ago
Thank you - but it's already in the list! It was added several months ago:-)