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

• Chores
  • Updated maintainers list with a new contributor
  • Added repository access for an existing contributor to the "community" repository

[coderabbitai]

Walkthrough

The pull request modifies the config/MAINTAINERS.json file by adding a new contributor named "Moderator" with the GitHub username "AayushSaini101" and updating the repository list for an existing contributor "Quetzalli Writes". The changes involve adding a new entry with specific attributes and expanding the repository list for an existing maintainer.

Changes

File	Change Summary
config/MAINTAINERS.json	- Added new contributor "Moderator" (AayushSaini101) with repos ["cli"] - Updated "Quetzalli Writes" repos from ["website"] to ["website", "community"]

Suggested Reviewers

• quetzalliwrites
• asyncapi-bot-eve

Poem

🐰 A maintainer joins the clan,
With CLI in their master plan,
Quetzalli's realm now spans more ground,
New contributors, project-bound!
Code grows stronger, team expands, hooray! 🚀

Finishing Touches

• 📝 Generate Docstrings

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

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	fdb41f6
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/677fa2630c2580000858838a
😎 Deploy Preview	https://deploy-preview-3559--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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4d002ce) to head (fdb41f6).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3559   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           19        19           
  Lines          668       668           
=========================================
  Hits           668       668           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

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

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

config/MAINTAINERS.json (1)

971-972: Remove trailing space in name field.

The name field contains a trailing space which should be removed for consistency.

-        "name": "Moderator ",
+        "name": "Moderator"

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4d002ce and fdb41f6.

📒 Files selected for processing (1)

• config/MAINTAINERS.json (2 hunks)

⏰ Context from checks skipped due to timeout of 180000ms (3)

• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Test NodeJS PR - windows-latest
• GitHub Check: Lighthouse CI

🔇 Additional comments (2)

config/MAINTAINERS.json (2)

471-472: LGTM!

The repository list update for Quetzalli Writes is properly formatted and aligns with the PR objective.

---

971-977: Consider adding optional fields for completeness.

Most maintainer entries include additional fields like linkedin, slack, twitter, and availableForHire. Consider adding these optional fields for consistency with other entries.

Run this script to see the most common fields across maintainers:

✅ Verification successful

Optional fields are indeed commonly used in maintainer profiles

The data confirms that optional fields like availableForHire (71%), slack (68%), linkedin (55%), and twitter (51%) are widely adopted across maintainer entries. Adding these fields would improve consistency with other maintainer profiles and provide valuable contact information.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Analyze the common fields used across maintainer entries
cat config/MAINTAINERS.json | jq -r '.[] | keys | @csv' | tr ',' '\n' | sort | uniq -c | sort -nr

Length of output: 284