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.120
edited by chrisby
on 2025/01/08 13:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -51,7 +51,7 @@
51 51  
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 -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, 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. Th 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 55  
56 56  **License Preferences**
57 57