Currently, the federated template does not contain a section for how the governance document should be updated. @jberkus fyi.

Operator Framework is currently using this template

Below is a draft to share what I have in mind, it is a WIP PR. Following the Operator Framework governance merge (and the language below settles), I'd be happy to open a PR here. Suggestions welcome :)

## Governance Amendments

The Operator Framework Community may adopt or amend its Governing
Documents according to the following process:

1. Propose a change by opening an issue in the community repository, and if there
   seems to be general agreement, open a pull request to this document.
2. The change should be announced via the mailing list along with an invitation for discussion on the Pull Request.
3. A minimum of 7 days must pass between the announcement and the vote. If there is not consensus, the Steering Committee is encouraged to delay the vote. The Steering Committee can pass the amendment with a 2/3 majority and a minimum quorum of 1/2 of the Committee.

We noticed that users and contributors of cloud native projects care a lot about why a certain technical decision was taken.

In our Kubernetes distribution, we use Markdown Any Decision Records. In essence, you create a folder docs/adr with a file template.md. Then you copy the template for each decision you take. Here is an example on how this would look like.

Would it be beneficial to include this in the CNCF project template?

There is broken link reference to an OWNERS file in https://github.com/cncf/project-template/blob/main/GOVERNANCE-maintainer.md:

[TODO: PROJECTNAME] Maintainers have write access to the [project GitHub repository](TODO).
They can merge their own patches or patches from others. The current maintainers
can be found in [OWNERS](./OWNERS).  Maintainers collectively manage the project's
resources and contributors.

However, I do not see an OWNERS file in the cncf/project-template repository. Would it be possible to provide a sample OWNERS file? From what I've seen, I think the file is just the GitHub usernames of the owners? If it doesn't make sense to add a sample OWNERS file, perhaps removing the broken link to the file in the GOVERNANCE-maintainer.md would be less confusing.

Add a link to the sig-security docs in the README instructions so that they know to copy in the other files.

https://contribute.cncf.io/maintainers/github/templates/

The templates are explained on the website but we should remind people about them here too.

I'm not sure who has permission to merge PRs in this repo, so I keep pinging @amye to merge things. Would it be possible for @jberkus and I to get the permissions required to merge PRs?

I promise that we won't merge anything unless we have TOC liaison approval, but allowing us to merge would reduce the load for Amye and the TOC :)

cc: @TheFoxAtWork & @dzolotusky