-
Notifications
You must be signed in to change notification settings - Fork 5
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 Notary project GOVERNANCE.md #7
Comments
Repo
Any other options? Looking for comments from the maintainers and community. |
I vote for 1. The existing Notary governance doc is reusable and most of the content is still applicable to our community. We could migrate it to this repo and iterate it. Instead, it will confuse people if an organization has two different governance guidelines. I seldom see separate governance in a subproject. |
+1 for option1 |
+1 for option 1, but if we plan to move away from Notary and keep Notation we need to have appropriate plan in place. |
We agreed a while back that we will move the governance documents from the +1 on Option #1 |
@vaninrao10 could you explain what do you mean "keep Notation"? Both |
I will vote for option 1 as well. Now we have 5 out of 9 MAINTAINERS vote for option 1. We can make decision on Mar 20 community call. |
Steps (to be confirmed in community meeting on Mar 30)
|
There was an agreement in one of the community calls a few weeks back. Can't we just create the PR and copy the docs? There will be no changes to the docs as it was agreed upon in the community call. BTW, the maintainers of the |
LGTM |
Updates:
|
LGTM. Is there a PR for this work already created? |
Closing this one as per #17 |
The Notary governance document
GOVERNANCE.md
should cover the following aspects:The text was updated successfully, but these errors were encountered: