Skip to content

owners: updating codeowners file#8365

Merged
alyssawilk merged 2 commits intoenvoyproxy:masterfrom
alyssawilk:owners
Sep 26, 2019
Merged

owners: updating codeowners file#8365
alyssawilk merged 2 commits intoenvoyproxy:masterfrom
alyssawilk:owners

Conversation

@alyssawilk
Copy link
Copy Markdown
Contributor

@alyssawilk alyssawilk commented Sep 25, 2019

Adding codeowners for unowned extension directories, mostly based on git blame, and sometimes based on maintainer suggestions.

As a reminder, codeowners are the people we'll generally default to for reviews of files in a given directory. An Envoy maintainer still has to LGTM in order to merge, and generally that'd end up being the maintainer listed in codeowners.

Risk Level: n/a
Testing: n/a
Docs Changes: n/a
Release Notes: n/a

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
@alyssawilk
Copy link
Copy Markdown
Contributor Author

alyssawilk commented Sep 25, 2019

@snowp @alyssawilk @eziskind @htuch @mattklein123 @zuercher @gsagula @dio @jose @rshriram @qiwzhang @lizan @fengli79 @lavignes @yuval-k @klarose @PiotrSikora @wozz @taiki45 @trabetti @ramaraochavali

If you're not comfortable doing reviews for the files specified here, please either comment here or take it up with me offline and I'll remove your handle and look into alternates.

Also if anyone values the comment blocks I can add them in but I find the directory name generally sufficient. WDYT?

mattklein123
mattklein123 previously approved these changes Sep 25, 2019
Copy link
Copy Markdown
Member

@mattklein123 mattklein123 left a comment

Choose a reason for hiding this comment

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

Thanks for putting this together.

snowp
snowp previously approved these changes Sep 25, 2019
CODEOWNERS Outdated
/*/extensions/filters/http/router @alyssawilk @mattklein123 @snowp
/*/extensions/filters/http/ext_authz @gsagula @dio
/*/extensions/filters/http/grpc_web @fengli79 @lizan
/*/extensions/filters/http/common/aws @lavignes @dio
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I did cover this on line 51

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Just wanted to call it out especially since the two lines didn't match :)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

oh good catch, thanks! Must have been after we landed the fix format checks and we just forgot to take it out.

htuch
htuch previously approved these changes Sep 25, 2019
Copy link
Copy Markdown
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

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

Thanks!

zuercher
zuercher previously approved these changes Sep 25, 2019
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
@alyssawilk alyssawilk dismissed stale reviews from zuercher, htuch, snowp, and mattklein123 via 3ff9160 September 25, 2019 17:08
@alyssawilk alyssawilk merged commit 1f32830 into envoyproxy:master Sep 26, 2019
danzh2010 pushed a commit to danzh2010/envoy that referenced this pull request Oct 4, 2019
Adding codeowners for unowned extension directories, mostly based on git blame, and sometimes based on maintainer suggestions.

As a reminder, codeowners are the people we'll generally default to for reviews of files in a given directory. An Envoy maintainer still has to LGTM in order to merge, and generally that'd end up being the maintainer listed in codeowners.

Risk Level: n/a
Testing: n/a
Docs Changes: n/a
Release Notes: n/a

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
@alyssawilk alyssawilk deleted the owners branch April 20, 2020 13:29
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.