Skip to Content
Last modified by chrisby on 2025/01/11 10:03
From version 2.122
edited by chrisby
on 2025/01/11 09:53
Change comment: There is no comment for this version
To version 2.115
edited by chrisby
on 2025/01/08 13:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -47,11 +47,11 @@
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. 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.
50 +To address problems with proprietary software, the FSF promotes copyleft licenses, like the AGPL license, which require that any derivative works remain under the same license. The notion of “derivative work” is somewhat vague in legal terms, but a common interpretation is that software depending on AGPL code to function is a derivative work.
51 51  
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 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.
52 +For instance, if a project directly incorporates AGPL source code or relies on an AGPL library, it must adopt the AGPL license for its entire codebase. Similarly, when software calls an external AGPL service over a network, the software is typically not a derivative work if that service is purely optional. However, if the service is essential and the software won’t function without it, even if the AGPL code is hosted externally, the software is still considered a derivative work. Attempting to “bypass” the AGPL by outsourcing essential functions in a network service will not avoid the license requirements.
53 53  
54 -In summary, copyleft licenses like the AGPL ensure that whenever code is reused or contributions are made to existing 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.
54 +In summary, this copyleft license ensures that whenever AGPL code is reused, or when contributions are made to existing copyleft code, the resulting work must remain open source. Athe  also guarantees that the source code is available so users can modify, build, and control the software themselves.
55 55  
56 56  **License Preferences**
57 57  
... ... @@ -69,7 +69,7 @@
69 69  
70 70  **Does a permissive or copyleft project lead to more contributions?**
71 71  
72 -* Permissive licenses might attract more users, especially vendors, and lead to more voluntary contributions. Copyleft licenses, on the other hand, might repel some contributors, but force improvements to be open-sourced and shared with the community. Which effect is greater depends on the situation.
72 +* Permissive licenses might attract more users, especially vendors, and lead to more voluntary contributions. Copyleft licenses, on the other hand, might repel some of them, but force improvements to be open-sourced and shared with the community. Which effect is greater depends on the situation.
73 73  
74 74  **Why should people with no technical expertise care about open source?**
75 75