You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTOR_LADDER.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ To apply to become a member of the kgateway-dev organization on GitHub, please o
50
50
1. Use the [membership request template](.github/PULL_REQUEST_TEMPLATE/apply_to_be_a_member.md). This template is linked from the default template when you open a PR, or you can paste this URL in your browser `https://github.com/kgateway-dev/community/compare/main...<my-fork>:<my-branch>?quick_pull=1&title=Request%20org%20membership%20for%20<user>&labels=membership&template=apply_to_be_a_member.md`, replacing:
51
51
-`<my-fork>:<my-branch>` with your fork/branch name, and
52
52
-`<user>` with your GitHub username
53
-
1. Add your GitHub username to the list of members (under `orgs.kgateway-dev.members` and `orgs.kgateway-dev.teams.org-members.members`) in our [organization file](./org.yaml). Please add your name in the correct alphabetical order to maintain a tidy organization file.
53
+
2. Add your GitHub username to the list of members (under `orgs.kgateway-dev.members` and `orgs.kgateway-dev.teams.org-members.members`) in our [organization file](./org.yaml). Please add your name in the correct alphabetical order to maintain a tidy organization file.
54
54
55
55
### Maintainer
56
56
@@ -75,11 +75,20 @@ A Maintainer must meet the responsibilities and requirements of an Organization
75
75
76
76
Any current Maintainer may nominate a current Organization Member to become a new Maintainer in one or more repositories, by opening a PR in the community repository using the [maintainer nomination template](.github/PULL_REQUEST_TEMPLATE/nominate_a_maintainer.md). The following requirements must be met before the PR is merged:
77
77
1. Each item in the template checklist must be satisfied.
78
-
1. At least 2 current Maintainers from each relevant repository must approve the PR.
79
-
1. There must be no objections from other maintainers. This can be achieved by either of the following, whichever occurs first:
78
+
2. At least 2 current Maintainers from each relevant repository must approve the PR.
79
+
3. There must be no objections from other maintainers. This can be achieved by either of the following, whichever occurs first:
80
80
* Leaving the PR open for one week with no objections
81
81
* Asking at the weekly community meeting whether there are any objections
82
82
83
+
### Becoming a CODEOWNER
84
+
85
+
You must already be a Maintainer of kgateway to become a CODEOWNER.
86
+
87
+
1. Review at least 5 PRs and author 5 PRs in the repository under the specific CODEOWNERS group
88
+
2. Get nominated by an existing CODEOWNER of that group and update the org.yaml and get a +1 from another CODEOWNER
89
+
90
+
Additional specific CODEOWNER requirements can be decided by the CODEOWNER group and the community as needed.
91
+
83
92
## Inactivity
84
93
85
94
It is important for contributors to be and stay active to set an example and show commitment to the project. Inactivity is harmful to the project as it may lead to unexpected delays, contributor attrition, and a lost of trust in the project.
0 commit comments