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

Ouverte
  • Quelque chose ne va pas ?
#600 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
45/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
Calme
Stack technique
github, python
Domaine
documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
Python
Étoiles
214
Forks
68
Merge moyen
51 min
PR mergées (30 j)
6

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Backblaze/b2-sdk-python

Toutes les issues de Backblaze/b2-sdk-python

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.