Skip to content

docs: consolidate README deployment section and ADR 0001 status - #246

Open
mrbobbytables wants to merge 1 commit into
mainfrom
fix/consolidate-readme-adr-deploy-233
Open

mrbobbytables wants to merge 1 commit into
mainfrom
fix/consolidate-readme-adr-deploy-233

Conversation

@mrbobbytables

Copy link
Copy Markdown
Member

Fixes #233.

Problem

PRs #167, #201, and #203 all rewrite the same README ## Deployment section and/or ADR 0001's Status field, with different (sometimes contradictory) wording. #201 and #203 are both currently mergeable and touch overlapping hunks of README.md; whichever merges first strands the other, and #167 (already CONFLICTING) records a different ADR outcome (Accepted vs Superseded by transfer).

What this does

Picks one, fact-checked version of each contested section as the single source of truth:

  • README ## Deployment: documents what is actually true right now — the site is served by GitHub Pages at cncf.github.io/endusers (confirmed via the live GET /repos/cncf/endusers/pages API response: html_url is http://cncf.github.io/endusers/, cname is null) rather than the aspirational endusers.cncf.io, which has no DNS record or static/CNAME yet.
  • ADR 0001: records that Option A (transfer to the cncf GitHub org) has been executed — provable from the repo now living at cncf/endusers — without asserting an unverified formal CNCF TOC/TAB vote (this addresses @castrojo's review comment on docs: record CNCF org transfer decision in ADR 0001 and project plans (issue #46) #167 asking to narrow the ADR to facts GitHub metadata proves, or cite a real decision source). Remaining DNS cutover to endusers.cncf.io is tracked as still open, matching the actual GitHub Pages state above.
  • adr/README.md: status table updated to match (ProposedAccepted).
  • adr/0001-stakeholder-outreach-draft.md: marked historical, since the transfer already happened.
  • package.json: repository.url now points at cncf/endusers.

Intentionally left out

Follow-up

Once this merges, #167, #201, and #203 should be closed or rebased to drop their now-redundant README/ADR hunks (#167 also carries other independent changes — LAUNCH.md/ROADMAP.md/MAINTAINERS.md updates and the SITE_URL workflow fix — which can be rebased on top of this if still wanted).

— hive: backend=copilot

🐝 Hive Agent: contributor | SHA: f43da47

Three open PRs (#167, #201, #203) independently rewrite the same
README Deployment section and ADR 0001 status, and would strand each
other on merge (issue #233). This picks a single, fact-checked source
of truth instead:

- README: document the actual current deployment (GitHub Pages at
  cncf.github.io/endusers) rather than the aspirational
  endusers.cncf.io domain, which has no DNS record or CNAME yet
  (verified against the live GitHub Pages API response).
- ADR 0001: record that Option A (transfer to the cncf GitHub org) has
  been executed, per repository metadata, without asserting an
  unverified formal TOC/TAB vote. The remaining DNS cutover is tracked
  as still open.
- adr/README.md: update the status table to match.
- package.json: repository.url now points at cncf/endusers.

Note: the .github/workflows/deploy-gh-pages.yml SITE_URL fix (still
pointing at the old castrojo.github.io host) and docusaurus.config.js
(already covered by #245) are intentionally left out of this PR — the
former needs a token/PR with 'workflow' scope, tracked as a fast
follow so it isn't lost.

Once this lands, PRs #167, #201, and #203 should be closed or rebased
to drop their now-redundant README/ADR hunks.

Fixes #233

Signed-off-by: mrbobbytables <mrbobbytables@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[scanner] PRs #167, #201, #203 overlap on the same README Deployment section and ADR 0001 status — merging any one strands the others

1 participant