What does it mean to say that two licenses are "compatible?" Read the answer on our #GPLFAQ page: https://u.fsf.org/3wl #GPL
u.fsf.orgFrequently Asked Questions about the GNU Licenses
- GNU Project - Free Software Foundation
Recent searches
Search options
Administered by:
#gpl
16 posts11 participants2 posts today
What does it mean to say that two licenses are "compatible?" Read the answer on our #GPLFAQ page: https://u.fsf.org/3wl #GPL
u.fsf.orgFrequently Asked Questions about the GNU Licenses
- GNU Project - Free Software Foundation
→ Une #intelligence #artificielle libre est-elle possible ?
https://linuxfr.org/news/une-intelligence-artificielle-libre-est-elle-possible#toc-le-r%25C3%25A9seau-de-neurones
« Posons-nous un instant la question : qu’est-ce que le #code #source d’un réseau de #neurones ? […] La #GPL fournit une définition : le code source est la forme de l’œuvre privilégiée pour effectuer des #modifications. Dans cette acception, le code source d’un réseau de neurones serait l’#algorithme d’entraînement, le réseau de neurones de départ et le #corpus sur lequel le réseau a été entraîné »
linuxfr.orgUne intelligence artificielle libre est-elle possible ? - LinuxFr.orgL’actualité du logiciel libre et des sujets voisins (DIY, Open Hardware, Open Data, les Communs, etc.), sur un site francophone contributif géré par une équipe bénévole par et pour des libristes enthousiastes
I am doing a webinar tomorrow on "Maths Education with the #Moodle STACK Question Type"
https://moodle.academy/calendar/view.php?view=day&course=1&time=1743494400#event_26872
I had made a short video to promote it but my colleague at @catalysteu took the mp4 and tightened it up rather nicely
This is the service we offer (but its all #GPL)
+ 
#licesing question.
People share (a)gpl code on github. Github is not available everywhere (even read access I think).
Does that break the GPL?
"...must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software"
(AGPL 3, section 13)
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
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
u.fsf.orgFrequently Asked Questions about the GNU Licenses
- GNU Project - Free Software Foundation
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
u.fsf.orgFrequently Asked Questions about the GNU Licenses
- GNU Project - Free Software Foundation
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"...
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
u.fsf.orgHow to Use GNU Licenses for Your Own Software
- GNU Project - Free Software Foundation
Replied to #
Don T3rr0r 
Don T3rr0r 
@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.
Replied in thread
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.
Replied to Greg
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
u.fsf.orgFrequently Asked Questions about the GNU Licenses
- GNU Project - Free Software Foundation
We're gonna be doing one thing, and one thing only. Killing @ubuntu.
# Oh 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.
Computer Hoy · Giro de 180 grados en Linux, revolución en Ubuntu que dice adiós para siempre a GNU/LinuxCanonical prepara una transformación importante en su sistema operativo de código abierto, con el objetivo de reforzar la seguridad y optimizar el rendimiento de Ubuntu.
Giro de 180 grados en #Linux, revolución en #Ubuntu que dice adiós para siempre a los utilitarios #coreutils , desarrollados en lenguaje #C, y licencia #GPL, de #GNU/Linux para remplazarlos por utilitarios en licencia #MIT , desarrollados en #Rust
computerhoy.20minutos.es/tecnologia/g...
Giro de 180 grados en Linux, r...
Bluesky SocialBluesky
When people release something under #GPL usually they just drop a text-copy of the license in the root folder under LICENSE. But I am looking at the license and it ends with a section "How to Apply These Terms to Your New Programs" which I think should actually be omitted? It's not the license to the software, it's more like advertising for the license itself, or instructions to the user. Is that right? Can this appendix be elided from the software distribution?
