Publish an official ForgeLM container image — deferred until a weight-redistribution position and the Docker standard exist
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- docker
- Área
- devops
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Deferred work ·
F-W20260729-DOCS-05-image· severity Medium · cost ~1 week · recorded indocs/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.
- Lenguaje dominante
- Python
- Estrellas
- 9
- Forks
- 1
- Merge medio
- 7 h 42 min
- PR fusionados (30 d)
- 4
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de HodeTech/ForgeLM
-
area: dev-tooling bug severity: low source: roadmap wave: 4
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
area: site bug good first issue severity: low source: review-2026-09 wave: 4
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
-
documentation good first issue severity: medium source: review-2026-09 wave: 3
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
documentation good first issue severity: low source: review-2026-09 wave: 4
Dificultad 1/5 1-3 horas Aptitud para principiantes 80/100
-
documentation severity: medium source: review-2026-09 wave: 3
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Todos los issues de HodeTech/ForgeLM
Issues similares
-
Consolidate the now-identical CLI-native and composed tasks_packages guards (#5945 follow-up)Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
spec-kitty/spec-kitty#6112 ·
Los mantenedores suelen responder en 1 día
-
[Bug]: OpenRouter streaming chunks report the requested router name instead of the model OpenRouter servedPosiblemente ocupada @Mrun25 la tomó hoy. Abiertobug llm translation
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
BerriAI/litellm#46095 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
uberdeveloper/fastbt#29 ·
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
andrew-blake/melcloudhome#368 ·
Los mantenedores suelen responder en 1 día
-
lane:discover
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
SPARDiffData/differential-data-collection#33 ·
Los mantenedores suelen responder en 1 día