this post was submitted on 19 Apr 2025
1391 points (99.4% liked)
Technology
69247 readers
3743 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Redis is also on the list, but not Valkey. Gitea is on the list, but not Forgejo. Still nice to see governments endorsing the open-source-ish software they know and FOSS principles, though!
I imagine the list will be dynamic. Those projects might be on a list somewhere, just haven't been vetted yet by their standards. Start with the source projects, then dive through the forks.
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.