-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Add GOVERNANCE.md #530
Add GOVERNANCE.md #530
Conversation
Signed-off-by: Yuri Shkuro <ys@uber.com>
3c6725b
to
8187590
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only a few minor comments.
GOVERNANCE.md
Outdated
@@ -0,0 +1,53 @@ | |||
# Jaeger Governance | |||
|
|||
This document defines project governance for the Jaeger project. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: could remove the first 'project'.
GOVERNANCE.md
Outdated
* understanding of how the team works (policies, processes for testing and code review, etc), | ||
* understanding of the projects' code base and coding style. | ||
|
||
A new maintainer must proposed by an existing maintainer by sending email to jaeger-maintainers@lists.cncf.io |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"must be proposed by"
"by sending an email"
Signed-off-by: Yuri Shkuro <ys@uber.com>
* understanding of how the team works (policies, processes for testing and code review, etc), | ||
* understanding of the projects' code base and coding style. | ||
|
||
A new maintainer must be proposed by an existing maintainer by sending an email to jaeger-maintainers@lists.cncf.io |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be done via a public forum, whether a public mailing list or github issue
Resolves #253 and #403.