Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CODEOWNERS
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,11 @@
/ladder/teams/sig-policy.yaml @cilium/sig-policy
/ladder/teams/sig-scalability.yaml @cilium/sig-scalability
/ladder/teams/sig-servicemesh.yaml @cilium/sig-servicemesh
/ladder/teams/tetragon-bpf.yaml @cilium/tetragon-bpf
/ladder/teams/tetragon-committers.yaml @cilium/tetragon-committers
/ladder/teams/tetragon-docs.yaml @cilium/tetragon-docs
/ladder/teams/tetragon-reviewers.yaml @cilium/tetragon-reviewers
/ladder/teams/tetragon-windows.yaml @cilium/tetragon-windows
Comment on lines +55 to +59
Copy link
Copy Markdown
Member

@joestringer joestringer May 11, 2026

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.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

This seems ideal, thanks for more info on this :)

/ladder/teams/vendor.yaml @cilium/vendor
/ladder/teams/wireguard.yaml @cilium/wireguard
/ladder/teams/ztunnel.yaml @cilium/ztunnel
4 changes: 4 additions & 0 deletions ladder/teams/tetragon-bpf.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
members:
- kkourt
- mtardy
- olsajiri
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can add me here.

Copy link
Copy Markdown
Contributor

@andrewstrohman andrewstrohman May 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add me here too.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can also add me here.

2 changes: 2 additions & 0 deletions ladder/teams/tetragon-docs.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
members:
- mtardy
1 change: 0 additions & 1 deletion ladder/teams/tetragon-reviewers.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@ members:
- ExceptionalHandler
- FedeDP
- andrewstrohman
- jrfastab
- kevsecurity
- kkourt
- michi-covalent
Expand Down
2 changes: 2 additions & 0 deletions ladder/teams/tetragon-windows.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
members:
- ExceptionalHandler
Loading