endoflife.date

End-of-life (EOL) and support information is often hard to track, or very badly presented. endoflife.date documents EOL dates and support lifecycles for various products.

github.com/endoflife-date endoflife.date/

blr.today

blr.today is an open-source project by Nemo that curates events happening in Bangalore.

It curates events from multiple sources, cleans them up, then curates them further by tagging them nicely, and makes all event data available as calendars you can subscribe to.

github.com/blr-today blr.today/

Nemo

Making and Breaking things, sometimes intentionally

View posts on Planet →

How to support

You can help us by adding a new product - https://endoflife.date/contribute
2. You can sponsor us via Open Collective or GitHub Sponsors at https://github.com/sponsors/endoflife-date or https://opencollective.com/endoflife-date
3. Tell us if your organization is using the endoflife.date data or APIs - https://github.com/endoflife-date/endoflife.date/wiki/Known-Users. Drop us a mail at nemo@endoflife.date

A small brief about your project

endoflife.date is an informational website that tracks support cycles and release schedules of over 340 products.

Not all product websites can easily answer the question: "How long is this product supported?".
We track it, and showcase exact dates along with a concise summary of the release policy.

The complete website is open-source, and we are always working to make it better. We have been doing this since 2019, as a collective effort involving over 500 contributors

One FOSS maintainer lesson for your younger self

Document tribal knowledge and decision rationale, so newer maintainers can learn from previous mistakes and attempts.

Why do you do it? Why do you bother maintaining a FOSS project?

Because Aaron Swartz would have loved it.

Which file in your project would you most like to set on fire?

/products/omnissa-horizon.

Broadcom recently acquired VMWare, but this acquisition did not include the VMWare End-User Computing division, which made a product called VMWare Horizon. This division was sold to a private equity firm called KKR, which renamed it to Omnissa. Since we track Horizon, I added this 600 word text to the page:
> After [Broadcom's acquisition of VMWare](https://investors.broadcom.com/news-releases/news-release-details/broadcom-completes-acquisition-vmware),
> Broadcom [divested the End-User Computing Division
> (which includes Horizon) to KKR](https://media.kkr.com/news-details/?news_id=48701629-ae4d-4d88-b1a9-90a438c6bf6c)
> and branded it as [Omnissa](https://www.omnissa.com/introducing-omnissa-the-former-vmware-end-user-computing-business/) as part of the restructuring - which is still in process.
> Omnissa and Broadcom have entered into [a reseller agreement enabling EUC to offer the "combined offering"](https://www.omnissa.com/setting-the-record-straight-euc-to-continue-to-offer-horizon-with-vsphere-and-vsan/)
> versions of Horizon SaaS and Horizon Term SKUs with vSphere Foundation for VDI. This
> [combined offering](https://kb.omnissa.com/s/article/14804) will be available
> in both Named User and Concurrent User license metrics and for 1-, 3-, and 5-year terms.
> EUC has no plans to increase Horizon list prices beyond normal annual adjustments.

Writing the above 600 words took me roughly 3 hours, because neither of the companies involved (VMWare, KKR, Omnissa, Broadcom) make it easy to get the above information. I wouldn't still set on fire though, because this information needs to be more accessible.

What's your open-source villain origin story?

The MP4 Player I owned was very slow, and Rockbox didn't support it. Rockbox was the coolest firmware, but unfortunately my device wasn't powerful enough to run it. However, there was another firmware called S1MP3 which was attempting the same, and I found refuge there.

If you had to use one emoji to convey what it is like to be a FOSS maintainer, what would it be?

👾

Built and Maintained by FOSS United

Contribute Forum RSS

foundation@fossunited.org