AOCL > Commit [4812118]

Christian Lee Seibold

Sun March 2, 2025 6:19 PM -0600

Update


 aocl.txt | 14 ++++++--------

Commit Hash: 48121186084695b755156ca8629df98676096377

Tree Hash: 188167e1d777a0f18b6d9341826b3568bacf56eb

Date: 2025-03-02T18:19:05-06:00

Browse Tree
Parent 609b697
Commits
Repo Home

Changes

aocl.txt

   ... | ...
    33 | 
    34 | 1.4 **"Derivative Work"** refers to any work that contains or is derived from any part of the Software's Source Code.
    35 |    a) What ARE Derivative Works:
    36 |       - Modifications or alterations to the Software's Source Code, such as bug fixes, feature enhancements, or performance improvements.
    37 |       - Ports or translations of the Software into other programming languages or formats.
-   38 |       - Software that incorporates, copies, or adapts the Software's Source Code into its own source files.
-   39 |       - Software that directly imports or includes the Software's Source Code (rather than linking to binary forms)
-   40 |       - Works that combine the Software's Source Code with other code at the source code level.
+   38 |       - Works that modify and incorporate, copy, or adapt the Software's Source Code so that it is dependent on other code at the source code level.
    41 | 
    42 |    b) What are NOT Derivative Works:
    43 |       - User interfaces that display output from or provide input to the Software without reproducing the Software's Source Code.
   ... | ...
    39 | 
    40 |    b) What are NOT Derivative Works:
    41 |       - User interfaces that display output from or provide input to the Software without reproducing the Software's Source Code.
-   44 |       - Software that links to the Software in binary form, either statically, dynamically, or through Foreign Function Interfaces (FFI).
+   42 |       - Works that link to the Software in unmodified source or binary form, either statically, dynamically, through Foreign Function Interfaces (FFI), or through the Software's APIs given the Work is dependent on the Software, but the Software is not dependent on the Work.
    45 |       - Programs that launch, invoke, or execute the Software as a separate process through operating system mechanisms.
    46 |       - Independent programs that exchange data or communicate with the Software through interfaces, protocols, or other interoperability mechanisms.
    47 |       - Works that use the Software as a tool without incorporating its Source Code.
    48 | 
    49 | 1.5 **"Prominent Notice"** refers to a notification that would be discoverable by an ordinary user during normal use of the software, including but not limited to placement in:
   ... | ...
    75 |       - A copy of Sections 4, 5, 7.1, and 7.2 of this license, or a reference to this license in full, must be included.
    76 |       - A prominent notice stating that the software incorporates elements covered by the AuraGem Opensource Copyleft License must be included.
    77 |       - A reference to where the Software's Source Code can be obtained must be included.
    78 |       - Any use of Trademarks must comply with Section 5 of this license.
    79 | 
-   80 |    c) Any distribution you make must be made directly under the terms of this license without sublicensing. Each recipient receives their rights directly from the original authors or copyright holders, not from you as an intermediary.
+   78 |    c) Any distribution you make must be made directly under the terms of this license without sublicensing. Each recipient receives their rights directly from the Original Authors or Copyright Holders, not from you as an intermediary.
    81 | 
    82 | ### 3. Copyleft
    83 | 
    84 | 3.1 Any Derivative Works of the Software must be licensed under the same terms as this license. You may not impose any additional restrictions on the rights granted by this license, nor may you sublicense the Software or any Derivative Works. Incorporating or embedding the Software's Source Code directly into another codebase creates a Derivative Work subject to this provision.
    85 | 
   ... | ...
    98 | 4.3 Attribution Display Requirements:
    99 |    a) For graphical user interfaces: If the Software displays attribution notices in a graphical user interface, software that also includes a graphical user interface must display equivalent attribution notices in a reasonably similar location and manner.
   100 |    b) For command-line interfaces: If the Software displays attribution notices in command-line output, software that also includes a command-line interface must display equivalent attribution notices in a reasonably similar manner.
   101 |    c) For documentation: Attribution notices must be preserved in all documentation related to the Software or Derivative Works.
   102 | 
-  103 | 4.4 Use of names, trademarks, service marks, or product names of the original authors or contributors is governed by Section 5 (Trademark Usage), with limited permissions for attribution purposes as specified in Section 5.2.
+  101 | 4.4 Use of names, trademarks, service marks, or product names of the Original Authors or Copyright Holders is governed by Section 5 (Trademark Usage), with limited permissions for attribution purposes as specified in Section 5.2.
   104 | 
   105 | 4.5 Scope of Attribution Requirements:
   106 |    a) The attribution requirements in this section (Section 4) apply to all software that uses the Software or its Source Code in any way, even if that software is not considered a Derivative Work under Section 1.4.
   107 |    b) This means that even software that merely links to the Software, provides a user interface for the Software, or communicates with the Software through APIs must comply with all attribution requirements in Section 4.
   108 |    c) These attribution requirements are independent of the obligation to share source code, which applies only to Derivative Works as defined in Section 1.4.
   ... | ...
   202 |    b) For violations involving non-Derivative Works:
   203 |       - Ceasing all interactions with the Software until the violation is corrected.
   204 | 
   205 |    c) In all cases:
   206 |       - Correcting the non-compliance within 30 days of becoming aware of it.
-  207 |       - Notifying the original authors or copyright holders of your corrective actions.
+  205 |       - Notifying the Original Authors or Copyright Holders of your corrective actions.
   208 | 
   209 | 9.3 If and only if you fully remedy the non-compliance within the specified period, your rights under this license may be reinstated. If you do not remedy the non-compliance within the specified period, you may not resume use of the Software in any way without obtaining a new license from the copyright holders.
   210 | 
   ... | ...
   206 | 
   207 | 9.3 If and only if you fully remedy the non-compliance within the specified period, your rights under this license may be reinstated. If you do not remedy the non-compliance within the specified period, you may not resume use of the Software in any way without obtaining a new license from the copyright holders.
   208 | 
-  211 | 9.4 The original authors or copyright holders may enforce this license through legal action. In the event of a breach of this license, they may seek:
+  209 | 9.4 The Original Authors or Copyright Holders may enforce this license through legal action. In the event of a breach of this license, they may seek:
   212 |    a) Injunctive relief to prevent further violations.
   213 |    b) Monetary damages for any losses incurred due to the violation.
   214 |    c) Recovery of attorney's fees and costs associated with enforcing this license.
   215 | 
   216 | ### 10. Disclaimer of Warranty