Should udos keep publishing to PyPI while it is an empty placeholder?

[thorwhalen]

Context

udos was created in 2022 as a placeholder for an open standard for dataset
search, acquisition, reusable preparation and sharing (see README). Four years
on, the package still contains exactly one module holding a module docstring and
nothing else, and there is one PyPI release, 0.0.2.

The packaging/CI modernization PR brings the repo onto pyproject.toml +
the wads uv-CI stub and turns CI green, but it cannot answer a question only the
maintainer can:

Question

Should udos keep publishing to PyPI while it has no content?

[tool.wads.ci.publish].enabled is true (the ecosystem default), so every merge
to the default branch bumps the version and pushes a new release. For a package
with no code, each merge spends a release number on an empty artifact.

Three reasonable answers:

1. Keep publishing. Harmless; it keeps the name reserved on PyPI and keeps the
   repo on exactly the same rails as every other package in the ecosystem. Nothing
   to do.
2. Pause publishing until there is content. Set
   [tool.wads.ci.publish].enabled = false in pyproject.toml. Validation still
   runs on every push; publishing is simply skipped (a commit containing the
   configured publish marker can still force one). Flip it back when the package
   grows an API.
3. Retire the repo. If the standard is being pursued elsewhere, archive this
   repo and leave 0.0.2 as the final release.

Related

The modernization PR also notes two GitHub repo settings that the repo audit
flags and that cannot be delivered through a PR:

gh repo edit i2mint/udos --homepage "https://i2mint.github.io/udos/" \
  --add-topic dataset --add-topic data --add-topic standard \
  --add-topic search --add-topic acquisition --add-topic sharing