Re:Code licensed under the AGPL must not be used at Google
by rapnie on Wednesday April 27, 2022 @01:20AM
(#31176604)
AFAIU there's no obligation to contribute upstream at all, just the need to provide the source such that anyone who wants to can contribute upstream. So you can't grab the code in your SaaS and extend it without making it available to the public.
For example the Truth Social was briefly in violation of AGPL when they took and adapted the Mastodon source code. Later on they provided a zip-file with the codes in it.
Re:Code licensed under the AGPL must not be used at Google
by hardwaresofton on Wednesday April 27, 2022 @01:29AM
(#31176654)
Thanks for this correction, updated the comment!
Re:Code licensed under the AGPL must not be used at Google
by josephcsible on Wednesday April 27, 2022 @01:19AM
(#31176597)
The AGPL just forces you to make the source code of your changes available under itself. There's no obligation to get them merged upstream.
Re:Code licensed under the AGPL must not be used at Google
by hardwaresofton on Wednesday April 27, 2022 @01:29AM
(#31176651)
Thanks for this correction, updated the comment!
The people it punishes are those who modify software but don't contribute changes back upstream.
See the FSF article (https://www.fsf.org/bulletin/2021/fall/the-fundamentals-of-t... ), reproduced below:
> Simply put, the AGPLv3 is effectively the GPLv3, but with an additional licensing term that ensures that users who interact over a network with modified versions of the program can receive the source code for that program. In both licenses, sections four through six provide the terms that give users the right to receive the source code of a program. These terms cover the distribution of verbatim or modified source code as well as compiled executable binaries. However, they only apply when a program is distributed, or more specifically, conveyed to a recipient. Using a program over a network is not "conveying." It is important to note that this only applies to the code running on the server, and not for example to the JavaScript programs that your browser may download and run locally — these are conveyed to you.
Some discussion a while back: https://news.ycombinator.com/item?id=30952949
[EDIT] - Altered the initial description, there's no requirement to merge upstream, just to make the code available!