B2 SDK docs: review upstream and fork URLs across badges, releases, and Edit on GitHub links
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- github, python
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
masteratf3ab7b71 - OS: Not applicable
- 主要语言
- Python
- 星标
- 214
- 派生
- 68
- 平均合并
- 51 分钟
- 30 天内合并 PR
- 6
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Backblaze/b2-sdk-python 的其他 Issue
-
Download and copy sync actions print remote file names without escape_control_chars可能已有人在做 @dreyfus92 于 15 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
Backblaze/b2-sdk-python#631 ·
维护者通常 1 天内回复
-
SqliteAccountInfo profile name validation uses "re.match", so only the first character is checked可能已有人在做 @nazarli-shabnam 于 9 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
Backblaze/b2-sdk-python#629 ·
维护者通常 1 天内回复
-
Adopt the AI-native SDLC and repository policies可能已有人在做 @goanpeca 于 18 天前认领。 未关闭enhancement
难度 5/5 一周以上 新手友好度 20/100
Backblaze/b2-sdk-python#634 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 50/100
Backblaze/b2-sdk-python#630 ·
维护者通常 1 天内回复
-
ci: cli-compat fails — 4 sse/sync integration tests broken in B2_Command_Line_Tool (all environments)可能重新可做 @ffumero2003 于 37 天前认领，目前没有进行中的 PR。 未关闭bug testing
Backblaze/b2-sdk-python#627 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 Backblaze/b2-sdk-python 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 72/100
btclib-org/btclib-node#2505 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
open-webui/open-webui#34462 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
gorakhargosh/watchdog#1462 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
openwisp/openwisp-monitoring#889 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
IETF-Hackathon/pqc-certificates#351 ·
维护者通常 2 天内回复