@eloy @creativecommons because it being part of a #Software is different than being standalone artwork.
- #GPL doesn't even demand #ReproduceableBuilds!
@eloy @creativecommons because it being part of a #Software is different than being standalone artwork.
This is just a quick public service announcement regarding my cybersecurity interests (and workflow). Under a system of #Rust evangelism, I will not be able to continue my #cybersecurity focus, nor will #InfoSec be able to thrive as a community. If you can convince the Rust team to convert to the #GPL or to another copyleft license, then my workflow can return to normal.
مشروع REUSE: تبسيط تراخيص البرمجيات الحرة
#تراخيص_البرمجيات_الحرة #رخص_البرمجيات #license #GPL #GNU #GNUTUX #FOSS #FREESOFTWARE #LINUX #BSD #MIT
I wonder if #GPL or #LGPL would make sense for #machinelearning models. As someone who wants to be a pioneer in #opensourceai I should consider reading and researching more about these topics.
Hot Take: The misinformation about the SSPL needs to stop.
If you disagree with the SSPL, that's fine.
But if you argue against what you think what the SSPL is, rather than what it actually is, you are actively harming the FOSS community.
The SSPL is based on the AGPL (Edit: It's actually based on the GPLv3). MongoDB (the company) has a nice little difference PDF that you can read. https://webassets.mongodb.com/_com_assets/legal/SSPL-compared-to-AGPL.pdf
The OSI says the SSPL is not Open Source. I understand their reasoning, and that's their prerogative. But I think this call was more harmful than it was beneficial.
The FSF said they'd look into the SSPL and make a comment, it's been a long while and they've been silent on the matter. Claims that the SSPL is not a Free Software license are false. Note that I'm also not making a claim that the SSPL is a Free Software license, because that equally lacks evidence.
I appreciate that people *really* do not like the requirements for Section 13. That's fine, if that's your beef with the SSPL, then say that instead of spreading falsities. I *really* don't like it when software fails to provide Freedom 3. I prefer copyleft licenses over permissive licenses. Some people prefer licenses that allow people to close the source later, I disagree with that.
Can we please just argue against realities, instead of fantasies? Thank you.
I stumbled upon yet another #software license discussion, and it seems that people have a hard time with this.
So I felt that I should write a simple overview/guide to choosing a license.
https://distractedmind.home.blog/2025/05/02/licenses-are-boring-but-you-really-need-one/
Ah yes, code scanners.
~It's not me trying to steal your work and undermine your workers rights you understand. It's the machine that demands it.~
If my code license offends you, remove my code. I have no business making it popular, only useful under the terms.
@funnelfiasco Still remember #OSCON 2013 when #GitHub keynote proudly proclaimed #GPL as the "least free" OSS license or something like that.
@federicobonfiglio ma la questione **NON** è l'uso di Rust!
Non si rendono conto che abbandonare le licenze persistenti, pensate per salvaguardare la libertà alla lunga sarà estremamente **dannoso**. L'esempio di BSD è lampante: spesso tecnicamente ottimo, quasi sempre "saccheggiato" da egoisti che non rendono nulla alla società. La #GPL incentiva la cooperazione (**anche** commerciale!) mentre le BSD favoriscono gli egoisti.
真的有人寄信要 GPL 授權的 copy...
Hacker News 上看到 2022 年的文章:「I wrote to the address in the GPLv2 license notice (2022) (mendhak.com)」,原文在「I wrote to the address in the GPLv2 license notice and received the GPLv3 license」。 作者在 GPLv2 看到這段: You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 5…
Moodle HQ is hiring they are looking for
36 new engineers
5 new #UX designers & 4 new Product designers
16 specialist roles in #accessibility documentation, DevOps & more
6 new leadership positions
@cferdinandi The Expat license allows for exactly the same things the GNU GPL does, which is what makes them compatible. E.g., a non-commercial software license would not be compatible with the #GNU #GPL since it limits how you can use a program, something the GNU GPL does not.
@cferdinandi @mav > As a result, GPL and MIT code are incompatible together.
That is not correct. The #GNU #GPL and “MIT” (Expat license) are compatible.
What's everyone's view on the #EUPL compared to the #GPL? I read thru it and my impression is that the EUPL achieves most of the same things as the GPL but with much less convoluted language, and written by EU lawyers rather than #FOSS activists which instills confidence.
This part feels a bit weird tho: "The Licensee must cause any Derivative Work to carry prominent notices stating that the Work has been modified and the date of modification." What's "prominent"?
#law #OpenSource #programming
@CuratedHackerNews it's me or many #rust programs don't use #gpl as license but less restrictive ones?
The GPL isn't just a license, it's a chain of custody for freedom. Unlike permissive MIT/BSD, that let corporations privatize code into closed ecosystems, GPL's ‘copyleft’ binds derivatives to openness, ensuring every user inherits the right to study, modify, and share.
Permissive licenses enable enclosure of the digital commons while GPL defends them. When code stays open, we retain collective sovereignty over the tools shaping society.
Sometimes I see @alternativeto pushing quite a lot of commercial software and wonder about the perceived shift of perspective.
#CAD #CAM for example: Artsoft's Mach3 & Mach4 are listed separately as controllers, but not the #FreeSoftware #OpenSouce alternative #UGS?! Even #YouTube is better in the case of #CNC since the existence of #UniversalGCODEsender isn't censored (like covid).
Please, stop the progress of #enshitification and save the much appreciated website with more #GPL alternatives. TY