01Project Bluefin / community
End User Community
The humans behind the test signal
Built by people who use Linux every day.
A living snapshot of the public members of the projectbluefin GitHub organization — the folks shaping the images, fixing the rough edges, and keeping the feedback loop honest.
9people in the
Bluefin orbit
Bluefin orbit
01
02GNOME community, desktop Linux, and the people who make it possible.
◌ Portland, USA
03
04
05
06Open source builder and Bluefin advisor.
07bootc creator · atomic desktops and reliable foundations.
08Bluefin advisor · infrastructure, Linux, and community.
09Open source advocate and Bluefin advisor.
Field notes / real systems
How the factory is put together.
Reference cards built from this lab's actual GitOps manifests, workflows, and operating docs — not a generic cloud diagram.
01Build & cache
BuildStream → BuildBarn
USB4-gated distributed builds move BuildStream actions to workers while BuildBarn owns the artifact, source, action, and CAS layers.
Git ref→BuildStream→BuildBarn RE→OCI
BuildStreamBuildBarnArgoUSB4
Inspect build telemetry ↗02Test & observe
Image → QA matrix
Published Bluefin lanes are polled by digest, dispatched into suite-specific Argo workflows, and recorded as evidence instead of vibes.
OCI digest→QA lanes→Results
Argo WorkflowsBehaveKubeVirtZot
Inspect test matrix ↗03Publish & release
Digest → release verdict
Factory signals join image freshness, build history, QA evidence, and security posture before a lane earns a useful verdict.
Build+QA+Security→Verdict
GitHubGHCRGrypeEvidence
Inspect release evidence ↗04Build & cache
Two-node lab fabric
Ghost and exo-0 share a deliberately explicit topology: node-local XFS storage, sharded CAS, workers on both nodes, and no silent fallback.
ghost⇄USB4⇄exo-0
XFSNVMelocal-pathRemote execution
Inspect lab capacity ↗05Test & observe
GitOps control plane
Tracked manifests reconcile through Argo CD; resource health, drift, policy checks, and rollout state stay visible to operators.
Git→Argo CD→Cluster
Argo CDKubernetesPolicyMetrics
Inspect GitOps state ↗06Publish & release
Local registry edge
Zot stores the lab's writable image results while registry mirrors reduce repeated upstream pulls for test and build workloads.
GHCR→Mirror→Zot→QA
ZotRegistry mirrorOCIDigest pinning
Inspect image lanes ↗No people match that search. Try a name, handle, or location.