[Phase 16] Write the Docker standard (prerequisite of S13)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker, docker-compose, markdown
- Domain
- documentation
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Python
- Stars
- 9
- Forks
- 1
- Avg merge
- 8h 10m
- Merged PRs (30d)
- 5
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from HodeTech/ForgeLM
-
area: dev-tooling bug severity: low source: roadmap wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
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)Possibly taken @vortsghost2025 claimed this today. Openarea: site bug good first issue severity: low source: review-2026-09 wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
documentation good first issue severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
documentation good first issue severity: low source: review-2026-09 wave: 4
Difficulty 1/5 1-3 hours Newbie friendliness 80/100
-
documentation severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in HodeTech/ForgeLM
Similar issues
-
vis.image() reports "Unsupported number of image channels: 224" for an HxWxC imagePossibly taken @piyush182004 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
fossasia/visdom#1997 · 3 comments ·
Maintainers usually reply within 6 days
-
Byse new domainOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Gujal00/ResolveURL#1525 ·
Maintainers usually reply within 1 day
-
Serialisation fails with pydantic 2.14: wrap serialisers pass SerializationInfo as index_keyPossibly taken @hugohills-regnosys claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
finos/rune-python-runtime#45 ·
-
[Bug]: LangGraph Store sync put bypasses namespace validationPossibly taken @ktz03 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
volcengine/OpenViking#6050 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hummingbot/condor#283 ·
Maintainers usually reply within 1 day