[Phase 16] Write the Docker standard (prerequisite of S13)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 半天
- 新手友好度
- 42/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- docker, docker-compose, markdown
调研方向
Start with docs/standards/README.md and the layout that documentation.md prescribes, then read Dockerfile, docker-compose.yaml and .dockerignore to see what the rules must cover. The standard must settle digest pinning, runtime versus devel stages, a non-root user with an owned cache path, service naming and a CI smoke obligation, and each rule must be checkable by a reviewer. Done means the new file sits under docs/standards/, is listed in the README, and Phase 16 step S13 can be reviewed against it.
由索引模型根据 Issue 内容生成。
描述
Roadmap · Phase 16 · prerequisite of step S13 · size M · planned in
docs/roadmap/phase-16-trust-surface-hardening.md:898-903
Summary
Dockerfile, docker-compose.yaml, .dockerignore and the EN/TR operations manual all ship, but no standard governs them: the only rule anywhere is a post-release checkbox in release.md, and no workflow under .github/workflows/ builds or smoke-tests the image. Phase 16 S13 has nothing to be reviewed against until this exists.
What the standard must settle
- A base-image digest-pinning policy.
- A runtime-versus-devel stage rule.
- A non-root user with an owned cache path.
- Service naming.
- A CI smoke obligation.
Acceptance criteria
- The standard lives under
docs/standards/in the layoutdocumentation.mdprescribes and is listed indocs/standards/README.md. - It answers every point above with a rule a reviewer can check, not a description.
- Phase 16 step S13 can be reviewed against it.
Planned in docs/roadmap/phase-16-trust-surface-hardening.md (read at f94595f). Unit IDs (F-W20260729-…) come from the 2026-07-29/30 full-project review; the issue numbers next to them are the October 2026 review's records of the same defects.
- 主要语言
- Python
- 星标
- 9
- 派生
- 1
- 平均合并
- 11 小时 8 分钟
- 30 天内合并 PR
- 10
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
HodeTech/ForgeLM 的其他 Issue
-
area: dev-tooling bug severity: low source: roadmap wave: 4
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
Site: the theme-locked --code-comment grey (#6a6f80) on the dark code surface is 3.8:1, below WCAG AA, in both themes (F-W1-SITE-06)可能已有人在做 @vortsghost2025 于 2 天前认领。 未关闭area: site bug good first issue severity: low source: review-2026-09 wave: 4
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
Choosing-a-trainer table documents KTO rows as {prompt, response, label}, but the KTO loader requires a completion column (F-W1-DOCS-TRAIN-02)可能已有人在做 @vortsghost2025 于 1 天前认领。 未关闭documentation good first issue severity: medium source: review-2026-09 wave: 3
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
documentation good first issue severity: low source: review-2026-09 wave: 4
难度 1/5 1-3 小时 新手友好度 80/100
维护者通常 1 天内回复
-
documentation severity: medium source: review-2026-09 wave: 3
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
huggingface/sentence-transformers#4186 ·
维护者通常 5 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 92/100
QuantEcon/QuantEcon.py#988 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
fabriziosalmi/certmate#1247 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
documentation good first issue
难度 2/5 半天 新手友好度 72/100
sujithputta02/Esapay#13 ·