From 892d8d60202b6e4f1ce59963102497c77ffa166b Mon Sep 17 00:00:00 2001 From: Bill Mulligan Date: Fri, 12 May 2023 18:26:29 +0200 Subject: [PATCH] Remove governance as optional for sandbox Signed-off-by: Bill Mulligan --- website/content/maintainers/governance/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/maintainers/governance/overview.md b/website/content/maintainers/governance/overview.md index d48a1948..4d6062db 100644 --- a/website/content/maintainers/governance/overview.md +++ b/website/content/maintainers/governance/overview.md @@ -60,7 +60,7 @@ There is a short list of P&P that every CNCF project is expected to have, and a ## Accurately Documenting Your Governance -Like technical documentation, governance documentation should explain how things actually work. If there are aspirational goals, those go in their own section under Roadmap or TODO. Remember, if you are a Sandbox or Incubating project, you aren’t expected to have all of these things sorted out yet. +Like technical documentation, governance documentation should explain how things actually work. If there are aspirational goals, those go in their own section under Roadmap or TODO. It can be tempting to define your project as you would like it to be (or how you would like to present it to the CNCF TOC) rather than how it actually is. Particularly, project leaders frequently make the mistake of attempting to make the project appear more organized and mature than it actually is, in documentation. This falls apart when users or contributors expect your project to live up to its governance documentation, and it doesn't. People who would have been fine with being told a project was single-company at the outset become very upset if they ask for their committer status and are refused later. For that matter, the CNCF TOC requires projects to be accurate about the things they are still working on, and inaccuracy may delay project acceptance or maturation.