To be fair, I know redis and gitea (barely, gitlab is way more popular) and not the other two. Enterprise support and name recognition are quite important for government usage.
Valkey was created recently as Redis changed their license, having clauses which made the user choose between being “discriminatory against users of the software that use proprietary software within their stack, as the license requires the open-sourcing of every part interacting with the service, which under these circumstances might not be possible” or being non-commercial.
Forgejo was created when Gitea decided to go the JetBrains route a few years ago. It’s since absorbed Gitea’s clout.
The simple answer: nobody is actually reading any of these licenses. I run into the problem constantly and even people who should know better do not (most of our IT staff for example…)
Yeah, and you have to pay for that. Lots of open source software have enterprise support and usage limit licenses but having to pay for something isn’t open source. I am personally ambivalent at non-commercial licenses but I agree that the restriction against using proprietary software with Redis in commercial usage is kinda bad.
To be fair, I know redis and gitea (barely, gitlab is way more popular) and not the other two. Enterprise support and name recognition are quite important for government usage.
Valkey was created recently as Redis changed their license, having clauses which made the user choose between being “discriminatory against users of the software that use proprietary software within their stack, as the license requires the open-sourcing of every part interacting with the service, which under these circumstances might not be possible” or being non-commercial. Forgejo was created when Gitea decided to go the JetBrains route a few years ago. It’s since absorbed Gitea’s clout.
The simple answer: nobody is actually reading any of these licenses. I run into the problem constantly and even people who should know better do not (most of our IT staff for example…)
Redis allows a third option, a commercial license.
Yeah, and you have to pay for that. Lots of open source software have enterprise support and usage limit licenses but having to pay for something isn’t open source. I am personally ambivalent at non-commercial licenses but I agree that the restriction against using proprietary software with Redis in commercial usage is kinda bad.
Of course you have to pay for a commercial license, it’s in the name. Development, tooling, support, etc, all costs money.
I like the distinction. If you want to profit from open source, make your code open source. If not, pay up.