LICENSE: Apache-2.0 §8 is non-canonical — restore verbatim

[dimitri-yatsenko]

The LICENSE file has a non-canonical Apache-2.0 §8 (Limitation of Liability). Line 153 reads:

8. Limitation of Liability. In no event and under no theory of liability, whether in contract, strict liability, or tort …

The canonical Apache-2.0 text (as in datajoint/datajoint-python/LICENSE) is:

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law …

Altering the body of the Apache-2.0 license means the file is no longer the Apache-2.0 license as published. This appears to have propagated by copy into a new sibling (dj-canvasxpress-codecs), where it was flagged in review.

Fix: restore §8 verbatim from the canonical Apache-2.0 text. Keeping the instructional APPENDIX removed and the Copyright … DataJoint Inc. line is fine — only the license body must be verbatim.

Surfaced during review of datajoint-company/dj-canvasxpress-codecs#1.

[MilagrosMarin]

Fixed by a1e0f90 (2026-07-22), the day after this was filed — the issue just stayed open.

Verified against the canonical text at https://www.apache.org/licenses/LICENSE-2.0.txt: the license body is verbatim, all 149 non-blank lines identical through END OF TERMS AND CONDITIONS. Only the Copyright 2026 DataJoint Inc. line and the standard boilerplate notice follow it, which this issue explicitly allows.

That commit restored two deviations rather than the one reported here. §8 as described, and also in §1: submitted to the Licensor → submitted to Licensor.

The propagation to dj-canvasxpress-codecs noted above is also resolved — its body is verbatim too.

One thing worth pulling out of this, in the other direction: datajoint/datajoint-python's own LICENSE has that same §1 deviation, submitted to the Licensor. This issue cited that file as the canonical reference, and on that one clause it isn't. Worth its own issue there.