As some of you may have picked up on, one of our primary goals at Tidelift is simply: pay the maintainers! Now, there’s a lot of complexity buried in that shorthand, but the high level goal is clear: we believe that creators and maintainers of open source software should be empowered earn scalable income from their open source projects.
To be as successful at this, Tidelift needs to effectively support maintainers of not just one, but tens, hundreds, and sometimes even thousands of popular open source projects.
To that end—and thanks to some great feedback from lifters on this forum!—today we’re releasing deeper integration with both npm and RubyGems, making it easier for you to quickly lift all of your packages.
Why is this important? Identifying (and lifting!) all of your packages can become cumbersome pretty quickly for prolific maintainers. And by not lifting all of your packages, you’re limiting your potential earnings from Tidelift subscribers (who want as many of their dependencies supported as possible!). And given our goal of paying maintainers, we needed to fix that!
This is also valuable for Tidelift subscribers, and will help us acquire more subscribers: the more lifted packages, the more valuable our subscription is to potential customers. By enabling lifters to support more packages on Tidelift, we will be able to acquire more subscribers, and help you earn more.
How does it work?
When you log into Tidelift, you may now see a new modal asking you to identify your npm or RubyGems username (or confirm what we guess your username is).
If you opt to do this, you can then navigate to the Packages tab, then Lift new package, where you’ll see the following:
If you click on “See if you have other packages to lift in your ecosystem!”, you’ll be taken to a new screen, where you can select all packages that you currently maintain. If you maintain them individually, you can lift them right away! If you are one of a number of maintainers, we’ll require you to receive confirmation from your co-maintainers that they’re okay with you lifting that package.
Please let us know if this new feature is helpful for you, if you encounter any bugs, and/or if you’d like this expanded to other ecosystems! And if you do find yourself lifting more packages, we’d love to get in touch about your experience. We’re investigating ways to make lifting simpler for maintainers with many packages, and we’d love to learn from you!