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

Aberta
  • Algo errado?
#600 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
45/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
github, python
Domínio
documentation

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
Python
Estrelas
214
Forks
68
Merge médio
51min
PRs com merge (30d)
6

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Backblaze/b2-sdk-python

Todas as issues de Backblaze/b2-sdk-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.