Comment by j1elo
1 day ago
Open Source has worked fine here. The author doesn't find financial support for the work, so they just want to change winds and that's a perfectly fine path forward.
If this is really much more than a personal project "for fun, on my leisure time", and it became an actually serious product-level project that provides good value in commercial environments for people, there's clearly an opportunity for a for-profit company to step in and cover that niche. But that'd require that users became customers and actually departed from their money to pay for it :)
I guess most will switch instead to asking who's the next project maintainer to work on it, to whom the new bug reports and complaints can continue to be sent for free. But if there's money to be made by using a tool, there should be money paid for using it too. We "just" need to find the new generation of FOSS Financial Sustainability solutions that actually work! Donations don't make the cut.
Something I learned about being a part of an ecosystem: if you want it, you need to support it and help it stay alive.
That applies to local shops as it does open source projects.
The project has never even had a donation button on its page, only a link with a few sponsors.
The effort to setup donations is almost always more trouble than the donations that result are worth. Better spent looking for a job, or working on a commercial project that will make money. People simply don't donate to open source projects at a level that matters.
I've been working on Open Source software for 30+ years. There's no money in it, if your idea for making money is "accept donations". I don't like it, but it's a fact. If you want to make money, you have to make something that isn't free (and even then, if you give away the most valuable parts, as in "open core" licensing, you probably still won't make enough money to make the development worth it).
When I was young and driven by idealism and optimism, I assumed that with enough users I'd be able to ring the cash register somehow. Turns out not so much. We got the users, the money never came. There are a few outliers, but there probably aren't a lot of opportunities to found a Red Hat today.
1 reply →
I wonder whether the author has considered taking the product to a paid level and what would be necessary for it.
Obviously, all contributors have some form of copyright, which may or may not have been waived depending on whether there was an ACL in place and jurisdiction. So he would need to get permission from the copyright holders, maybe in exchange for a percentage of the profit.
Changing the license of already existing code? You might not be able to do that without permission from other contributors, I agree.
But it's MIT license. We can open a company tomorrow, take that code, and start selling it. Further development and improvements of the code could be trivially done openly or behind closed doors. FWIW the author themselves could do that if they wanted.
ANd that gets rather looked on here as the authors being deceitful and not really Open Source doing a bait and switch.
I've been working on a software package I'm hoping to release in a few months... I'm really torn on either split FLOSS with commercial extensions, or just going fully private... I was planning on a pretty generous free tier, but hoping to make a bit on the side from commercial customers.
It's a bit of a niche as it is, so that's going to be rough in any kind of pricing model, as a large part of that niche is either homebrew types and the other commercial industry that will likely require some more integrations and customization.
5 replies →