Talk:Affero General Public License

message: I am not completely sure why we have separate pages for the old AGPL and the new AGPLv3 that was recently released by the FSF.  We should figure out if we want to merge them.  I am not completely sure myself how to start that process, but I wanted to mention it here. -- bkuhn 21:30, 24 November 2007 (UTC)
replies: text: Please, read the GNU Affero General Public License 3.0 Preamble’s penultimate paragraph, and revert the merge. --AVRS (talk) 14:41, 28 November 2007 (UTC)
replies: text: I understood this before I did the merge.  The distinction is not notable, so two articles are not needed.  It is far better for Wikipedia and it's readers, for there to be one article that explains the evolution of the concept, and the evolution of the license(s).  We're an encylopedia, not a legal glossary. There are many editors who would propose making this merged article, a section of the GPL article, for the same reasons. Work on making the merged article, the best WP article it can be.  Lentower (talk) 15:22, 28 November 2007 (UTC)
replies: text: I think the article should still be called “GNU Affero General Public License”, because that’s what it describes, and that is what seems to be more notable now. --AVRS (talk) 15:51, 28 November 2007 (UTC)
replies: text: See the talk page for the other article that is now a REDIRECT for why i did the merge this way.  The merged article is findable by both titles, describes both licenses.   Perhaps the descriptions can be improved. Few but a lawyer or a GNU partisian will see a meaningful or WPnotable difference between them. Lentower (talk) 16:09, 28 November 2007 (UTC)
thread_title:  Two pages for Affero license? 

message: I did the merge.  I left the other newer article, the REDIRECT. Lentower (talk) 04:34, 25 November 2007 (UTC)
replies: text: Please, read the GNU Affero General Public License 3.0 Preamble’s penultimate paragraph, and revert the merge. --AVRS (talk) 14:41, 28 November 2007 (UTC)
replies: text: I understood this before I did the merge.  The distinction is not notable, so two articles are not needed.  It is far better for Wikipedia and it's readers, for there to be one article that explains the evolution of the concept, and the evolution of the license(s).  We're an encylopedia, not a legal glossary. There are many editors who would propose making this merged article, a section of the GPL article, for the same reasons. Work on making the merged article, the best WP article it can be.  Lentower (talk) 15:22, 28 November 2007 (UTC)
replies: text: I think the article should still be called “GNU Affero General Public License”, because that’s what it describes, and that is what seems to be more notable now. --AVRS (talk) 15:51, 28 November 2007 (UTC)
replies: text: See the talk page for the other article that is now a REDIRECT for why i did the merge this way.  The merged article is findable by both titles, describes both licenses.   Perhaps the descriptions can be improved. Few but a lawyer or a GNU partisian will see a meaningful or WPnotable difference between them. Lentower (talk) 16:09, 28 November 2007 (UTC)
thread_title: Merge done

message: This is a fantastic article and one of the best resources on the AGPL available. Thanks to everyone who has helped contribute to this! —mako๛ 19:31, 14 January 2008 (UTC)
thread_title:  Great Article 

message: «Note that GNU Affero General Public License is not the same legal document as the Affero General Public License, though they are quite similar in intent and effect.»
Either that is wrong, or the whole article needs to be rewritten. The page is titled "AGPL", the heading section is all about "GNU AGPL" but ends with the mentioned sentence, and the remainder of the article seems to say both are the same. If someone could clear it up and correct it... thanks. ;)
--portugal (talk) 14:39, 19 February 2008 (UTC)
replies: text: It is my understanding that the AGPL is essentially being replaced by the GNU AGPL, seeing as how Affero has updated their AGPL precisely to make it compatible with the GNU AGPL. The title probably should be renamed to GNU Affero General Public License. MahangaTalk 06:56, 23 February 2008 (UTC)
replies: text: This is a very confusingly-written article. I have made some changes designed to clear up some of the confusion between the old AGPL and the FSF's GNU AGPLv3 published in 2007.  Much more work is needed here. Rfontana (talk) 20:57, 15 July 2008 (UTC)
replies: text: I have now made a number of changes to this article to make it clearer and less confusing. Rfontana (talk) 19:13, 16 July 2008 (UTC)
thread_title:  AGPL vs GNU AGPL - same or not? 

message: Sorry, Rfont, this is still confusing as hell. The intro realllly needs a simple summary of what it is. The fact that the FSF suggests people use it isn't nearly enough. I'm trying to use this in some software..but I'm not really sure why.
Miserlou (talk) 05:19, 29 July 2008 (UTC)
replies: text: "Application service provider loophole." Que??! Miserlou (talk) 03:48, 31 July 2008 (UTC)

text: The AGPL v1 is not GNU. The AGPL v2 is for compatibility to GNU AGPL v3. The AGPL v3 is GNU. AGPLv1 was published by Affero. The AGPLv3 was published by GNU. - The articles have been merged now. Please check if you still find it confusing. Kissaki (talk) 10:41, 26 February 2024 (UTC)
thread_title: Confusing

message: If nobody is sure what the loophole is, how could they have a licence exist to stop it?
--99.250.177.248 (talk) 23:00, 25 October 2008 (UTC)
replies: text: I assume this has been resolved through better text by now? Kissaki (talk) 10:42, 26 February 2024 (UTC)
thread_title:  Loophole 

message: Technically speaking, version 1 sounds like it forbids opting-out of having a "download source" link:
But version 3 sounds like it actually forces one to actively program a "download source" link, if one doesn't already exist:
Is it really so? Does it mean v3 users - if their modifications include network interaction - aren't allowed to use the linkless original source as-is? Must they build a whole sub-program to present the source? Again, I'm only talking about programs that don't have such a link to begin with. -79.176.200.211 (talk) 20:44, 16 April 2010 (UTC)
thread_title:  Opt-in download source vs. Opt-out 

message: The table should be expanded to include the transitional license. 65.94.47.63 (talk) 03:06, 3 July 2011 (UTC)
thread_title:  AGPL2 

message: This list is a Bad Idea. I hesitate to delete it all since it might include notable examples of AGPL software, but this ever growing list need to be addressed soon. Belorn (talk) 19:43, 11 November 2011 (UTC)
replies: text: Rewrote it in same style as Free_software#Examples_of_free_software. Belorn (talk) 17:38, 12 November 2011 (UTC)
thread_title:  Example of web applications under AGPL 

message: The note at the top is wrong. It says AGPL redirects to this article, but it doesn't. Looks like that page was speedied last month. Ntsimp (talk) 15:25, 14 January 2012 (UTC)
thread_title:  Hatnote 

message: The part about Opa's standard library license is wrong or outdated. From the Opa FAQ:
"The Opa Compiler which is licensed with the Affero GPL and the Opa Standard Library which is licensed with the MIT License. As a result, you can use Opa to build any application you want, either open source or proprietary."  — Preceding unsigned comment added by 194.206.149.138 (talk) 13:56, 3 October 2012 (UTC)
thread_title:  Opa description - wrong or outdated 

message: Would be useful to compare/contrast AGPL vs normal GPL
12.167.60.2 (talk) 18:39, 14 November 2013 (UTC)
thread_title:  Difference section 

message: The MongoDB database is under AGP: "The goal of the server license is to require that enhancements to MongoDB be released to the community. Traditional GPL often does not achieve this anymore as a huge amount of software runs in the cloud. For example, Google has no obligation to release their improvements to the MySQL kernel – if they do they are being nice.
To make the above practical, we promise that your client application which uses the database is a separate work. To facilitate this, the mongodb.org supported drivers (the part you link with your application) are released under Apache license, which is copyleft free."
I assumed the AGPL would only apply to the networked software in a restricted sense (but not sure any more), like the web-application. You usually would not have the database, MongoDB or otherwise, accessible to the Internet.
Let's assume the web application itself is not under AGPL. Then it needs not provide the source code for it. However the less likely software to be changed, MongoDB, still has to provide source if changed (and only then it seems)? The GPL, and copyright in general works for derived software, and it is delimited on a process boundary. If the same applies to AGPL as for the GPL then it would not fully close the "network loophole". Would you have to provide the source (then changed) to that process or all that it might use directly or indirectly? I guess not. If however you need to provide source for processes used by a changed APGL software, where would it end?
Let's say the web application is under AGPL, then the source code for it but also the database schema (not the data nor the database source code) would have to be provided? PHP and Apache, if changed? Would not fall under a "system exception"? comp.arch (talk) 13:17, 2 April 2014 (UTC)
replies: text: Wikipedia talk pages are not the best place to ask for legal advice, and your are much more likely to get a better reply by asking stackoverflow. That said... AGPL is a relative new license. This mean that legal praxis is not yet built, so a judge would ask what was the intention of the MongoDB authors in picking the license. The judge would also look at how the accused infringer used the software, and reason if the usage intentionally tries to circumvent the authors wishes. So in the case of mongodb, the authors has made their intention public. they say: "To say this another way: if you modify the core database source code, the goal is that you have to contribute those modifications back to the community. Note however that it is NOT required that applications using mongo be published.  The copyleft applies only to the mongod and mongos database programs.". Belorn (talk) 14:29, 2 April 2014 (UTC)
replies: text: Yes I know. I just wandered what would happen in the general case where the software is only indirectly accessible over the Internet. I made it look as the web application is the first software, but that is of course no the case. There is the TCP/IP stack, probably Apache, PHP. (Could be some terminal server software/X Windows in between.) If the drivers for MongoDB would have used AGPL it would apply to all the web application probably (and possibly even without if not specifically not indicated otherwise as they do). comp.arch (talk) 17:34, 2 April 2014 (UTC)
thread_title:  Database AGPL (and possibly schema) with/without AGPL webserver, and system exception 

message: Hello fellow Wikipedians,
I have just modified 2 external links on Affero General Public License. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20080315231323/http://www.softwarefreedom.org/technology/blog/2007/nov/21/stet-and-agplv3/ to http://www.softwarefreedom.org/technology/blog/2007/nov/21/stet-and-agplv3/
*Added archive https://web.archive.org/web/20000815065020/https://www.gnu.org/philosophy/license-list.html to https://www.gnu.org/philosophy/license-list.html
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 14:48, 27 June 2017 (UTC)
thread_title:  External links modified