Skip to Content
Last modified by chrisby on 2025/01/11 10:03
From version 2.99
edited by chrisby
on 2025/01/08 13:19
Change comment: There is no comment for this version
To version 2.118
edited by chrisby
on 2025/01/08 13:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -47,14 +47,11 @@
47 47  
48 48  **Copyleft Licenses**
49 49  
50 -To address the problems with proprietary software, the FSF primarily promotes copyleft licenses, which require that any derivative works of the software be licensed under the same terms as the original code. The term "derivative work" is legally somewhat vague, but here is a common understanding is, "If the AGPL is essential for the software to work, then the software is considered a derivative product". For example:
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 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.
51 51  
52 -* When a software needs AGPL source code directly in order to build it, that means using a AGPL licensed library or directly AGPL code into the project, its a derivate work.
53 -* Another case is usage network. For example, A vendor could come up with the idea to use AGPL code for his propieatary product, but out sources it into a s seaprate service assessible via network, so it does not use the source code. This way 
54 - * If the AGPL service is not essential and an optional addition to the software
55 - * if
52 +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, the software is usually not 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. Attempting to "work around" the AGPL by outsourcing essential functions in a network service will not avoid the license requirements.
56 56  
57 -This ensures that when contributions are made to a copyleft project, or when copyleft code is directly reused in another project, the resulting work must be released under the same copyleft license. This prevents vendors from incorporating copyleft code into proprietary products, and ensures that any derivative works remain open source. In addition, copyleft licenses require that the source code be made available to users so that they can modify, build, and control the software themselves.
54 +In summary, copyleft licenses like the AGPL ensure that whenever code is reused or contributions are made to existing copyleft code, the resulting work must remain open source. These licenses also require that the source code be made available upon request, so that users can modify, build, and control the software themselves if they wish.
58 58  
59 59  **License Preferences**
60 60