Skip to Content
Last modified by chrisby on 2025/01/11 10:03
From version 2.116
edited by chrisby
on 2025/01/08 13:41
Change comment: There is no comment for this version
To version 2.117
edited by chrisby
on 2025/01/08 13:42
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, the software is usually not a derivative work if the service is purely optional. 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.
53 53  
54 -In summary, this copyleft license ensures that whenever AGPL code is reused, or contributions are made to existing copyleft code, the resulting work must remain open source. The AGPL license also guarantees that the source code must be made available if a user requests it, so that users 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.
55 55  
56 56  **License Preferences**
57 57