I would understand if Canonical want a new cow to milk, but why are developers even agreeing to this? Are they out of their minds?? Do they actually want companies to steal their code? Or is this some reverse-uno move I don’t see yet? I cannot fathom any FOSS project not using the AGPL anymore. It’s like they’re painting their faces with “here, take my stuff and don’t contribute anything back, that’s totally fine”
Sorry, I’m not much of a software dev so bear with me:
If the libraries are GPL licensed, is there a problem? Unless you’re editing the libraries themselves.
Now if the application is GPL licensed and you’re adding functionality to use other libraries, please push upstream. It helps the community and the author will more likely than not be happy to receive it
Any linking against GPL software requires you to also release your source code under GPL.
ALGPL allows you to link to it dynamically without relicensing, but as explained, there are platforms where dynamic linking isn’t an option, which means these libraries can’t be used if one doesn’t want to provideALGPL licensed source code of their own product.You mean LGPL when you say AGPL, right?
Yes, sorry
Using a GPL library will require you to re-license your entire project as GPL, regardless of whether you made a change or not.
LGPL is a bit better, because it allows you to dynamically link the library. But you’re required to provide a copy of source for the library, and any users must be able to swap the built library with their own copy.
Eg; you can use an AGPL-licensed .dll in your closed-source windows program, because users can swap that .dll easily.
You can’t do the same for a ps5 game because users aren’t able to replace any files that the game uses.