My recipe database and baking planner focused on bread baking is now finally open source. Feel free to take a look and maybe send in a pr or just take a look:
Nous saluons la publication sous licence #AGPL du logiciel Biblys, solution e-commerce au service de l'édition indépendante !
https://blog.biblys.fr/posts/biblys-est-desormais-un-logiciel-libre
Depuis hier vous pouvez trouver le code source de #Biblys ainsi qu'une bibliothèque en #PHP pour gérer les ISBN et EAN.
Félicitations à Clément Latzarus pour cette démarche indispensable d'ouverture qui lui a pris plus de sept ans pour l'accomplir dans les meilleures conditions !
Vous agissez dans la #santé au #travail ? Vous êtes IDEST, médecins du travail, IPRP ou autre dans un #SPST interentreprises ? Vous avez besoin d'analyser transversalement l'effectif de vos 400 à 500 entreprises, 7 à 10 000 salariés, et de mettre en face la sinistralité AT MP ?
Mon webmaster a été dans ce cas. Il a fait de cette problématique un outil sous licence libre (#AGPL) devenu sujet de DIU pour valider son évolution professionnelle.
A découvrir ici : https://st.medshake.net
The year is fast on its way into its final quarter, which means the #FOSS release of #Mattrbld is coming closer.
A big part of that is the licence, of course. I want Mattrbld (and potential derivatives) to be accessible to all, forever. Which is why I’m considering the #AGPL licence (since technically it’s a SaaS product).
Is there anything that would speak against this choice? Are there some special considerations to take before applying the licence?
What's that you say?
ElasticSearch is once again available under the #AGPL?
Great news, I say.
https://www.elastic.co/de/blog/elasticsearch-is-open-source-again
"Decentralized communication protocol Matrix shifts to less-permissive AGPL open source license."
"AGPLv3 is a recognized open source license, even though not everyone is a fan of its inherent restrictions."
#PaulSawers, 2023
Yeah, we get it Paul. Having to help with the dishes after you eat your free lunch is "restrictive". It's more "permissive" to let people waltz in, eat their fill, and bugger off, without being expected to help out
Big tech like #Amazon, #Microsoft, #Apple seem to dislike strong copyleft licenses like #AGPL and #EUPL. Isn't that alone a good reason to license your code under one of these?
#TIL about #LibreLingo;
"... an experiment to create a community-driven language-learning platform"
Licensed under AGPL.
Can someone explain the #AGPL to me?
For example: #gitAnnex is licensed under AGPL3+. So if a company bases their product on it and they provide an online service that involves git-annex in the {front,back,}end, then... what? They would need to make their entire stack AGPL-compatible, i.e. provide the source code? Or only if they changed something in git annex they would need to make *their* version of git annex public, not their entire stack?
Yesterday I spent a few minutes switching my main two repositories from #GPL to #AGPL licenses because GPL has a loophole that I wanted closed.
tl;dr: GPL can be ignored if the code is being accessed via a server based API.
I've no idea why that wasn't covered by default.
To me the default should be everything and people could then choose looser licenses where they choose to permit certain uses without code sharing.
Be-aware!
#FOSS #Copyright #Licensing #OpenSource
Hi folks, I'm thinking about switching a project from AGPL 3 to EUPL 1.2.
Any thoughts on that or advice?