And then people complain about "bait and switch " or "pulling the rug" when an OSS project becomes successful and tries to fund itself in some way. "But that should be free" shouts everyone. I'm increasingly coming around to the idea that OSS was the biggest swindle the corporations managed to pull off.
Select the right OSS license and use dual licensing.
GPL/AGPL/LGPL is the way to go for business. There are many dual-licensing success stories using GPL/AGPL, both large and small: Qt, iText, Grafana, Loki, Tempo, Mattermost, Cal.com, Baserow, and even MongoDB originally.
Qt is an especially interesting case because KDE and the Qt Company have a written contract. Qt can't just switch licenses. They have retreated from every voluntary contribution to open source, but the contract binds them and they can't do anything to it unless they do complete rewrite from scratch.
I can't speak for anyone else, but I don't mind at all when an open source project switches licenses or whatever. They gave away the fruit of their labor, but I am not entitled to any more of it.
What does bother me is when the projects pivot to claiming that users now have a moral obligation to financially support the project. There is a kind of dishonesty in this move.
It's not that a successful project "should be free", it's that its success depended on it being free. If they had said all along that they'd eventually ask users to pay, that would be honest... but then they wouldn't have seen much of that adoption in the first place.
In my case, I never intended on my open source project becoming popular, it just did and I had to either abandon it or make it my job. I'm not sure where that falls in your judgement.
It's your project, to the extent that you own the copyright. You are free to switch the license on your project, etc. If anyone tries to shame you for this, you should pay no mind. (Edited to add that you are also free to abandon it, and you could do that with a clear conscience.)
Likewise, users are free to continue using open source software without payment or donation, to fork the project, etc. If anyone tries to shame them for this, they should pay no mind.
Why would you have to abandon it instead of just keeping on in your preferred pace? If anybody wants more rapid development they can fork it, not your problem.
Some people also have tried the paid new feature prioritization where it later lands for everyone. I think it worked in some projects but project must have been really good otherwise.
I mean: who doesn't want to work full time on their passion project? Especially when I'd just been made redundant, I feel most people would do the same.
> I can't speak for anyone else, but I don't mind at all when an open source project switches licenses or whatever. They gave away the fruit of their labor, but I am not entitled to any more of it
It only bothers me when they try to claim their new license is open source or use misleading language when it isn't. Which seems to be what 90% companies doing that do.
People can do whatever they want with their intellectual property as long as they aren't lying about it.
I've been shouting this from the rooftops for ages now. OSS is a trojan horse, something meant to devalue the work of independent developers/small businesses and ensure that the only way the software can be supported is through the patronage of big tech, who earn the money to control such OSS through their unethical monopolistic practices. Look at the languages with funding, and where it comes from. C and C++ (both LLVM and GCC), C#, JS/TS, Java, Rust, Go, Python are all directly funded by big tech. The naive idealism results in everything falling into the hands of ~10 corporations plus some VCs who gamble on which ones will become worth acquiring by big tech, and then we wonder why everything goes to shit and our entire ecosystem is so user-hostile.
I'm not saying that big tech isn't hijacking open source software, but that does not mean that free or OSS was always "meant to devalue" devs or small companies.
Until very recently, big tech pumped untold millions of dollars into obliterating FLOSS altogether, calling it a cancer that will destroy any enterprise it touches.
You mean just Microsoft. Microsoft was an outlier. Even in the 90s, Linux and GCC were being funded by big tech. Obviously they were developed with the best of intentions, but I think it's accurate to say that OSS is "meant" to devalue developers because the purpose of a system is what it does, and that is what it does in practice.
"The purpose of a system is what it does" is the weirdest cliché I encountered here, and that's not just because it is horoscope nonsense dressed up as a fact, but because it brilliantly illustrates how many people here think they just know what a system does on a glance.
But if it was true: In the 90s, millions of small businesses around the world used FLOSS to host websites and offer services over the internet. That was decidedly not the route big enterprises wanted to go. They wanted to push through big standards through ITU et al, build giant, patented moats, and host it all on big mainframes with huge Oracle databases.
Even today, there exist small to medium businesses in the hosting and shopware space, and they can only do that because big tech could not push them out of that space because FLOSS protected them.
All of these are angles an AI reviewer can test for as well, and will (IME) mostly catch mistakes correctly. I also still manually review code, and usually also catch issues, but the severity of what I find shrinks ever further as agents get better.
The sprawling code comments are becoming the most draining part of code review though, that's really killing me from the inside.
> All of these are angles an AI reviewer can test for as well, and will (IME) mostly catch mistakes correctly.
No, none of today's AI would give you enough signal around "should this thing be built in the first place" nor if it's the correct solution on a high level.
They don't understand why you are doing what you are doing, and even if you explain it, they still don't actually understand the motivation and lots of other things.
You'll get them to do guesses and pretend they actually know how to prioritize and will tell you it makes lots of sense, whatever they come up with. But try following it blindly and you'll see where you end up.
This is why "one agent + one good developer" beats "thousands of agents working in a swarm" still today.
I don’t think I claimed agent reviews to be a panacea. It’s a tool that can help you lower the review pressure in companies working with agentic coding tools.
> What really important things are human reviews catching in your org?
Another person said:
> 1. Whether the thing should be done in the first place
And you replied:
> All of these are angles an AI reviewer can test for as well, and will (IME) mostly catch mistakes correctly
Which as I noted, is very far from the truth. I neither claimed that you said "agent reviews are a panacea", but when you claim "AI can solve all those things" and two of the first items cannot be addressed by AI (today), then I'm rebuking those specific things, not some other general point you implicitly made.
It is mostly useless at figuring out if "should this thing be built in the first place" and "if it's the correct solution", and mostly cannot help at all with those things.
Where "mostly" means kind of what it says but also not really.
The AI review are still quite far from having the same level of critical thinking and high level knowledge of your application, what you have done in the past and want to do next etc.
If you don't master this for your own project, what's even the point of your job.
reply