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

Publish an official ForgeLM container image — deferred until a weight-redistribution position and the Docker standard exist

Open
#916 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
8/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker
Domain
devops

Research direction

Start in docs/roadmap/risks-and-decisions.md at the deferral row near line 260, and read release.md for the current release contract. The work is blocked on a weight-redistribution decision and on the Docker standard in #888, so there is no code to change yet. Done means a release-time workflow pushes digest-pinned images with provenance and an SBOM, the manuals name the variants it builds, and the row is removed with its ID in the CHANGELOG.

Written by the indexing model from the issue text.

Description

area: packaging-ci deferred severity: medium source: roadmap wave: 3

Deferred work · F-W20260729-DOCS-05-image · severity Medium · cost ~1 week · recorded in docs/roadmap/risks-and-decisions.md:260

Summary

Decision C-15 made local docker build the distribution contract; publishing an image was deferred, not rejected. A publish pipeline is new release surface — registry auth, packages: write, an immutable tag/digest policy, provenance and SBOM coverage that release.md does not define — and the advertised airgap variant (with pre-cached weights) raises a model-weight redistribution question that is not an engineering decision.

Condition or budget

A decided position on redistributing pre-cached weights, plus the Docker standard (#888) that Phase 16 S13 relies on.

State today (re-checked 2026-10-09)

No workflow builds or pushes an image; no Docker standard exists; no redistribution decision is recorded.

Related

#451 corrects the manuals to the local-build contract (part of Phase 16 S13, #899).

Acceptance criteria

  • A release-time publish workflow pushes digest-pinned images with provenance and an SBOM, as the Docker standard requires, and the manuals name exactly the variants it builds.
  • The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).

Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.

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.