Description
The analyzed checkout uses kkowalski-reef/b2-sdk-sep2026 as its Git remote while retaining hard-coded references to Backblaze/b2-sdk-python. These occur in README badges, pyproject.toml project metadata and Towncrier URLs, noxfile.py release instructions, and doc/source/conf.py "Edit on GitHub" settings. Some links may intentionally point upstream, but the fork's purpose, contribution target, and release authority are not documented.
Steps to reproduce
1. Run `git remote -v` in the analyzed checkout.
2. Search README.md, pyproject.toml, noxfile.py, and doc/source/conf.py for `Backblaze/b2-sdk-python`.
3. Follow the issue, release, badge, and "Edit on GitHub" destinations and compare them with the intended maintenance workflow.
Expected behavior
Document whether the fork is a temporary review artifact, a downstream distribution, or an independently released project. Build a small link-ownership table, then make each issue, release, badge, source-edit, and package-homepage link intentionally target upstream or the fork. Avoid changing release destinations until ownership is confirmed.
Actual behavior
The fork identity is ambiguous. A contributor may open an issue or documentation edit upstream while working in the fork, and a maintainer could misunderstand which repository, tag, or release page is authoritative. Blindly replacing every URL would also be risky because some upstream references may be correct.
Environment
- Python version: Not applicable
- b2sdk version: fork
master at f3ab7b71
- OS: Not applicable
Description
The analyzed checkout uses
kkowalski-reef/b2-sdk-sep2026as its Git remote while retaining hard-coded references toBackblaze/b2-sdk-python. These occur in README badges,pyproject.tomlproject metadata and Towncrier URLs,noxfile.pyrelease instructions, anddoc/source/conf.py"Edit on GitHub" settings. Some links may intentionally point upstream, but the fork's purpose, contribution target, and release authority are not documented.Steps to reproduce
Expected behavior
Document whether the fork is a temporary review artifact, a downstream distribution, or an independently released project. Build a small link-ownership table, then make each issue, release, badge, source-edit, and package-homepage link intentionally target upstream or the fork. Avoid changing release destinations until ownership is confirmed.
Actual behavior
The fork identity is ambiguous. A contributor may open an issue or documentation edit upstream while working in the fork, and a maintainer could misunderstand which repository, tag, or release page is authoritative. Blindly replacing every URL would also be risky because some upstream references may be correct.
Environment
masteratf3ab7b71