Skip to Content
Last modified by chrisby on 2025/01/11 10:03
From version 2.121
edited by chrisby
on 2025/01/08 13:47
Change comment: There is no comment for this version
To version 2.123
edited by chrisby
on 2025/01/11 09:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -47,8 +47,10 @@
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, such as the AGPL, which require that any derivative works remain under the same license.
51 51  
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.
53 +
52 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.
53 53  
54 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.
... ... @@ -55,7 +55,7 @@
55 55  
56 56  **License Preferences**
57 57  
58 -The OSI aims to maximize the contributions and impact of open source by being open to all open source licenses. Permissive licenses have become very popular in recent years, especially in commercial contexts, but the OSI is open to choosing copyleft licenses if developers want to ensure that derivative works remain open and free. The FSF, on the other hand, tolerates all open source licenses, but has a strong preference for copyleft licenses, believing that all software should be protected in this way.
60 +The OSI aims to maximize the contributions and impact of open source by being neutral and open to all licenses that meet the open source definition, whether permissive or copyleft. The FSF accepts all open source licenses, but has a strong preference for copyleft licenses.
59 59  
60 60  **User Behavior**
61 61  
... ... @@ -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 of them, but force improvements to be open-sourced and shared with the community. Which effect is greater depends on the situation.
74 +* 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.
73 73  
74 74  **Why should people with no technical expertise care about open source?**
75 75