Skip to content

Add Community Specification governance - #4

Draft
fkautz wants to merge 1 commit into
mainfrom
lf/governance-and-notices
Draft

Add Community Specification governance#4
fkautz wants to merge 1 commit into
mainfrom
lf/governance-and-notices

Conversation

@fkautz

@fkautz fkautz commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add the Community Specification governance policy for the SAF-K8S control catalog.
  • Add Contributor Covenant 2.0 and repository-specific reporting contacts.
  • Add Community Specification license acceptance, withdrawal, and patent exclusion notices.
  • Link the governance and notice documents from the license, scope, and generated README.
  • Update the Markdown generator so governance information and LF Projects notices remain reproducible.

Motivation

The SAF-K8S catalog is licensed under the Community Specification License 1.0 but did not include the corresponding governance, participation, and notice documents. This change documents how the Working Group operates, bounds the governed specification content, and provides the records required by the Community Specification process.

Impact

Contributors and users can now identify the Working Group's roles, decision process, scope, conduct requirements, license acceptance process, withdrawals, and patent exclusions directly from the repository. Generated README updates will preserve the governance and LF Projects references.

Validation

  • Ran generate_markdown.py successfully with PyYAML 6.0.3.
  • Confirmed generation changed only the expected README content.
  • Ran git diff --cached --check before committing.
  • Included the required DCO sign-off.

Signed-off-by: Frederick F. Kautz IV <fkautz@alumni.cmu.edu>
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.

1 participant