docs(maintainers): update MAINTAINERS.yaml file with the latest CODEOWNERS changes

[asyncapi-bot]

Description

• Update MAINTAINERS.yaml based on CODEOWNERS files across all repositories in the organization.

For details on why a maintainer was removed or changed, refer to the Job summary page.

Summary by CodeRabbit

• Chores
  • Updated maintainer roster: removed one maintainer entry and added a new maintainer to the project team
  • Updated repository assignments for an existing maintainer

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The MAINTAINERS.yaml file was updated to reflect team changes: removed Ashmit Jagtap as a maintainer, removed the conference-website repository from HariKrishnan's assignment, and added TenzDelek as a new maintainer.

Changes

Cohort / File(s)	Summary
Maintainers List Update MAINTAINERS.yaml	Removed Ashmit Jagtap's complete entry, removed conference-website from HariKrishnan's repos, and added TenzDelek as new maintainer with TSC membership.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• bandantonio
• derberg
• thulieblack
• asyncapi-bot-eve

Poem

🐰 The roster hops along with care,
Some faces gone, some names are there,
TenzDelek bounds into the fold,
While grateful thanks for Ashmit are told,
The team evolves, as all teams must—
With open hearts and growing trust! ✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bot/update-maintainers-21920379078

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[asyncapi-bot]

Repositories (conference-website) have been removed from Vishvamsinh Vaghela's repository list in MAINTAINERS.yaml. Only asyncapi-bot can make such changes. This information is derived from the CODEOWNERS file located in any repository under AsyncAPI GitHub organization.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[asyncapi-bot]

@TenzDelek We invited you to join the AsyncAPI organization, and you are added to the team that lists all Maintainers.

Please take a moment to verify if you would like to provide more details for your account, such as your LinkedIn profile, Twitter handle, or company affiliation. In case there is anything you want to add, please open up a separate pull request for the MAINTAINERS.yaml file.

Additionally, if you are interested in becoming a TSC member and contributing to the direction of the AsyncAPI Initiative, let us know, and we'll be happy to guide you through the process. Every maintainer has the right to become a TSC member, just open a pull request to modify your entry in MAINTAINER.yaml file and make sure isTscMember property is set to true. Consider also adding slack information with your Slack Member ID. We use it in our automation to drop you reminders to participate in voting. To find your Member ID, click on your profile photo in Slack and click "Profile". In the right side of their profile section, click on the three dots and click "Copy Member ID".

You can find some basic information about TSC membership in this TSC-related guide. Feel free to reach out to us for more help by dropping a comment in this pull request, or by asking for help in our Slack.

Welcome aboard! We are excited to have you as part of the team.

[asyncapi-bot]

@ashmit-coder We would like to express our gratitude for your contributions as a maintainer of AsyncAPI Initiative. Your efforts have been immensely valuable to us, and we truly appreciate your dedication. Thank you once again, and we wish you all the best in your future endeavors!