social.coop

0 posts0 participants0 posts today

lil5 :golang: 🚲 🇳🇱Because the <a href="https://fosstodon.org/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> <a href="https://fosstodon.org/tags/License" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#License</a> text is added to the top and the <a href="https://fosstodon.org/tags/CommonsClause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> is added afterwards <a href="https://fosstodon.org/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> considers the project <a href="https://fosstodon.org/tags/GPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPLv3</a> software. I’m amazed GitHub doesn’t have better licensing monitoring tools. This makes automated license tracking pretty iffy in my book.

Matt "msw" Wilson"draft <a href="https://mstdn.social/tags/CommonsClause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a>"

Matt "msw" WilsonThe <a href="https://mstdn.social/tags/CommonsClause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> pollutes the <a href="https://mstdn.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://mstdn.social/tags/commons" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#commons</a>. It creates new hazards for software users to navigate.It's /especially/ confusing when nonsensically combined with a <a href="https://mstdn.social/tags/GPL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> family license like <a href="https://mstdn.social/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AGPLv3</a>.<a href="https://mstdn.social/tags/FreeSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeSoftware</a> <a href="https://mstdn.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://github.com/thecodingmachine/workadventure/issues/2317" rel="nofollow noopener noreferrer" target="_blank">https://github.com/thecodingmachine/workadventure/issues/2317</a>

Matt "msw" WilsonOne that comes to mind is FOSSA. They're a venture capital backed startup that offers "Audit-Grade Open Source Dependency Protection".They also are the originators of the "<a href="https://mstdn.social/tags/CommonsClause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a>" <a href="https://mstdn.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> license rider that adds confusing restrictions that make software no longer Open Source. <a href="https://commonsclause.com/" rel="nofollow noopener noreferrer" target="_blank">https://commonsclause.com/</a>

Trolli Schmittlauch 🦥Eww, <a href="https://toot.matereal.eu/tags/WorkAdventure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WorkAdventure</a> is licensed under <a href="https://toot.matereal.eu/tags/CommonsClause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> (put on top of AGPL), which makes it non-free software in total. <a href="https://github.com/thecodingmachine/workadventure/issues/523" rel="nofollow noopener noreferrer" target="_blank">https://github.com/thecodingmachine/workadventure/issues/523</a>That really is unfortunate.

Yarmo 🕊We need to talk licenses. Recently discovered <a href="https://fosstodon.org/tags/commonsclause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#commonsclause</a> through the <a href="https://fosstodon.org/tags/n8n" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#n8n</a> project (big fan). I'm quite ideological but I really dig the pragmatism behind this license. The code is still <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>, accessible and extendible. That's what I want from a product I need to trust. If the owner wants my contributions but doesn't want me making money from it… I understand that! Yet I read a lot of criticism about this license.What am I not seeing?

StrypeyLike <a href="https://mastodon.nzoss.nz/tags/fairsource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FairSource</a>, and the <a href="https://mastodon.nzoss.nz/tags/commonsclause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a>, <a href="https://mastodon.nzoss.nz/tags/licensezero" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LicenseZero</a> is yet another attempt at mususing the term <a href="https://mastodon.nzoss.nz/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> to describe the software license equivalent of the <a href="https://mastodon.nzoss.nz/tags/nocommercialuse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NoCommercialUse</a> licenses in the <a href="https://mastodon.nzoss.nz/tags/creativecommons" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CreativeCommons</a> suite: <a href="https://licensezero.com/" rel="nofollow noopener noreferrer" target="_blank">https://licensezero.com/</a>

Dr. Roy Schestowitz (罗伊)<a class="hashtag" href="https://pleroma.site/tag/redis" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> Labs and the tragedy of the <a class="hashtag" href="https://pleroma.site/tag/commonsclause" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> <a href="https://media.libreplanet.org/u/libreplanet/m/redis-labs-and-the-tragedy-of-the-commons-clause-b4d1/" rel="nofollow noopener noreferrer" target="_blank">https://media.libreplanet.org/u/libreplanet/m/redis-labs-and-the-tragedy-of-the-commons-clause-b4d1/</a>

Strypey<a href="https://hitchhiker.social/@djsumdog" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@djsumdog</a> true, there is the <a href="https://mastodon.nzoss.nz/tags/commonsclause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a>, and the use of the <a href="https://mastodon.nzoss.nz/tags/peerproductionlicense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PeerProductionLicense</a> on software, both of which are motivated by similar concerns to the NC license, but I would argue they have very different implications (I know <a href="https://social.coop/@wolftune" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@wolftune</a> disagrees with that, but there you go) <a href="https://freeradical.zone/@CharredStencil" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@CharredStencil</a> <a href="https://vampire.estate/users/LWFlouisa" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@LWFlouisa</a>

StrypeyA sober analysis of the <a href="https://mastodon.nzoss.nz/tags/commonsclause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> license from a business perspective. Applying the # <a href="https://redmonk.com/sogrady/2018/09/10/tragedy-of-the-commons-clause/" rel="nofollow noopener noreferrer" target="_blank">https://redmonk.com/sogrady/2018/09/10/tragedy-of-the-commons-clause/</a>

Dr. Roy Schestowitz (罗伊)Free Software Foundation updates their licensing materials, adds <a href="https://pleroma.site/tag/commonsclause" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> and <a href="https://pleroma.site/tag/fraunhofer" rel="nofollow noopener noreferrer" target="_blank">#Fraunhofer</a> FDK AAC license <a href="https://hub.packtpub.com/free-software-foundation-updates-their-licensing-materials-adds-commons-clause-and-fraunhofer-fdk-aac-license/" rel="nofollow noopener noreferrer" target="_blank">https://hub.packtpub.com/free-software-foundation-updates-their-licensing-materials-adds-commons-clause-and-fraunhofer-fdk-aac-license/</a>

Dr. Roy Schestowitz (罗伊)<a href="https://pleroma.site/tag/gpl" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> Licensing: <a href="https://pleroma.site/tag/fsf" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> Update Rules <a href="https://pleroma.site/tag/commonsclause" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> Non-Free, <a href="https://pleroma.site/tag/redhat" rel="nofollow noopener noreferrer" target="_blank">#RedHat</a> on Compliance <a href="http://www.tuxmachines.org/node/117372" rel="nofollow noopener noreferrer" target="_blank">http://www.tuxmachines.org/node/117372</a>

Dr. Roy Schestowitz (罗伊)<a href="https://pleroma.site/tag/fsf" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> Update Rules <a href="https://pleroma.site/tag/commonsclause" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> <a href="https://pleroma.site/tag/nonfree" rel="nofollow noopener noreferrer" target="_blank">#NonFree</a> <a href="https://www.i-programmer.info/news/136-open-source/12289-fsf-commons-clause-no.html" rel="nofollow noopener noreferrer" target="_blank">https://www.i-programmer.info/news/136-open-source/12289-fsf-commons-clause-no.html</a> a threat to <a href="https://pleroma.site/tag/copyleft" rel="nofollow noopener noreferrer" target="_blank">#copyleft</a> mantra

Dr. Roy Schestowitz (罗伊)<a href="https://pleroma.site/tag/copyleft" rel="nofollow noopener noreferrer" target="_blank">#Copyleft</a> Licensing: <a href="https://pleroma.site/tag/gpl" rel="nofollow noopener noreferrer" target="_blank">#GPL</a> Initiative, Free Software Directory, <a href="https://pleroma.site/tag/fsf" rel="nofollow noopener noreferrer" target="_blank">#FSF</a> Policy on <a href="https://pleroma.site/tag/commonsclause" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> etc. <a href="http://www.tuxmachines.org/node/117257" rel="nofollow noopener noreferrer" target="_blank">http://www.tuxmachines.org/node/117257</a> <a href="https://pleroma.site/tag/gnu" rel="nofollow noopener noreferrer" target="_blank">#gnu</a> <a href="https://pleroma.site/tag/freesw" rel="nofollow noopener noreferrer" target="_blank">#freesw</a>

Dr. Roy Schestowitz (罗伊)FSF: "We added the <a href="https://pleroma.site/tag/commonsclause" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> to our list of nonfree licenses. Not a stand-alone license in and of itself, it is meant to be added to an existing free license to prevent using the work commercially" <a href="https://www.fsf.org/blogs/licensing/recent-licensing-updates" rel="nofollow noopener noreferrer" target="_blank">https://www.fsf.org/blogs/licensing/recent-licensing-updates</a>

StrypeySome thoughts on the <a href="https://mastodon.nzoss.nz/tags/commonwashing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonWashing</a> that is the <a href="https://mastodon.nzoss.nz/tags/commonsclause" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> license, put together by <a href="https://mastodon.nzoss.nz/tags/bradlykuhn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BradlyKuhn</a>: <a href="https://sfconservancy.org/blog/2018/aug/22/commons-clause/" rel="nofollow noopener noreferrer" target="_blank">https://sfconservancy.org/blog/2018/aug/22/commons-clause/</a>

Dr. Roy Schestowitz (罗伊)<a href="https://pleroma.site/tag/mongodb" rel="nofollow noopener noreferrer" target="_blank">#MongoDB</a> Becomes More Affero GPL-Like <a href="http://www.tuxmachines.org/node/116533" rel="nofollow noopener noreferrer" target="_blank">http://www.tuxmachines.org/node/116533</a> nothing like <a href="https://pleroma.site/tag/redis" rel="nofollow noopener noreferrer" target="_blank">#redis</a> and <a href="https://pleroma.site/tag/commonsclause" rel="nofollow noopener noreferrer" target="_blank">#commonsClause</a> <a href="https://commonsclause.com/" rel="nofollow noopener noreferrer" target="_blank">https://commonsclause.com/</a>

Dr. Roy Schestowitz (罗伊)<a href="https://pleroma.site/tag/debian" rel="nofollow noopener noreferrer" target="_blank">#Debian</a> dev forks <a href="https://pleroma.site/tag/redis" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> modules that are under <a href="https://pleroma.site/tag/commonsclause" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> licence <a href="http://www.tuxmachines.org/node/116453" rel="nofollow noopener noreferrer" target="_blank">http://www.tuxmachines.org/node/116453</a>

Dr. Roy Schestowitz (罗伊)OSS: <a href="https://pleroma.site/tag/rms" rel="nofollow noopener noreferrer" target="_blank">#RMS</a> on <a href="https://pleroma.site/tag/commonsclause" rel="nofollow noopener noreferrer" target="_blank">#CommonsClause</a> , Customer Conversations Changing in Era of Open Source, <a href="https://pleroma.site/tag/sourcegraph" rel="nofollow noopener noreferrer" target="_blank">#Sourcegraph</a> Liberated <a href="http://www.tuxmachines.org/node/116162" rel="nofollow noopener noreferrer" target="_blank">http://www.tuxmachines.org/node/116162</a>

Aaron Wolf<a href="https://ecodigital.social/@adfeno" class="u-url mention">@adfeno</a> <a href="https://mastodon.nzoss.nz/@strypey" class="u-url mention">@strypey</a> <a href="https://social.coop/@snowdrift" class="u-url mention">@snowdrift</a> I agree, those non-FLO incompatible terms are problematic. I/we support *neither*. But do notice that <a href="https://social.coop/tags/CommonsClause" class="mention hashtag" rel="tag">#CommonsClause</a> and <a href="https://social.coop/tags/Copyfarleft" class="mention hashtag" rel="tag">#Copyfarleft</a> are at least different motivations. The former is meant specifically to *encourage* and enable proprietary licensing (while still having FLO something), while the latter is *sometimes* used by those who would like to offer the capitalists nothing at all, not even via a proprietary license.But either harms the FLO commons we have.

Recent searches

Search options

Administered by:

Server stats:

#commonsclause