upvote
Many important open source projects have already switched to Business Source License. However, they only switched after they became famous. I have not seen any projects that became famous that started with BSL.
reply
> Many important open source projects have already switched to Business Source License.

No: first not "many", but very few. And second they are proprietary projects.

reply
Some of us have the radical opinion that the definition of open source isn't what a specific organization (with no trademark on the term) dictates, but whether the source is open.

Other people express strong opposition to the idea that "open" might just mean the same thing as "available" in the context of open source. None of those people have proposed a more coherent definition that I've seen of what that word means in that specific phrase though.

reply
"Open Source" and "Free Software" are both well-established terms with well-documented histories of debate and consensus-forming among huge and healthy communities over a span of decades, and organizations that steward the meanings of those terms. Just because you don't like them doesn't mean you get to pretend you're the first person to try to define the word "open" for software.

https://opensource.org/osd https://www.fsf.org/licensing/

reply
I often hear this criticism and "bait-and-switch" is also mentioned. At the same time, when you have a small project or tool only used by a handful of people the risk of it being hacker or not responding in time is very different to a project which is essential to the whole world. I don't now what a realistic solution would look like though.
reply
Then it wouldn't be free software anymore.
reply
Yes, they should do this. Howvee, they'd stop being considered free software and open source.

Alternatively they can put such large share-back requirements that corporations don't want to use it and would rather pay for an alternate license. SSPL and to a lesser extent AGPL achieve this.

reply
A free software license is by definition a license that doesn't place requirements on anyone to pay for it, sponsor it, contribute or otherwise. If a license didn't grant these freedoms, it wouldn't be a free software license.

What you're asking is, should widely used libraries be proprietary software sold for money? And that is indeed an honest question. There's a huge ecosystem of developers out there who say yes, there's nothing special about that idea at all.

For example, on Apple, Google and Microsoft platforms you don't use OpenSSL when writing native apps. You use the vendor's cryptography APIs. The licenses of Windows and macOS force all users large or small to pay for them. On Android, the native crypto provider is Conscrypt:

https://github.com/google/conscrypt/

... which is open source, but you will notice that it doesn't accept outside contributions and is funded by revenue from Android's proprietary components licensing. So that's very close to the model you're suggesting: it's "open source" but in practice large corporations pay Google lots of money for the privilege of shipping it.

Moreover Google fund BoringSSL and other forks of OpenSSL. The issue here isn't funding levels (anymore). The issue is that OpenSSL is written in C, and not very good C at that.

reply
Minor nitpick, but at least as far as the GNU GPL goes, it explicitly allows you to charge for software distribution when the software came bundled with a tangible item (like the firmware of an IoT device). The distributor can require you to pay them to get it. This was more common in the old days when software mostly came on CD-ROMs and you'd be getting another physical item in the mail, but the provision remains in the GPLv3 under section 6(b)(1) as an option that the distributor can require.
reply
It has to be the reasonable costs of distribution. It can't just be an arbitrary fee.
reply
Not exactly. You can charge whatever you like for the software - but whoever buys it from you is then allowed to give it away for free to anyone else, so this is only a theoretical possibility.

The thing you're allowed to charge for but only a reasonable amount is to provide the sources to software you have previously distributed, for free or otherwise. If I get some binaries from you and then request the sources too, under the GPL, you are forced to provide them, but you can ask for a fee to cover the transfer costs.

reply
I certainly think so, but we who think this get shouted down because "It's not Open Source(TM)".
reply
Have you ever wondered who's in charge of choosing what counts as Open Source(TM)? Look no farther: https://opensource.org/sponsors

Yes, that Automattic. Yes, that Google, AWS and Cisco. Yes, that Microsoft. There are one or two entities in this list I don't mind but... damn.

It's time to retire the phrase "open source" and go back to "free software". Not many people know "open source" was originally coined by corporations who didn't want anything to do with freedom.

reply
Not many people seem to know that the definition of "open source" they use (the OSD) is actually the definition of "free software" Debian uses (the DFSG) with the serial numbers filed off.

The problem with "free software" lies exclusively with the English language; other languages don't have the same issue due to having separate words for "freedom" and "zero price".

reply
Debian is free to use any inclusion criteria it wants - especially since it still includes software thst doesn't meet the criteria. It shouldn't become the global default definition of "open source" though.
reply
That's why some prefer calling it "libre software."

Also see LibreOffice.

reply
The FSF would say the exact same. So this point is moot, unless you think Richard Stallman is a corporate shill.
reply
This is backwards imo, it is related to people that chose to build these projects. Everyone might have a different decision on it.
reply