Files

T

Thore CimbalandClaude Opus 5 a1def8666e feat(issues): adopt the component trackers — one backlog, one numbering (ADR-0019)

ADR-0012 made docs/issues/ canonical for the management scope only and left
gitops, ThreadNet-Web and threadnet-call on GitLab "until the component adopts".
That split produced exactly what it invited: two numbering worlds where
management#20 and gitops#20 are different issues, drift nobody had to answer for
(gitops#61 carried no milestone since 2026-08-11), and component backlogs that
host sessions without lab access cannot read at all.

The 46 open component issues are now files 0056-0101. The file id is the
group-wide identifier; provenance lives in the frontmatter (new field `projekt`
plus gitlab_iid) and in the filename, so "gitops#61" still finds 0091. Bodies are
copied verbatim; comments and history stay on GitLab, as with the 2026-08-11
management import.

Both scripts learned the second dimension: spiegel_issues.py routes each file to
its origin project, reopens issues that are open in the repo but closed on the
board, and writes the new iid back after creating one; gruppenpruefung.py checks
drift across all four trackers instead of management alone. What the mirror
cannot decide stays a finding, not a silent state.

Two things needed a hand, both recorded in the files: gitops#61 had no milestone
(M1 - it is a live account-takeover path) and carried two area labels where the
schema holds one. The Gitea migration footers in the imported bodies point at
decommissioned trackers; their links are removed, the provenance sentence stays.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-18 12:00:00 +00:00

1.9 KiB

Raw Blame History

type, id, status, created, milestone, priority, wartegrund, projekt, gitlab_iid, related

type

status

created

milestone

priority

wartegrund

projekt

gitlab_iid

issue

0096

waiting

2026-07-31

medium

Gesamtklammer — appId-Wechsel (neues Profilverzeichnis) muss bewusst entschieden werden

threadnet-web

Rebranding: Element → aXion1337 (Web + Desktop, Gesamtklammer)

Adoptiert aus threadnet-web#7 (2026-08-18, ADR-0019). Kommentare und Verlauf bleiben dort; kanonisch ist ab jetzt diese Datei.

Sammel-TODO (gewünscht von sorb, 2026-07-31): die Client-Komponenten tragen an etlichen Stellen noch Upstream-Element-Branding. Ziel: konsistentes aXion1337-Branding über Web + Desktop.

Ist-Stand:

Web: config.json setzt bereits brand: aXion1337.Chat + eigenes Theme — aber Upstream-Assets (Favicons, Logos, Wortmarke im Onboarding/Auth-Flow) sind noch Element.
Desktop: Installer heißt „Element Setup" (Default-VARIANT_PATH element.io/release/build.json), appId: im.riot.app, productName: Element, Element-Icons, Protokoll-Handler io.element.desktop/element.

Arbeitspakete:

Desktop-Variante apps/desktop/axion1337/build.json (eigenes appId/productName/Icons) + VARIANT_PATH in den CI-Jobs desktop_linux/desktop_windows setzen. ⚠️ appId-Wechsel = neues Install-/Profilverzeichnis für Bestandsnutzer (bewusst entscheiden, Migrationsnotiz).
Web-Assets: Favicon/Logo/Wortmarke gegen aXion-Varianten tauschen (Upstream-Merge-freundlich: eigene Dateien + Config-Referenzen statt Upstream-Dateien überschreiben, wo möglich).
Prüfen, welche Stellen Upstream regelmäßig anfasst (Merge-Reibung minimieren) — Ergebnis hier dokumentieren.

Teilaspekt Signing/Installer-Branding Windows: siehe #6 (bleibt dort für den Windows-Teil, dieses Issue ist die Gesamtklammer).

Migriert aus Gitea sorb/ThreadNet-Web#7 — dort erstellt am 2026-07-31 von sorb.

1.9 KiB Raw Blame History

Rebranding: Element → aXion1337 (Web + Desktop, Gesamtklammer)

1.9 KiB

Raw Blame History