Add the Zensical documentation of the Python package (docs/package, built by the docs workflow), merge the standard publish workflow with the setuptools-scm tag check, add the SPDX header rule to ruff, restructure the README, and point every repository and registry address at the Gitea organization papers. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B8cL4zN4XpaQF5cBtASzfq
1022 B
1022 B
License
paperspec is not under the studio's usual license.
Because the formats are meant to be implemented by anyone, in any product, without asking, each path of the repository keeps the license that LICENSE.md gives it.
| Paths | License | SPDX |
|---|---|---|
spec/, docs/, README.md, CONTRIBUTING.md, CHANGELOG.md and the other prose |
Creative Commons Attribution 4.0 International | CC-BY-4.0 |
schemas/, sql/, context/, registry/, vectors/, fixtures/ |
Creative Commons Zero 1.0 Universal | CC0-1.0 |
src/ (the paperspec package and its commands), tests/, tools/ |
Apache License 2.0 | Apache-2.0 |
Python source files open with an SPDX-License-Identifier: Apache-2.0 header, which ruff checks.
All text in the fixtures is synthetic, and the keys in fixtures/keys/ are public test keys that must never sign anything else.
The full text is in LICENSE.md at the root of the repository, https://git.scient.ing/papers/paperspec/src/branch/main/LICENSE.md.