Skip to content

Commit 32e2cd3

Browse files
authored
Add GOVERNANCE.md (#530)
1 parent da7e633 commit 32e2cd3

File tree

1 file changed

+53
-0
lines changed

1 file changed

+53
-0
lines changed

GOVERNANCE.md

+53
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# Jaeger Governance
2+
3+
This document defines governance policies for the Jaeger project.
4+
5+
## Maintainers
6+
7+
Jaeger Maintainers have write access to the Jaeger GitHub repository https://github.com/jaegertracing/jaeger.
8+
They can merge their own patches or patches from others.
9+
10+
This privilege is granted with some expectation of responsibility: maintainers are people who care about the Jaeger project and want to help it grow and improve. A maintainer is not just someone who can make changes, but someone who has demonstrated his or her ability to collaborate with the team, get the most knowledgeable people to review code, contribute high-quality code, and follow through to fix issues (in code or tests).
11+
12+
A maintainer is a contributor to the Jaeger project's success and a citizen helping the project succeed.
13+
14+
## Becoming a Maintainer
15+
16+
To become a maintainer you need to demonstrate the following:
17+
18+
* commitment to the project
19+
* participate in discussions, contributions, code reviews for 3 months or more,
20+
* perform code reviews for 10 non-trivial pull requests,
21+
* contribute 10 non-trivial pull requests and have them merged into master,
22+
* ability to write good code,
23+
* ability to collaborate with the team,
24+
* understanding of how the team works (policies, processes for testing and code review, etc),
25+
* understanding of the projects' code base and coding style.
26+
27+
A new maintainer must be proposed by an existing maintainer by sending an email to jaeger-maintainers@lists.cncf.io
28+
(please do not CC the nominee on the nomination email) containing the following information:
29+
30+
* nominee's first and last name,
31+
* nominee's email address and GitHub user name,
32+
* an explanation of why the nominee should be a committer,
33+
* a list of links to non-trivial pull requests (top 10) authored by the nominee.
34+
35+
Two other maintainers need to second the nomination. If no one objects in 5 working days (U.S.), the nomination is accepted. If anyone objects or wants more information, the maintainers discuss and usually come to a consensus (within the 5 working days). If issues can't be resolved, there's a simple majority vote among current maintainers.
36+
37+
## Changes in Maintainership
38+
39+
Maintainers can be removed by a 2/3 majority vote by maintainers.
40+
41+
## GitHub Project Administration
42+
43+
Maintainers will be added to the GitHub @jaegertracing/jaeger-maintainers team, and made a GitHub maintainer of that team.
44+
They will be given write permission to the Jaeger GitHub repository https://github.com/jaegertracing/jaeger.
45+
46+
## Changes in Governance
47+
48+
All changes in Governance require a 2/3 majority vote by maintainers.
49+
50+
## Other Changes
51+
52+
Unless specified above, all other changes to the project require a 2/3 majority vote by maintainers.
53+
Additionally, any maintainer may request that any change require a 2/3 majority vote by maintainers.

0 commit comments

Comments
 (0)