Skip to Content
Last modified by chrisby on 2025/01/11 10:03
From version 2.124
edited by chrisby
on 2025/01/11 09:56
Change comment: There is no comment for this version
To version 2.125
edited by chrisby
on 2025/01/11 09:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -47,7 +47,7 @@
47 47  
48 48  **Copyleft Licenses**
49 49  
50 -To address problems with proprietary software, the FSF promotes copyleft licenses, such as the AGPL, which require that any derivative works remain under the same license.
50 +To address problems with proprietary software, the FSF promotes copyleft licenses, such as the AGPL, which require that any derivative works remain under the same license. The basic idea is to say, when you use and take advantage of the open source ecosystem, it is fair to oblige you to contribute back to
51 51  
52 52  The term "derivative work" is somewhat vague in legal terms, but a common interpretation is that software that depends on AGPL code to function is a derivative work. For example, if a project directly incorporates AGPL source code or relies on an AGPL library, it must adopt the AGPL license for its entire code base. Similarly, if software calls an external AGPL service over a network and the service is purely optional, the software is not considered a derivative work. However, if the service is essential and the software won't work without it, even if the AGPL code is hosted externally, the software is still considered a derivative work. Therefore, attempting to "work around" the AGPL by outsourcing essential functions in a network service will not avoid the license requirements.
53 53