-
Notifications
You must be signed in to change notification settings - Fork 104
tetragon: create new specialized review teams #411
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| members: | ||
| - kkourt | ||
| - mtardy | ||
| - olsajiri | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can add me here.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please add me here too.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You can also add me here. |
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| members: | ||
| - mtardy |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| members: | ||
| - ExceptionalHandler |
Uh oh!
There was an error while loading. Please reload this page.
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.
Just as a heads up for expectations around these:
We implement a similar pattern for CODEOWNERS for teams used by cilium/cilium. The idea we have for this is that each team is responsible for review & quality in the target area, and they should have the most context about any potential changes in the team membership, whether adding or removing people. Ultimately though for cilium/cilium the decision is up to the (Cilium) Committer group, and all PRs to membership in this repository are expected to have two approvals from (Cilium) Committers. Only the (Org) committers can merge PRs into this repository.
For ebpf-go library the owners are managed slightly differently, it's just the core maintainer group that approves all changes to all teams for that subproject.
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 seems ideal, thanks for more info on this :)