-
Notifications
You must be signed in to change notification settings - Fork 579
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
Move Aneurysm9 to emeritus status #5533
Conversation
Signed-off-by: Anthony J Mirabella <[email protected]>
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.
Should we open issues to track the components that are now missing CODEOWNERS? Or do we know of anyone who would be a good fit?
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.
Fist of all, thanks for your contributions to the project 🙏
If it is not you then are you able to find someone in AWS who could be a codeowner of AWS detectors and instrumentations?
I have some people internally I'm going to reach out to about taking the code owner role for the AWS components in this repo, but don't have any names to give at this time. If you'd like me to keep my name on them in the interim I can do so, but will be responsive on a best-effort basis. |
I think it will be a lot better than having nobody. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5533 +/- ##
=======================================
- Coverage 62.7% 62.7% -0.1%
=======================================
Files 192 192
Lines 11786 11786
=======================================
- Hits 7401 7399 -2
- Misses 4169 4170 +1
- Partials 216 217 +1 |
I have been unable to provide this position the bandwidth that it deserves and it is time to formalize recognition of that fact.