Conversation

Personal opinion: the Commons Clause does damage to Free And #OpenSource Software communities, and it will continue to do so until archives the GitHub project and adds a warning to the website about the hazards it brings.
Quote Tweet
Coldcard changed its firmware license from GPLv3 to MIT+Commons Clause. Considering @fsf and @OpenSourceOrg definitions, @COLDCARDwallet is not anymore #OpenSource, or is it? 1/ In this B-side of the spanish #L123's @nvk answers me that and much more bit.ly/L123B_Coldcard
Show this thread
Embedded video
2:13
4.3K views
2
17
I went and read the terms of the Commons Clause, because I keep hearing about it. It appears to be designed explicitly to transition OSS projects away to a "source-available" licensing model. I guess it's easier to add a clause to an existing license instead of writing a new one
1
What's particularly interesting is that it clearly states it is not an OSS license, and that it should be qualified as a "source-available license". The right to sell is restricted, but mostly if you sell the software as-is, similar to UI component libraries commercial licensing
1
I agree with you, AGPLv3 + dual-licensing really has nothing to do with the spirit of free software, it's really used as a tool to keep one company in a position where they can do more than their competitors with the code. It could honestly be considered "source-available"
2
1
It doesn't restrict use in any way. It just comes with obligations upon some triggering conditions (e.g, distribution, creating derivative works). But you're free to use the software any way you wish (as an end-user). You just need to give others the same freedom you were given.
1
It does heavily restrict usage as an end user. The users of source code are developers, and it heavily restricts what they can do with it including mixing it with actual free software without the same usage restrictions. GPL is non-free software, based on their own definition.
1
5
Show replies
Restrictive GPL licensing naturally turns into these non-commercial licenses. Saying some restrictions are good because you agree with the intent but other restrictions are bad because you don't agree with the intent doesn't change that it's heavily restricting usage either way.
1
You are only "restricted" from making the software proprietary (i.e., not give others the permissions you were given).
Quote Tweet
Replying to @wewegomb and @alyssarzg
The GPL is completely business friendly, so long as business objectives are compatible with Free Software objectives. The GPL has created virtually impossible-to-measure business value by unencumbering businesses, as software users, from the restrictions of proprietary licensing.
2
1
Show replies