social.coop

0 posts0 participants0 posts today

avlapHow does the institutional crisis in the <a href="https://mastodon.nl/tags/USA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#USA</a> affect the <a href="https://mastodon.nl/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> license? Like, do you want your copyright (or copyleft) being protected by a Russian or Chinese judge? <a href="https://mastodon.nl/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> <a href="https://mastodon.nl/tags/USA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#USA</a> <a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> <a href="https://mastodon.nl/tags/EU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EU</a> <a href="https://mastodon.nl/tags/court" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#court</a>

Philippe MarczewskiUn an après sa parution, "Quand Cécile" (Le Seuil) va voyager un peu. Nous avons besoin, plus que jamais, d'un imaginaire européen susceptible de nous donner de l'espoir. Un imaginaire qui, parce qu'il chérit la diversité des cultures et des langues, et connait la valeur du bien commun, a pour but d'offrir bien plus que "les dividendes de la paix". C'est dire si je suis vraiment très heureux de figurer sur cette liste.<a href="https://mastodon.social/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> <a href="https://mastodon.social/tags/europeanunion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#europeanunion</a> <a href="https://mastodon.social/tags/litterature" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#litterature</a> <a href="https://mastodon.social/tags/books" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#books</a> <a href="https://mastodon.social/tags/FWB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FWB</a> <a href="https://euprizeliterature.eu/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://euprizeliterature.eu/</a>

Ype Kingma<a href="https://social.tchncs.de/@theesm" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@theesm</a> I'm using <a href="https://mastodon.green/tags/APL2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#APL2</a> / <a href="https://mastodon.green/tags/MIT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MIT</a> at the moment, o.a. because this dual licence is widely used for <a href="https://mastodon.green/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> code.I considered a triple licence also giving the choice of <a href="https://mastodon.green/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> , but refrained from doing so because I do not know of an example for that.

WilkoWhat's the general opinion on <a href="https://social.tchncs.de/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> here? I license most of my own stuff <a href="https://social.tchncs.de/tags/gpl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gpl</a> (as I'm fairly confident it's enforceable in the EU as there are court cases backing this) but have been wondering if EUPL is a better choice as the GPL was written with the US legal system in mind and I'm not a US citizen, the EUPL seems to have backing by the European Commission which has more weight in my jurisdiction.

small circle 🕊 in calmnessA <a href="https://social.coop/tags/DuckDuckGo" class="mention hashtag" rel="tag">#DuckDuckGo</a> search on <a href="https://social.coop/tags/EUPL" class="mention hashtag" rel="tag">#EUPL</a> gives a proper <a href="https://social.coop/tags/Wikipedia" class="mention hashtag" rel="tag">#Wikipedia</a> entry: <a href="https://duckduckgo.com/?q=eupl&t=ffab&ia=web" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://duckduckgo.com/?q=eupl&t=ffab&ia=web</a>

avlap<a href="https://mastodon.social/@rzeta0" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@rzeta0</a> <a href="https://post.lurk.org/@nebogeo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nebogeo</a> <a href="https://social.thentrythis.org/@thentrythis" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thentrythis</a> Wasn't GPLv3 a mistake by overreaching a lot? Making people less willing to go for GPL?The <a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> is a reciprocal license, which is a more permissive license then GPL.

avlap<a href="https://interoperable-europe.ec.europa.eu/collection/eupl/news/gpl-20-facing-court-ruling-paris" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://interoperable-europe.ec.europa.eu/collection/eupl/news/gpl-20-facing-court-ruling-paris</a><a href="https://heathermeeker.com/2024/02/17/french-court-issues-damages-award-for-violation-of-gpl/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://heathermeeker.com/2024/02/17/french-court-issues-damages-award-for-violation-of-gpl/</a> <a href="https://mastodon.nl/tags/GPL2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL2</a> <a href="https://mastodon.nl/tags/EU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EU</a> <a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a>

avlapI feel the <a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> is missing a requirement which <a href="https://mastodon.nl/tags/MPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MPL</a> has: "You must "additionally distribute" under (L)GPL. In other words, you must make the MPL-licensed source code available to your recipients under both MPL and (L)GPL. Someone downstream from your recipients can then take under (L)GPL-only or MPL-only. " <a href="https://www.mozilla.org/en-US/MPL/2.0/combining-mpl-and-gpl/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.mozilla.org/en-US/MPL/2.0/combining-mpl-and-gpl/</a><a href="https://mastodon.nl/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> <a href="https://mastodon.nl/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> <a href="https://mastodon.nl/tags/LGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LGPL</a> <a href="https://mastodon.nl/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a> <a href="https://mastodon.nl/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> <a href="https://mastodon.nl/tags/mozilla" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mozilla</a> <a href="https://mastodon.nl/tags/EU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EU</a>

avlap<a href="https://hachyderm.io/@mitchellh" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mitchellh</a> Isn't the EUPL or MPL license something for <a href="https://mastodon.nl/tags/Ghostty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ghostty</a>? Then people can use it in any project, but will the gostty code be free. <a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> <a href="https://mastodon.nl/tags/MPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MPL</a> <a href="https://mastodon.nl/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a>

silwolBig tech like <a href="https://chaos.social/tags/Amazon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Amazon</a>, <a href="https://chaos.social/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a>, <a href="https://chaos.social/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apple</a> seem to dislike strong copyleft licenses like <a href="https://chaos.social/tags/AGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPL</a> and <a href="https://chaos.social/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a>. Isn't that alone a good reason to license your code under one of these?

dwardoricHi folks, I'm thinking about switching a project from AGPL 3 to EUPL 1.2.Any thoughts on that or advice?<a href="https://chaos.social/tags/AGPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPL</a> <a href="https://chaos.social/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> <a href="https://chaos.social/tags/FLOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FLOSS</a> <a href="https://chaos.social/tags/License" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#License</a> <a href="https://chaos.social/tags/Licensing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Licensing</a>

EC_DIGITUnlock the secrets of <a href="https://social.network.europa.eu/tags/OSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OSS</a> licensing with <a href="https://mstdn.social/@geant" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@geant</a> latest guide! 📘 Learn why the European Union Public Licence-1.2 (<a href="https://social.network.europa.eu/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a>) stands out for preserving code's public nature while ensuring maximum compatibility. 👉 <a href="https://europa.eu/!xWFFmc" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://europa.eu/!xWFFmc</a>

Maxi 10x 💉Sehr interessante Zusammenfassungen hier zur <a href="https://chaos.social/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a>-Softwarelizenz und ihren Vorteilen gegenüber den GPL-Varianten:<a href="https://fosstodon.org/@prma/112326274313004459" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://fosstodon.org/@prma/112326274313004459</a>

PermaI'm considering using EUPL instead of GPLv3 for my binaries. What do you think? <a href="https://fosstodon.org/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> <a href="https://fosstodon.org/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a>

Sofie 🏳️‍🌈The <a href="https://hachyderm.io/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> is one of those licenses that keep on growing on me.For example, today I learned that its compatible license clause, which lets you integrate any EUPL code into a larger work under a different copyleft-license, will still require you to publish source code even if you only distribute your larger work over the network, regardless of which compatible copyleft license you choose.I didn't even know it was possible to require that!:revblobfoxread: <a href="https://joinup.ec.europa.eu/collection/eupl/news/understanding-eupl-v12" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://joinup.ec.europa.eu/collection/eupl/news/understanding-eupl-v12</a>

BramThis is also why I use and can highly recommend the <a href="https://social.noordstar.me/tags/EUPL" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> to everyone who likes copyleft. It's a copyleft license, but it offers a dual license to other established copyleft licenses. So it's basically saying, "you can use whichever license you like, as long as it's copyleft too." This makes it way more compatible with licenses that would otherwise clash. 🇪🇺

avlap"Then you need to write a piece of code which you can license under the GPLv3+, or find a suitable module already available that way, and add it to the program. Adding that code to the CeCILL-covered program provides grounds to relicense it to GPLv3+."4/4<a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> <a href="https://mastodon.nl/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a> <a href="https://mastodon.nl/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> <a href="https://mastodon.nl/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> <a href="https://mastodon.nl/tags/copyright" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyright</a> <a href="https://mastodon.nl/tags/copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a> <a href="https://mastodon.nl/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a>

avlap"To do this two-step relicensing, you need to first write a piece of code which you can license under the CeCILL v2, or find a suitable module already available that way, and add it to the program. Adding that code to the EUPL-covered program provides grounds to relicense it to the CeCILL v2."3/...<a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> <a href="https://mastodon.nl/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a> <a href="https://mastodon.nl/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> <a href="https://mastodon.nl/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> <a href="https://mastodon.nl/tags/copyright" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyright</a> <a href="https://mastodon.nl/tags/copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a> <a href="https://mastodon.nl/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a>

avlap"The EUPL allows relicensing to GPLv2 only and GPLv3 only, because those licenses are listed as two of the alternative licenses that users may convert to. It also, indirectly, allows relicensing to GPL version 3 or any later version, because there is a way to relicense to the <a href="https://mastodon.nl/tags/CeCILL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CeCILL</a> v2, and the CeCILL v2 gives a way to relicense to any version of the GNU GPL." 2/...<a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> <a href="https://mastodon.nl/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a> <a href="https://mastodon.nl/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> <a href="https://mastodon.nl/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> <a href="https://mastodon.nl/tags/copyright" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyright</a> <a href="https://mastodon.nl/tags/copyleft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a>

avlapQuestion about <a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a> <a href="https://mastodon.nl/tags/license" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#license</a> and comments on them by <a href="https://mastodon.nl/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> <a href="https://hostux.social/@fsf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fsf</a> In the FAQ about <a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a>, it is stated:"To be legitimate, the use of the compatibility clause must result from necessity: using it for the sole purpose of relicensing a copy of the original work would be a <a href="https://mastodon.nl/tags/copyright" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#copyright</a> infringement." <a href="https://joinup.ec.europa.eu/collection/eupl/how-use-eupl" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://joinup.ec.europa.eu/collection/eupl/how-use-eupl</a>BUT! On website of <a href="https://mastodon.nl/tags/FSF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> <a href="https://mastodon.nl/tags/GNU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GNU</a>, a way is described to relicense <a href="https://mastodon.nl/tags/EUPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUPL</a>. Are they pointing to a way which is in fact a copyright infringement?<a href="https://www.gnu.org/licenses/license-list.en.html#OSLRant" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.gnu.org/licenses/license-list.en.html#OSLRant</a> 1/...

Recent searches

Search options

Administered by:

Server stats:

#eupl