Reader 0.2 release repair and ready-backlog consolidation
维护者通常 1 天内回复
已经有一个关联 PR 被合并了。
- #276 来自 @andy-zen-dev —— 已合并
评估
调研方向
Start with the existing scrip-site-two-full-work-gallery branch at c411e29030e7e778f99cd9689441d348f75a7715, the Reader integration in #274, and site_renderer.py; inspect open PR #276 before touching the work. Verify the publisher crash recovery and concurrent publication regressions, then run full repository CI, an installed wheel smoke test, and a deterministic site rebuild on the successor's exact head. Done means the stated acceptance criteria pass together while preserving the branch histories and current master changes.
由索引模型根据 Issue 内容生成。
描述
Owner-requested delivery cleanup, 2026-10-18. #268 and #272 are now merged into master; #267/#271 closed. The remaining executable product issues are #269 and #273. #265 has separate missing administration/branch-deletion capabilities, not an analyzer blocker.
Delivery claim
Reuse the existing un-PR'd scrip-site-two-full-work-gallery branch at c411e29030e7e778f99cd9689441d348f75a7715 for one successor PR against current master. Preserve its three unique gallery files, adopt the existing Reader integration from #274 without reimplementation, fix the exact site_renderer.py syntax regression and verify the pending crash-safe publisher patch. Preserve the original histories and all current master changes. #270/#274 stay as provenance until the successor is accepted; do not start another competing integration.
Acceptance
- One runnable installable Reader with all existing 29 metrics, private bounded UTF-8 input, JSON/HTML/CSV and canonical five-route site.
- Full repository CI, clean installed-wheel smoke and deterministic site rebuild on the successor's exact head. Crash recovery/concurrent publication regressions; no weakened tests or publication allow-list.
- Reuse and verify the two-work source-free gallery; no new literary text or parity claim.
- Refresh the existing compact queue, reconcile delivery-oriented ownership into local instructions, and add the next key roadmap tasks with acceptance and scoped dependencies.
- No same-run merge of the repaired semantic change. No scheduler, access, visibility, administrative or external registry change.
M1-M5 completion remains unclaimed; M2 remains 0/5.
- 主要语言
- Python
- 星标
- 4
- 派生
- 0
- 平均合并
- 12 小时 50 分钟
- 30 天内合并 PR
- 86
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
drevendev/Scriptorium 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 25/100
drevendev/Scriptorium#285 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
drevendev/Scriptorium#284 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
drevendev/Scriptorium#283 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
drevendev/Scriptorium#282 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
drevendev/Scriptorium#281 ·
维护者通常 1 天内回复
查看 drevendev/Scriptorium 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
huggingface/smolagents#3106 ·
维护者通常 2 天内回复
-
area:scripts area:tests bug priority:later
难度 2/5 1-3 小时 新手友好度 72/100
Ikalus1988/MisakaNet#4358 ·
维护者通常 1 天内回复
-
Discovered ports from service discovery are never propagated to modules in Module.load()可能已有人在做 @vishalmore90 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
OWASP/Nettacker#1828 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
aws-samples/sample-per-model-bedrock#708 ·
维护者通常 1 天内回复
-
maintenance
难度 2/5 1-3 小时 新手友好度 62/100