Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Phase 16] S13 — Packaging metadata, dependency single-source, container distribution

Open
  • Is something wrong?
#899 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, docker-compose, python
Domain
build-system, devops, documentation

Research direction

Blocked by #888, so start there; this step is reviewed against that standard. Begin with the roadmap plan at docs/roadmap/phase-16-trust-surface-hardening.md lines 682-721, then the cache mount in docker-compose.yaml (hf_cache at /root/.cache/huggingface versus USER forgelm). Done means the seven exit criteria pass, including the workflow_dispatch smoke job and twine check.

Written by the indexing model from the issue text.

Description

phase: 16 source: roadmap

Roadmap · Phase 16, step S13 · size L · 7 unit(s) · planned in docs/roadmap/phase-16-trust-surface-hardening.md:682-721

Summary

The distribution surface — what a user installs and what they run it in — with one root cause: hand-maintained duplicates of a single truth. docker-compose.yaml mounts hf_cache:/root/.cache/huggingface while the image drops to USER forgelm, so the cache never persists (an artifact defect, not only a documentation one). The manual advertises three image variants (latest, slim, airgap) that nothing builds, and every documented docker run … forgelm --config … resolves to forgelm forgelm … against the shipped ENTRYPOINT.

Units

Unit Tracked by (October 2026 review)
C31-DOCKER-RUNBOOK (= DOCS-05 + OPS-13) #157 · #159 · #201 · #210 · #217 · #218 · #298 · #409 · #422 · #451 · #602 · #615 · #619 · #638 · #643 · #702 · #789
F-W20260729-OPS-11, F-W20260729-OPS-12, F-W20260729-OPS-14, F-W20260729-OPS-17, F-W20260729-OPS-18 #114 · #465 · #523 · #558 · #566 · #607 · #668 · #686 · #702 · #776
C31-DEPENDENCY-SOURCE (= OPS-07 + OPS-08) #537 · #686 · #702

Blocked by

#888 — the standard this step is reviewed against; write it first.

Decisions this step executes

  • C-15 — container distribution: local docker build is the contract; a published image is tracked as a condition (deferred issue).
  • C-16 — fix the docker-compose.yaml cache path in the same change, with a ### Fixed entry naming the orphaned-volume effect.

Plan

  • Delete the three phantom variants and re-derive README and both manuals from the artifacts on disk.
  • Fix the compose cache path in the same change.

Exit criteria

  • README and both manuals describe exactly one distribution path.
  • A guard fails when a first-party registry reference has no backing publish workflow, when a compose file name in prose is absent from disk, or when a documented service name is absent from services:.
  • The documented first container command succeeds in a workflow_dispatch smoke job.
  • Two disposable docker compose run --rm invocations share one cached snapshot without root.
  • The documented wizard command leaves a validated YAML on the host after --rm that passes python3 -m forgelm --config <file> --dry-run.
  • A meta-test compares normalised direct dependencies between the nightly minimum-deps list and the package metadata.
  • A clean isolated build emits no packaging-metadata deprecation warning and twine check dist/* passes.

How to deliver

  • One root-cause family, committed on its own; then an Opus review round and a Sonnet review round, each with verified findings fixed and committed before the next step begins.
  • A reproducer that is red before the fix and green after; the full gauntlet from CLAUDE.md passes under ./.venv/bin/python.
  • Every English documentation edit ships with its Turkish mirror in the same commit; a new or renamed audit event gets its EN and TR catalog rows in the same PR.
  • A step that grows a deferred module carries its budget_history justification in the same diff; a widened guard rolls out non-strict first, then flips.
  • Commit bodies cite Absorbs F-W20260729-…; the CHANGELOG [Unreleased] section gets an entry only for a change a user or library consumer can observe (decision C-20).

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HodeTech/ForgeLM

All issues in HodeTech/ForgeLM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.