Skip to content

docs: fix CoC contact link and CNCF name in CODE_OF_CONDUCT.md - #2251

Merged
John15321 merged 1 commit into
flatcar:mainfrom
Priyanshubhartistm:fix-coc-contact-info-inconsistency
Jul 31, 2026
Merged

docs: fix CoC contact link and CNCF name in CODE_OF_CONDUCT.md#2251
John15321 merged 1 commit into
flatcar:mainfrom
Priyanshubhartistm:fix-coc-contact-info-inconsistency

Conversation

@Priyanshubhartistm

@Priyanshubhartistm Priyanshubhartistm commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Why

CODE_OF_CONDUCT.md had two small but real problems in its contact line:

  1. The private Maintainer mailing list link was missing the mailto: scheme, so instead of opening an email client it rendered as a broken/relative link. This is the same bug that was just fixed in governance.md (docs: fix broken maintainer mailing list links in governance.md #2244) - just in a different file.
  2. "Cloud Native Foundation" is not a real organization - CNCF stands for Cloud Native Computing Foundation, and that's the name used correctly everywhere else in this repo (see README.md, governance.md).

What changed

  • CODE_OF_CONDUCT.md: added mailto: to the maintainer mailing list link, and corrected "Cloud Native Foundation" to "Cloud Native Computing Foundation".

Open question / not addressed here

While looking at this I noticed the three docs that describe how to report a CoC violation each name a different secondary contact:

  • README.md points to a named Linux Foundation mediator (Mishi Choudhary)
  • CODE_OF_CONDUCT.md points to a generic CNCF email (conduct@cncf.io)
  • governance.md points to an unnamed CNCF Code of Conduct Committee

I don't know which of these is actually current/correct, so I'm not guessing at a reconciliation here - this PR only fixes the mechanical link/name issues. Flagging in case a maintainer wants to pick one canonical contact path across all three files as a follow-up.


Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
@John15321
John15321 merged commit 5b280fc into flatcar:main Jul 31, 2026
1 check passed
@github-project-automation github-project-automation Bot moved this from ✅ Testing / in Review to Implemented in Flatcar tactical, release planning, and roadmap Jul 31, 2026
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.

3 participants