docs(community): update latest maintainers list

[asyncapi-bot]

Updated Maintainers list is available and this PR introduces changes with latest information about Maintainers

Summary by CodeRabbit

• New Features

  • Added new contributors, Azeez Elegbede, Vinit Shahdeo, and Anubhav Vats, enhancing the community involvement.

• Updates

  • Updated existing contributor information to reflect current status and repository associations.

[coderabbitai]

Walkthrough

The changes involve modifications to the config/MAINTAINERS.json file, focusing on the addition and removal of contributors along with updates to their associated metadata. New contributors Azeez Elegbede, Vinit Shahdeo, and Anubhav Vats were added, while Lukasz Gornicki's repository list was updated to remove "asyncapi-react." These updates ensure the contributor list reflects current involvement and availability.

Changes

File	Change Summary
config/MAINTAINERS.json	- Added contributors: Azeez Elegbede (repos: asyncapi-react, conference-website, chatbot), Vinit Shahdeo (repo: diff), Anubhav Vats (repo: diff) - Updated Lukasz Gornicki's repositories, removing asyncapi-react.

Possibly related PRs

• docs(community): update latest maintainers list #3273: This PR also updates the config/MAINTAINERS.json file, including the addition of the contributor Anubhav Vats, which directly relates to the changes made in the main PR.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• derberg
• magicmatatjahu
• akshatnema
• sambhavgupta0705
• anshgoyalevil

🐰 In the garden where bunnies play,
New friends join us, hip-hip-hooray!
Azeez, Vinit, and Anubhav too,
With skills and talents, oh so true!
Let's hop along, our team is bright,
Together we’ll code, from morning to night! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	2f14613
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/670b9b97f453b100092da730
😎 Deploy Preview	https://deploy-preview-3291--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

config/MAINTAINERS.json (2)

Line range hint 1012-1021: LGTM with a suggestion: Consider adding missing fields for consistency.

The addition of Vinit Shahdeo as a maintainer is generally correct. However, for consistency with other entries, consider adding the following fields if available:

• linkedin
• slack
• company

This will ensure all maintainer entries have a uniform structure.

---

Line range hint 1022-1031: LGTM with issues to address: Incorrect twitter handle and missing fields.

The addition of Anubhav Vats as a maintainer is generally correct, but there are two issues to address:

1. The twitter handle is set to "postmanlabs", which seems incorrect for an individual maintainer. Please verify and update with Anubhav's personal twitter handle if available.

2. For consistency with other entries, consider adding the following fields if available:

   • linkedin
   • slack
   • company

These changes will ensure accuracy and maintain a uniform structure across all maintainer entries.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a46f870 and 2f14613.

📒 Files selected for processing (1)

• config/MAINTAINERS.json (1 hunks)

🧰 Additional context used

🔇 Additional comments (2)

config/MAINTAINERS.json (2)

Line range hint 323-334: LGTM: New maintainer added correctly.

The addition of Azeez Elegbede as a maintainer is well-structured and contains all the necessary information. The entry follows the established format and includes the appropriate repositories.

---

Line range hint 261-286: Confirmed: "asyncapi-react" removed from Lukasz Gornicki's repos.

The removal of the "asyncapi-react" repository from Lukasz Gornicki's list of repos has been correctly implemented as mentioned in the AI summary.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	46
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-3291--asyncapi-website.netlify.app/