Evaluate detaching repository from abandoned upstream fork

[cbusillo]

Context

cbusillo/printnode_community is currently still marked as a fork of PrintNode/PrintNode-Python, but upstream appears abandoned and this repo is now maintained as our community/stewardship home for the package.

GitHub supports detaching eligible forks from their fork network through repository Settings. This should be handled deliberately because the operation is permanent and can affect repository metadata even though git history is preserved.

Finish Line

Decide whether to detach this repository from the upstream fork network, and if yes, perform the detachment after capturing enough repository state to recover from any metadata surprises.

Checklist

• Confirm upstream is still abandoned and no longer an appropriate parent.
• Snapshot branches, tags, releases, open issues, open PRs, branch protections, Actions settings, secrets/deploy keys inventory names, and repo topics/description.
• Confirm this repo has no child forks and still meets GitHub detachment eligibility requirements.
• Decide whether to preserve any visible attribution to the original upstream in README/project docs.
• Detach the fork through GitHub repository Settings if still desired.
• Verify repository URL, clone behavior, branch protections, Actions, issues, releases, and package/release workflows afterward.

References

• GitHub Docs: Detaching a fork - https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork

[shiny-code-app]

Direction reconciliation, 2026-09-26 (against the owner's overall DIRECTION.md)

Disposition: parked.

Own-project housekeeping; the detach itself is permanent and the owner's call when it is picked up.

Parked until printnode_community is picked from the own-projects share.