Read on Twitter
Last week, we announced a bunch of work that we’ve been working on for the past year @tidelift. Catalogs change the way that teams adopt and use open source. I keep meaning to share some thoughts but the past week has just been busy 
1/n
1/n
It’s been a huge team effort so thanks to everyone on the team. We’ve overhauled our data infrastructure, built up a lot of new workflow stuff, and built a CLI tool that folks can install to power a lot of the workflow. Oh yeah, and it was done during a pandemic. 2/n
Building your own catalog of approved OSS can simplify legal review for new software releases and reduce the burden on every team to understand the impact of security vulns. You let devs focus on building awesome products while keeping an org wide handle on potential risks. 3/n
Obviously doing so requires a workflow that works across your whole company. A web app for many, a CLI tool for devs, and native notifications where you work are crucial to success. And the data backing it all needs to be accurate and current. 4/n
Managed catalogs bring more value by giving the decision makers in your organization information that has been curated and verified by the maintainers of the open source you’re using. Oh yeah, and we pay the maintainers! 5/n
All of this can let you mimic some of how Google, Netflix, and other tech giants engage with and manage their open source usage. But with a Tidelift subscription you don’t have to use a monorepo or build a whole lot of tools on your own to get there. 6/n
That said, if you enjoy building tools like this, I’m hiring engineers for my team. We wanna make open source better for everyone! Take a look at https://tidelift.com/jobs and apply or DM me. There are roles in the rest of the org too and happy to talk about them as well. /fin
