Publish the package and its documentation, and move to the papers organization
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
This commit is contained in:
37 files changed
+1005
-83
No files matched your search
+1
-1
@@ -2,7 +2,7 @@
|
||||
|
||||
This specification states exactly what each paperspec file holds and how every value in it is computed.
|
||||
The schemas, SQL, JSON-LD context, registries, vectors and fixtures are normative too, and each chapter says which of them it relies on.
|
||||
A chapter and a vector that disagree signal a bug, so please report it in the repository, <https://git.scient.ing/infra/paperspec>.
|
||||
A chapter and a vector that disagree signal a bug, so please report it in the repository, <https://git.scient.ing/papers/paperspec>.
|
||||
|
||||
Two readers will get the most from it: implementers who build a reader, writer, converter or checker, and experts who want the precise rules.
|
||||
Newcomers should start with the [guides](../docs/README.md), which explain what the formats are for.
|
||||
|
||||
Reference in new issue
Block a user