Skip to Content
Last modified by chrisby on 2025/01/11 10:03
From version 2.88
edited by chrisby
on 2025/01/08 11:22
Change comment: There is no comment for this version
To version 2.94
edited by chrisby
on 2025/01/08 13:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -47,11 +47,18 @@
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 a common understanding is that it means a new work based on the original copyleft code that incorporates it at the source level. 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.
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 exa
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, then the whole project must be AGPL licensed as well.
53 +* another is when a software uses an external AGPL service via network. Here are two cases:
54 + * If the AGPL service is not essential and an optional addition to the software
55 + * if
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.
58 +
52 52  **License Preferences**
53 53  
54 -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.
61 +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.
55 55  
56 56  **User Behavior**
57 57