Update CODEOWNERS: Aug 2026 - #24847
Conversation
As a follow-up on bff05a9, fill in the current Codeowners file with TSC members, as well as nominate additional reviewers. Contributors who are removed from the list for large scopes: the proposal makes a loose assumption that they are no longer actively developing and/or reviewing the affected segments of the codebase. Thus, the PR should only go in once it satisfies edit requests and a general approval by such long-standing contributors and code owners. There's little to no fine-graining of directory scopes in this PR. A handful of directories is removed from the list as either outdated or as a way of (temporarily?) transfering the default code ownership thereof to higher-level code owners. Any contributor, regardless of TSC membership, is generally free to volunteer for the existing or narrower review scopes, as well as offload notifications and first-point-of-contact duties to other project members. Signed-off-by: Artem Gindinson <gindinson@roofline.ai>
779e356 to
de94336
Compare
Signed-off-by: Artem Gindinson <gindinson@roofline.ai>
|
Hey folks, I'll keep the PR open for several days, and hopefully I haven't missed anyone in the ping below. Many thanks! @ScottTodd @Groverkss @kuhar @amd-eochoalo @MaheshRavishankar @IanWood1 @hanhanW @Max191 @qedawkins @nirvedhmeshram @krzysz00 @rsuderman @keshavvinayak01 @antiagainst @AWoloszyn |
Signed-off-by: Artem Gindinson <gindinson@roofline.ai>
Signed-off-by: Artem Gindinson <gindinson@roofline.ai>
Signed-off-by: Artem Gindinson <gindinson@roofline.ai>
Signed-off-by: Artem Gindinson <gindinson@roofline.ai>
edf6553 to
9dbd52d
Compare
amd-eochoalo
left a comment
amd-eochoalo
left a comment
There was a problem hiding this comment.
Just removing myself from CODEOWNERs. Thanks!
Signed-off-by: Artem Gindinson <gindinson@roofline.ai> Co-authored-by: Erick Ochoa Lopez <eochoalo@amd.com>
ScottTodd
left a comment
ScottTodd
left a comment
There was a problem hiding this comment.
LGTM for removing codeowners entries for me (I'm still watching the repository and around on Discord to help with questions 😄)
| # Default to members of the IREE TSC | ||
| * @AGindinson @devtbi @jschuhmacher @schuermans-roofline |
There was a problem hiding this comment.
You could also create a github team for the TSC (https://github.com/orgs/iree-org/teams)
There was a problem hiding this comment.
Good suggestion, thanks Scott! I'll probably do this as a follow-up, we might as well revise/set up teams for component reviews
Signed-off-by: Artem Gindinson <gindinson@roofline.ai>
124663c to
1f5a5a4
Compare
|
Soft ping here if anyone would like to add feedback. We could merge this in a couple days. |
Signed-off-by: Artem Gindinson <gindinson@roofline.ai>
Signed-off-by: Artem Gindinson <gindinson@roofline.ai>
8 participants
As a follow-up on bff05a9, fill in the current Codeowners file with TSC members, as well as nominate additional reviewers.
Contributors who are removed from the list for large scopes: the proposal makes a loose assumption that they are no longer actively developing and/or reviewing the affected segments of the codebase. Thus, the PR should only go in once it satisfies edit requests and a general approval by such long-standing contributors and code owners.
There's little to no fine-graining of directory scopes in this PR. A handful of directories is removed from the list as either outdated or as a way of (temporarily?) transfering the default code ownership thereof to higher-level code owners.
Any contributor, regardless of TSC membership, is generally free to volunteer for the existing or narrower review scopes, as well as offload notifications and first-point-of-contact duties to other project members.