#gpl
These are public posts tagged with #gpl. You can interact with them if you have an account anywhere in the fediverse.
The dedication of @rms to the GNU project and his work on copyleft licenses have made a profound impact on the software world. Through the GPL, RMS has ensured that software users retain essential freedoms - freedoms to use, study, change and share. #FreeSoftware #SoftwareFreedom #GPL #Copyleft
Mathe-Ass hat jetzt Sparklines pro Level für eure Zeiten:
https://www.draketo.de/anderes/mathe-ass
»Löse die Aufgaben und steige Stufen auf. Knacke deine Zeiten«
Den zweiten Teil unterstützt es hiermit jetzt besser.
Um in Level 1 das Maximum zu erreichen, müsst ihr unter 2 Sekunden kommen 
Mathe-Ass ist #FreieSoftware unter #GPL, die Quellen sind komplett in https://hg.sr.ht/~arnebab/draketo/browse/anderes/mathe-ass.org
Have questions about possible violations of #GNU licenses? We have answers! Check out all the questions and answers on our FAQ page at https://u.fsf.org/3kx #GPL
What if I discover a possible violation of the GPL? "You should report it. First, check the facts as best you can. Then tell the publisher or copyright holder of the specific GPL-covered program." Read the full answer https://u.fsf.org/3ks #GNUGPLFAQ #GPL
so, uh, the GPL's text proposes that an interactive-mode program should display something like this when starting up:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type "show w".
This is free software, and you are welcome to redistribute it under certain conditions; type "show c" for details.
and i just realized that this is awfully similar to the way GDB's interface works. the notice is different, and the commands are show copying and show warranty instead, but you can see how the two are related.
if anything, this makes me think that the text used in the GPL might have been taken from an earlier version of GDB, back when show had fewer possible parameters and it was possible to unambiguously assign show c and show w to "show the program's license" and "show the warranty info"...
@bkuhn any advice for choosing #copyleft #licenses for #Rust code?
In a recent thread you mentioned #LGPL and I'm curious about templating.
In my understanding it's not possible for the user to replace just the LGPLd library on their system, so it's effectively the same as #GPL .
I chose #MPL 2.0 instead.
Same problem exists in C++ template-only libraries, but I found no ultimate guide.
Are you aware of any?
How do I use GNU licenses for my own software? We are glad you asked! Please see our "GPL how to" page for the full answer and thank you for making the ethical choice! https://u.fsf.org/2b5 #GPL
@t3rr0rz0n3 Three of those apply equally to the #GNU #GPL, so not sure what point you are trying to make.
The GNU GPL does not disallow use in proprietary software, there is no obligation to share anything, and companies (and anyone) can profit without giving back.
Don T3rr0r 
@t3rr0rz0n3@xarxa.cloud
Using the MIT license might seem like a good idea, but:
Allows your code to be used in proprietary software No obligation to share improvements Companies can profit without giving back Doesn’t protect user freedom
If you want your code to stay free: use GPL.
I have wanted to use the #collaboraonline online office suite for my online Office suite for a long time.
After a lot of experime
ntation and learning I have it working on my self hosted #Nextcloud and it does what I want and seems responsive. However one of the big learning points is that most of my online writing requirements are met with the built in #markdown editor.
What if I discover a possible violation of the GPL? "You should report it. First, check the facts as best you can. Then tell the publisher or copyright holder of the specific GPL-covered program." Read the full answer https://u.fsf.org/3ks #GNUGPLFAQ #GPL
You all have the right to write #FreeSoftware, and you write whatever you want.
And when you look at what software other people are writing, keep it in mind, that they have the right to write whatever software they feel like.
They even have all rights to license it under #MIT or #BSD licenses, because everyone has the right to make objectively wrong decisions, too 
https://www.reddit.com/r/linux/comments/1jjo1hv/a_tremendous_feature_of_open_source_software_is/
Don T3rr0r @t3rr0rz0n3@xarxa.cloudWe're gonna be doing one thing, and one thing only. Killing @ubuntu.
# @cr0n0s@social.tchncs.deOh vaya, si que el tema Ubuntu + Rust, si que va traer cola para rato. Licencias, GPL/MIT,. ¿Generara cambios radicales en distintas aplicaciones coreutils (GNU)? ¿Porque no usar Rust, manteniendo las licencias GPL actuales?
Lo más seguro, distros basadas en Ubuntu, tendrán que continuar la ola. ¿Debian como reaccionara,...?
Sin duda estara de candela. Atentos.
@rod2ik@mastodon.social
Canonical prepara una transformación importante en…
Computer HoyLa rivoluzione di Ubuntu: addio a GNU/Linux - Tom's Hardware
Abbandonare la #GPL sarà un grosso problema
https://www.tomshw.it/hardware/la-rivoluzione-di-ubuntu-addio-a-gnulinux-2025-03-22
La rivoluzione di Ubuntu: da GNU/Linux a Rust/Linux,…
Tom's HardwareIn 1989, we published the GNU #GPL. It is at the core of #SoftwareFreedom and it protects users' rights to run, copy, modify, and share. Read more about #FreeSoftware licensing https://www.fsf.org/licensing
Although It pains me to find there are #bugs in my code, it also thrills me to get a well explained issue created and I like to add the names of the people reporting to the readme, which you can see here.
https://github.com/marcusgreen/moodle-qtype_gapfill/blob/master/changelog.md
For me it illustrates how Free/Libre #GPL licensed software can be collaboratve. I would never have known about this problem if that issue had not been filed.
Fill in the blanks question type with very easy to…
GitHubIn 1989, we published the GNU #GPL. It is at the core of #SoftwareFreedom and it protects users' rights to run, copy, modify, and share. Read more about #FreeSoftware licensing https://www.fsf.org/licensing
