☁️♮🏛Cloud Native Computing Foundation Policy Repo

This repo contains several documents related to the operation of the Cloud Native Computing Foundation.

Governance

• The charter under which CNCF operates
• Maintainer election policy for the maintainer-elected TOC member and the two maintainers on the governing board
• The membership agreement
• The Code of Conduct which has been translated into multiple languages

Project Guidance

• Copyright notice recommendations
• Website guidelines for mentioning companies while maintaining neutrality
• Allowlist License Policy for which licenses are acceptable in upstream dependencies without requiring an explicit vote of the governing board

Community recommendations

• CNCF Blog Guidelines outlining who can submit, suggested topics, and how to submit.
• A style guide with recommendations for cloud native terminology
• A translation guide for the Chinese equivalent of cloud native phrases

Other content

A lot of project, TAG, and TOC-related content is in the TOC repo. cncf.io has information on all programs offered publicly by CNCF.

Project maintainers

CNCF project maintainers are recorded in two files:

• project-maintainers-.project.csv — the primary list. It is generated automatically for projects that manage their maintainers in their own .project repo. To change these maintainers, update maintainers.yaml in the project's .project repo; the change is picked up by automation. Do not edit project-maintainers-.project.csv directly — any manual edits are overwritten.
• project-maintainers.csv — a legacy list for the projects not yet onboarded to the .project process. An existing maintainer of one of these projects can update it by Pull Request, and should also email cncf-maintainer-changes@cncf.io (or raise a service desk ticket) so the project's CNCF-run maintainer mailing list is updated to match.

Access to the CNCF Service Desk and project maintainer mailing lists is controlled by the link between a maintainer's GitHub handle and their LFID, which can be updated at openprofile.dev. The name and affiliation shown in this generated list are also taken from the LFID profile.

Keep these records in sync: update maintainer membership in the project's .project/maintainers.yaml, keep each maintainer's name, primary email, and current affiliation accurate in their LFID profile, and ensure current affiliations are shown in the project's public maintainer or governance documentation. The .project/maintainers.yaml file records GitHub handles and teams; changing it does not update LFID or project documentation, and updating a profile does not update the project repository.

Questions about maintainer records can be sent to cncf-maintainer-changes@cncf.io.

How to request changes

You are welcome to file non-technical issues related to CNCF on this repo.