Skip to content

fix: redact operator name from CITATION.cff; add .zenodo.json#1

Open
Zer0pa-Architect-Prime wants to merge 2 commits intomainfrom
zenodo-metadata-redaction-2026-05-03
Open

fix: redact operator name from CITATION.cff; add .zenodo.json#1
Zer0pa-Architect-Prime wants to merge 2 commits intomainfrom
zenodo-metadata-redaction-2026-05-03

Conversation

@Zer0pa-Architect-Prime
Copy link
Copy Markdown
Contributor

Summary

  • CITATION.cff: Removes given-names: Priniven (private operator name) from public author field. Replaces individual attribution with org-level name: "Zer0pa".
  • .zenodo.json: Adds Zenodo release metadata file. Uses org attribution, no operator name exposure, custom license noted in notes field (LicenseRef-Zer0pa-SAL-6.2 is not a Zenodo-recognised SPDX ID — noted explicitly).

Why

The brief PYPI_ZENODO_PARALLEL_LANE_BRIEF_2026-05-03 requires:

  • No exposure of operator private names in public package or release surfaces.
  • Zenodo metadata hygiene before any GitHub Release is tagged.

ZeroShip is not PyPI-shaped. No pyproject.toml, no publish workflow needed. This PR covers the Zenodo-only path.

Not included

  • No GitHub Release tag (no Zenodo-triggering release until operator confirms readiness).
  • No changes to license type (remains LicenseRef-Zer0pa-SAL-6.2; custom SPDX noted in .zenodo.json notes field).
  • No changes to README or proof anchors.

Checkers

  • Operator reviews CITATION.cff org attribution is acceptable
  • Operator confirms .zenodo.json notes wording for custom license is correct
  • Merge when confirmed; tag a GitHub Release when Zenodo integration is ready to trigger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant