As of: 2026-08-14 Owner: strategist, with maintainer approval for external contact
This is an evidence ledger, not a prospect list. It separates prepared material from outreach that was sent, on purpose. We list no organization as a TunaOS adopter without consent-confirmed public evidence in ADOPTERS.md.
| Channel | Prepared material | Sent? | Evidence / next action |
|---|---|---|---|
| DistroWatch | Submission draft, tracked by #1333 | No — draft only | Maintainer review and submission date are still required; record the submission URL and first referral snapshot here. |
| GNOME 51 release week | Release content draft, tracked by #1334 | No — draft ready | Maintainer review and timing for GNOME 51 upstream release week (~09-12). |
| CNCF / bootc showcase | Showcase draft & FOSDEM/CNCF section, tracked by #1340 | No — pitch explicitly not sent | A maintainer must approve the recipient/channel, send the pitch, and record the public thread or response. A bootc dependency is not an adoption reference. |
| Chainguard supply chain | Collaboration brief, tracked by #1339 | No — draft ready | Maintainer review required before initiating cold outreach on supply-chain collaboration. |
| Public adopter call | Consent workflow, tracked by #1367 | No Discussion URL yet | Create the Show-and-tell Discussion, then record response and consent-confirmed-entry counts in the call and monthly snapshot. |
- Replace No only with a date and a durable public link to the evidence.
- Record no-response and declined outreach but do not convert it into an adopter count.
- Keep production, development/evaluation, and anonymous reports as separate measures.
- Do not use stars, downloads, image pulls, CI jobs, or ecosystem rows as evidence of organizational adoption.