Jeff (@jeffmakes)
The public hardware repository is hosted under Jeff's GitHub account.
SourceTROOPERS23 · Germany · 2023
Badge.Team retro-adventure conference badge
A Badge.Team-powered TROOPERS23 electronic badge with a public retrospective PDF, open hardware repository, firmware repository, and companion SAO hardware repository.
People
The public hardware repository is hosted under Jeff's GitHub account.
SourceThe public TROOPERS23 firmware repository is hosted under the Badge.Team GitHub organization.
SourceTROOPERS23 fills an important gap between the minimal TROOPERS22 record and the better-documented modern Badge.Team style: it has official post-event badge storytelling plus public implementation repositories.
TROOPERS23's badge design is anchored by a public hardware repository, and a companion SAO add-on board is documented in a separate SAO repository. Component-level claims should continue to track the published schematics and BOM rather than be copied from memory.
TROOPERS23's badge has a source-backed firmware trail in the Badge.Team ecosystem, given by the public badgeteam/troopers-2023-firmware repository, making it stronger than a mere event-page sighting.
The official TROOPERS23 badge retrospective frames the badge as a conference artifact with its own story, while the separate hardware, firmware, and SAO repositories make it useful for future badge teams studying how Badge.Team-era conference badges were assembled.
Lifecycle
The separate tr23-sao-hw repository documents a companion SAO board for the TROOPERS23 badge.
SourceThe public Badge.Team firmware repository gives the badge a recoverable software trail instead of leaving the dossier at a hardware-only record.
SourceOperational history
The catalogue publishes the record without a badge image until an original licensed photo can replace it.
This keeps the record useful without turning repository existence into unverified hardware-spec prose.