Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Retire the Amperstrand fork — OpenTollGate/tollgate-module-basic-go becomes the single source of truth (migration executed, plan inside)

Cerrado
  • ¿Algo no está bien?
#758 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Amperstrand ya está trabajando en esto.

Desde el 8/10/2026.

  • #759 de @Amperstrand — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github, go
Área
devops, release

Línea de trabajo

Start with the listed remaining phases and check the upstream README, CONTRIBUTING, release-process, and operator-guide for fork references. Then compare the named branches and upstream PRs, verify whether the gitleaks workflow runs on the ngit lane, and confirm the prerequisites are complete before archiving the fork read-only.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

important needs:human-review

Retire the Amperstrand fork — make OpenTollGate/tollgate-module-basic-go the single source of truth

The fork (Amperstrand/tollgate-module-basic-go) was the packaging/release staging area through the alpha cycle. That role is over: upstream now carries the packaging tree, the CI, the release process, and the review queue. This issue tracks the retirement so nothing is lost and no workflow keeps pointing at the fork.

Done (2026-10-07, this session)
Action Result
Issue tracker emptied — 11 live product issues migrated as #747–#757 (full bodies preserved, headers point at the fork originals for discussion history); 5 closed with dispositions (#102 superseded-by-upstream, #103 → #665, #106 umbrella dispositioned, #109 migrated via #715+PRTA#196, #110 → #715) fork open issues: 0
Open PR #110 (postinst) closed superseded by #715
Repo banner fork description now reads "SUPERSEDED — single source of truth: OpenTollGate/tollgate-module-basic-go. Do not open issues or PRs here"
min_steps rescue check fork #102's substance verified already-upstream (dual-key UnmarshalJSON + default-floored-to-1) — no rescue needed; remaining work is spec-side (OpenTollGate/tollgate#20)
The migration map (fork → upstream)

Fork #87→#747 (mint-health recovery budgets), #88→#748 (rate limit vs suites), #89→#749 (UDP DNS), #90→#750 (TIP vectors Go leg), #92→#751 (GPL license text decision), #95→#752 (fee-less 1-sat swap rejection), #96→#753 (release-asset sha256s — pairs with the publish gate), #97→#754, #99→#755, #100→#756, #101→#757 (the firewall/nftables class).

Remaining phases
  1. Branch triage (bulk, low-risk). The fork carries 67 branches on a diverged main (patch-id comparison to upstream is meaningless — the histories rewrote). Named cross-check shows the short fix/* branches are relay twins of already-open upstream PRs (#504→#742, #520→#740, #722→#739, dockerfile-hoist→#728, dev-env→#736, first-purchase→#737) — they die when those merge. The long-lived feat/*/chore/* branches (identity-v2, vendor-ie-v2, wallet-port, nut-spec-quotes, publish-verification, …) need ONE pass: name ↔ upstream-tracker cross-check, rescue anything with a live idea and no upstream home, delete the rest. Nothing is lost by deletion-at-archive anyway — archived repos keep refs readable.
  2. Docs repoint. Grep upstream docs (README, CONTRIBUTING, release-process, operator-guide) for Amperstrand-fork references and repoint to upstream paths; release-process.md's "never the fork, never a reused name" rule gets a closing note that the fork is archived read-only.
  3. CI/workflow parity check. The gitleaks local backstop (fork #108 lineage) is upstream (.github/workflows/gitleaks.yml); confirm it actually runs on the ngit lane too (the #520/#740 class), not just GitHub.
  4. Freeze → archive. Once (1)–(3) are green and no open fork items exist (already true), archive the fork read-only. The banner + empty tracker make this safe at any point after branch triage.
Non-goals / notes
  • The gonuts-tollgate fork is a different fork and stays (it is the maintained wallet library, per AGENTS.md).
  • ai-legion working copies of fork checkouts should be re-pointed at upstream remotes (same class as the PRTA stale-copy finding).
  • Archiving keeps all history readable; deletion is NOT proposed.
Lenguaje dominante
Go
Estrellas
12
Forks
14
Merge medio
1 d 8 h
PR fusionados (30 d)
201

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenTollGate/tollgate-module-basic-go

Todos los issues de OpenTollGate/tollgate-module-basic-go

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.