B2 SDK docs: review upstream and fork URLs across badges, releases, and Edit on GitHub links

Offen
  • Stimmt etwas nicht?
#600 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
github, python
Bereich
documentation

Rechercherichtung

Start with git remote -v in the checkout, then search README.md, pyproject.toml, noxfile.py, and doc/source/conf.py for Backblaze/b2-sdk-python. Build a link-ownership table that records each badge, issue/release URL, Towncrier reference, source-edit link, and package homepage, marking upstream or fork intent. Done means the fork's purpose and release authority are documented and every link is intentionally assigned; do not change release destinations until that ownership is confirmed.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
Python
Sterne
214
Forks
68
Ø Merge
51 Min.
Gemergte PRs (30 T.)
6

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus Backblaze/b2-sdk-python

Alle Issues in Backblaze/b2-sdk-python

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.