71
The Lack of Compensation in Open Source Software is Unsustainable
(trstringer.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Nov 2023
71 points (100.0% liked)
Free and Open Source Software
17949 readers
62 users here now
If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Think about it from a manager’s position. If they pay something for nothing extra (donate), they won’t last long at the company. They are attracted to 2 benefits:
Corps love commercial software because managers whose neck is on the line can point the finger away from themselves if something goes wrong with it (or so they think… which is what matters in the end anyway). They tend to consider FOSS when there is a fall guy. So e.g. they hire RedHat. But as I think the article mentions, that money doesn’t trickle down from there.
We used a FOSS compiler through a separate contract. The company paid a high price for pampering by the compiler supplier. And the support was magnificent. We got the “pro” version (which for the most part was just a newer release than the version in the commons & perhaps a few extras that were just more of a luxury). But it was really about the support. Anyone on the team could file a ticket with the compiler supplier. Not just for bugs and enhancements, but if something was unclear, or if we needed to know how to do something. They always responded well, gave tips, advice, and workarounds, and if there was a bug they fixed it and we got the fix quickly. They never dropped the ball. Our bugs and enhancement requests would then make it into the core product that benefited the commons. It was a good arrangement.
Then you consider our most heavily used FOSS tool apart from the compiler: emacs. We had an internal team who compiled it and injected our internal mods to customize it for the org. Not sure if any of our customizations would have value outside the org or if that team did PRs.
In short, it’s not enough to just maintain the code and hope for donations. You need to offer a support package that gives 1st class treatment to corps who would pay a premium for it. I’m not sure if the emacs project offers anything comparable to the compiler we used, but I could see the folks I worked for signing up for something like that.