-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create org-wide repository for governance documents and templates #77
Comments
Please sign off in a comment if you agree or add your comments. |
Linking the Notary TOC issue - cncf/toc#981 |
👍 |
LGTM |
LGTM 👍 |
LGTM |
2 similar comments
LGTM |
LGTM |
Based on the responses above as well as the discussion in the Notary meeting from Jan 30th 2023 (https://hackmd.io/_vrqBGAOSUC_VWvFzWruZw) the decision is to proceed with this proposal and create |
Folks, I have created the repository https://github.com/notaryproject/.github and closing this issue as a result. Please look for some PRs in the new repository for approvals. |
As a result of the discussion in CNCF TOC regarding the status of the Notary project, we discussed in a few of the Notary meetings to increase the visibility of the governance documents as well as to update the list of maintainers. With this issue, I would like to propose to the community to move the governance documents from their current location (under the
notaryproject/notary
repo) to a standard.github
repo as per the following GitHub documentation https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-fileThe goal for the new repo will be to store the following governance documents:
As well as to create standard issue and PR templates as in https://github.com/notaryproject/notation/tree/main/.github/ISSUE_TEMPLATE that can be leveraged for all repos under the organization.
This proposal is to just migrate the documents to a central place. For updating the governance documents, adding new documents like SECURITY.md, or updating maintainers, we should file separate issue.
Filing in this repository as the most generic repository under the organization.
The text was updated successfully, but these errors were encountered: