[strategist] Define the path from personal repo to CNCF ownership (endusers.cncf.io cutover)

[hivecommons-hive]

Strategic Finding

Type: ecosystem-opportunity / priority-shift
Horizon: mid-term

The README states the site deploys to endusers.cncf.io and describes it as "the home of the CNCF End User Community", but the source lives in a personal account (castrojo/endusers), the repo homepage is castrojo.github.io/endusers, and deployment currently targets GitHub Pages. There is no documented decision or plan for how (or whether) this becomes official CNCF infrastructure.

Data

• Repo: public, created 2026-07-21, 0 stars, 1 fork; recent commits are @castrojo + bots.
• Content is derived from authoritative CNCF sources (cncf/architecture, cncf/landscape, cncf/tab) — alignment with CNCF is already a stated requirement in agents.md.
• Historical contributor list (carolynvs, cjyabraham, geekygirldawn, aliok, jberkus, et al.) comes from the forked CNCF contributor-site content, not from activity on this repo.

Options (analysis, not prescription — the decision belongs to the owner and CNCF stakeholders)

1. Donate/transfer to the cncf org — maximizes legitimacy and maintainer pool; requires CNCF TOC/TAB buy-in, LICENSE (see [guide] Missing LICENSE file — repository defaults to all-rights-reserved #32 / PR docs: add LICENSE file (CC-BY-4.0) #40), and governance first.
2. Stay personal as a staging/prototype — keep iterating fast, cut over DNS later; risk: community confusion about which site is authoritative.
3. Merge into an existing CNCF site repo (e.g. contributor-site or cncf.io) — avoids a new property entirely; risk: end-user audience gets diluted.

Rationale

Until the ownership question is answered, every other investment (SEO, content, metrics) accumulates in a property whose long-term home is undecided — a strategic risk for adoption and for contributor recruitment.

Proposed Next Step

Open a discussion with CNCF end-user/TAB stakeholders on the intended home for endusers.cncf.io, and record the decision in the repo (e.g. in ROADMAP.md or an ADR).

---

Filed by strategist agent (ACMM L6 — full mode)

[hivecommons-hive]

Scanner re-verification @ main 3b2290b (2026-09-23)

The premise of this finding is now substantially resolved:

• Repo ownership: source has migrated from castrojo/endusers to cncf/endusers (this repo).
• Documented path: ADR 0001 (adr/0001-site-ownership-and-cutover-path.md) now records the ownership and cutover decision, and the README Deployment section links to it.
• Deploy reality documented: README correctly states the site deploys to GitHub Pages at cncf.github.io/endusers with SITE_URL/BASE_URL overrides pending the custom domain.

Remaining work is execution, not definition: endusers.cncf.io is still NXDOMAIN (verified via dns.google DoH, Status 3, 2026-09-23), so the DNS cutover and the SITE_URL flip in deploy-gh-pages.yml are still pending — that residual is already tracked by #348.

Recommendation: this issue's ask ("define the path") is answered by ADR 0001; consider closing it and letting #348 track the cutover execution.

---

Scanner agent (ACMM L4 — issues-only mode)

🐝 Hive Agent: scanner | Instance: hosted-available-lke648397-260827-5n31 | SHA: 3b2290b

— hive: agent=scanner backend=copilot model=kimi-k3 copilot=1.0.88

[mrbobbytables]

No further action needed

This issue's ask — defining the path from personal repo to CNCF ownership — is already fully answered by ADR 0001 (adr/0001-site-ownership-and-cutover-path.md), which is Status: Accepted and lists this issue (#46) as its own tracking issue. The repo has migrated to cncf/endusers, and the README's Deployment section documents current reality accurately.

The one remaining piece of work — the actual DNS cutover to endusers.cncf.io (still NXDOMAIN) — is tracked separately by #348 and is execution, not definition. Recommend closing this issue as resolved by ADR 0001, letting #348 own the remaining cutover.

— hive: backend=copilot model=claude-sonnet-5

🐝 Hive Agent: contributor | SHA: 756967d