Skip to content

Conversation

@mtardy
Copy link
Member

@mtardy mtardy commented Oct 22, 2025

And also add the tetragon-reviewers empty team for now for people that want to join the project and climb the contributor ladder.

And also add the tetragon-reviewers empty team for now for people that
want to join the project and climb the contributor ladder.

Signed-off-by: Mahe Tardy <[email protected]>
@joestringer
Copy link
Member

joestringer commented Oct 22, 2025

Interesting the linter probably doesn't like the empty member list there. I don't know if the new empty line causes problems with YAML formatting in interpreting the list... Simple answer here might just be to run ./tools/generate-reviewers.sh and YOLO :shipit: .

Practically speaking for existing members of the tetragon team I don't think this reflects any change in reality. It does however clearly open up a path for newer contributors to move up the ladder to reviewer in the way documented in this repository. I think that would be a good step forward. Needless to say though any change to Tetragon subproject structure would be subject to @cilium/tetragon / @cilium/tetragon-maintainers approval (typically lazy consensus, but I would encourage involvement from you all!).

I'd be happy to help ensure the org behind the scenes follows this desired state if the PR is approved. (Basically rename the team, create the new one and link up the config from this repo to the reality; subsequent changes would be reflected automatically after merge)

Copy link
Member

@xmulligan xmulligan left a comment

Choose a reason for hiding this comment

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

I think we need a different name for this team because it could easily be confused with the overall project committers in https://github.com/cilium/cilium/blob/main/MAINTAINERS.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants