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
@@ -7,7 +7,7 @@ Its problems are modeled on the failures that the specification's rules address.
|
||||
Three readers can use the guide, and each gets something different.
|
||||
A newcomer knows what a paper and a citation are, not hashes or JSON, so every term is defined where it first appears.
|
||||
An implementer who will write a reader, writer, converter or checker gets the chapter and test vector for each step.
|
||||
An expert gets the status: [paperspec](https://git.scient.ing/infra/paperspec) is at version 0.1.0, and each format is `candidate` or `provisional` in [`registry/formats.json`](../registry/formats.json) (19 candidate, 13 provisional).
|
||||
An expert gets the status: [paperspec](https://git.scient.ing/papers/paperspec) is at version 0.1.0, and each format is `candidate` or `provisional` in [`registry/formats.json`](../registry/formats.json) (19 candidate, 13 provisional).
|
||||
The `scienting-` prefix on format names, as in `scienting-doc/1`, is the formats' namespace.
|
||||
It has nothing to do with the repository's name.
|
||||
|
||||
|
||||
Reference in new issue
Block a user