Update ai codeowners

[kingernupur]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[kashifkhan]

we cant remove the team entirely. We should add granular level access for the folks who are still DRI for their respective projects

[kingernupur]

we cant remove the team entirely. We should add granular level access for the folks who are still DRI for their respective projects

@kashifkhan I haven't removed the team entirely. There are still relevant team members in the AI Service label. I have modified the to remove my team members since we are getting incorrectly tagged in AI issues like these AI Project client says "Invalid tool value(s): azure_function" · Issue #39778 · Azure/azure-sdk-for-python. We do not currently add value to these tags.

Me and my team are still tagged for ML code path owners in the same file.

[kashifkhan]

we cant remove the team entirely. We should add granular level access for the folks who are still DRI for their respective projects

@kashifkhan I haven't removed the team entirely. There are still relevant team members in the AI Service label. I have modified the to remove my team members since we are getting incorrectly tagged in AI issues like these AI Project client says "Invalid tool value(s): azure_function" · Issue #39778 · Azure/azure-sdk-for-python. We do not currently add value to these tags.

Me and my team are still tagged for ML code path owners in the same file.

@kingernupur thanks for confirming :) So there are no other granular level changes at the ai project level, iow anything ml will get tagged to your team, anything ai wont ?

[kingernupur]

we cant remove the team entirely. We should add granular level access for the folks who are still DRI for their respective projects

@kashifkhan I haven't removed the team entirely. There are still relevant team members in the AI Service label. I have modified the to remove my team members since we are getting incorrectly tagged in AI issues like these AI Project client says "Invalid tool value(s): azure_function" · Issue #39778 · Azure/azure-sdk-for-python. We do not currently add value to these tags.
Me and my team are still tagged for ML code path owners in the same file.

@kingernupur thanks for confirming :) So there are no other granular level changes at the ai project level, iow anything ml will get tagged to your team, anything ai wont ?

That's right. If and when my team starts contributing to anything under AI in this repo, I will tag my team again to more granular labels :)