>"The model and pitch also came into clearer focus. Truly, it’s simple: if you’re betting your business on a critical open source technology, you<p>1. want it to be sustainably and predictably maintained; and<p>2. need occasional access to expertise that would be blisteringly expensive to acquire and retain.[5]<p>Getting maintainers on retainer<p><i>solves both problems for a fraction of the cost</i><p>of a fully-loaded full-time engineer. From the maintainers’ point of view, it’s steady income to keep doing what they do best, and to join one more Slack Connect channel to answer high-leverage questions. It’s a great deal for both sides."<p>I love it!<p>I love your business model!<p>More power to you, your company, and other future Open Source maintenance companies!
I'm really glad to see `bluemonday` in such company, but I'm also really happy to hand over the reigns to a group of engineers that can focus on OSS.<p>I am the author of <a href="https://github.com/microcosm-cc/bluemonday">https://github.com/microcosm-cc/bluemonday</a> but being a maintainer is a journey, you make a tool for yourself, you realise others will benefit and open it up to others... time passes... and then you realise you are that tiny pillar in the XKCD comic about dependencies, and that when you make a casual update to the project that multiple security companies ping you to ask the impact and scope of the change, implications, and of course others ping you to say that it breaks their individual workflow.<p>I've known Filippo for almost as long as that library has existed, and I know it's in a safe pair of hands, and that Geomys is going to be a good home to all of the OSS projects that they have in their portfolio.<p>It's definitely a journey, how should these foundational elements be supported and funded? This is one answer to that question, and I'm glad it exists as my spare cycles were very few, I'm also really glad for Filippo being so key to it, if anyone will make this work and do a good thing it will be him and those who he surrounds himself with.
This is what I was envisioning when I wrote this: <a href="https://gavinhoward.com/2023/11/how-to-fund-foss-save-it-from-the-cra-and-improve-cybersecurity/" rel="nofollow">https://gavinhoward.com/2023/11/how-to-fund-foss-save-it-fro...</a> .
I personally like Sentry's approach more, their program focused on supporting the breadth and depth of their dependency tree rather than just the critical components <a href="https://blog.sentry.io/we-just-gave-500-000-dollars-to-open-source-maintainers/" rel="nofollow">https://blog.sentry.io/we-just-gave-500-000-dollars-to-open-...</a> Disclaimer: I work for thanks.dev
This is pretty exciting to see. I'm not an OSS maintainer myself, mostly due to lack of focus/energy, but the prospect of working with a company such as Geomys is inspiring. And I've been wanting to learn Go anyway...
This is a fascinating idea. However, I wonder how it fits with the fact that the target type of project is still maintained by one person / project expert. Where is the redundancy for the proverbial maintainer-run-over-by-a-bus? While the three engineers necessary for maintaining a critical dependency is expensive, a company is unlikely to lose them all at once.
I wrote a bash script before anything existed for node.js to run a process on a server...people were just doing `node ./index.js` -- my script created and init.d/start-node.sh script and suprisingly its my most popular project even today -- that was back in 2010 I wrote that shit. SHortly after it got picked up by some js newsletters and HN I found nodemon and switched to that.<p>For what its worth now I use systemd scripts.