chore: remove smoya from TSC

[smoya]

Hi AsyncAPI community,

I’ve decided to step down from the AsyncAPI Technical Steering Committee and resign as a maintainer from all the repositories I currently own.

These are the repositories I’ll be stepping away from progressively:

• spec
• spec-json-schemas
• parser-go
• parser-js
• converter-go
• bindings
• raml-dt-schema-parser
• openapi-schema-parser
• avro-schema-parser
• go-watermill-template
• template-for-go-projects
• parser-api
• server-api

This has been a tough decision. I’ve done my best to keep up, but the truth is I no longer have the time needed to do a solid job as a maintainer. Rather than stay in a role I can’t give my full attention to, I prefer to make space for others who can bring the energy and care these projects deserve.

I’m really proud of everything we’ve done together. I’ll always treasure the time I spent working on AsyncAPI, and I’m deeply grateful for the community—it’s one of the best I’ve ever been part of. I carry all of you with me moving forward.

If you’re interested in helping maintain any of these repositories, please let me know. I’d love to see someone take over and continue the work, and I’m happy to help with the transition however I can.

I’ll also be posting this in the AsyncAPI Slack. Thanks for everything, and see you around. 💛

Summary by CodeRabbit

• Chores
  • Updated the emeritus TSC members list to include a new entry.
  • Adjusted maintainer status for Sergio Moya.

[coderabbitai]

Walkthrough

This change updates project governance records by adding "smoya" to the emeritus TSC members list in Emeritus.yaml and setting the isTscMember field to false for "Sergio Moya" in MAINTAINERS.yaml. No other fields or structures are modified.

Changes

File(s)	Change Summary
Emeritus.yaml	Added "smoya" to the list of emeritus TSC members.
MAINTAINERS.yaml	Updated "Sergio Moya" by setting isTscMember from true to false.

Possibly related PRs

• chore: remove cameron rushton from the tsc members list #1856: Updates TSC membership status and emeritus list, similar to the changes in this PR.

Suggested labels

ready-to-merge

Suggested reviewers

• derberg
• thulieblack

Poem

A hop and a skip, a YAML tweak,
Emeritus lists for those we seek.
Sergio steps to a new role,
As records change, we reach our goal.
With every field and every name,
The project’s history stays aflame! 🐇

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e902daf and 8c3a10f.

📒 Files selected for processing (2)

• Emeritus.yaml (1 hunks)
• MAINTAINERS.yaml (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Validating the list of maintainers

MAINTAINERS.yaml

[error] 1-1: Validation of maintainers file failed against schema.json. See validator.errors for details.

🔇 Additional comments (2)

Emeritus.yaml (1)

29-29: New emeritus TSC entry looks good.

The addition of - smoya under emeritus_tsc is correctly indented and reflects the update in MAINTAINERS.yaml. No further changes needed here.

MAINTAINERS.yaml (1)

348-354: Reflect removal from TSC accurately.

Changing isTscMember from true to false for Sergio Moya correctly updates his Technical Steering Committee status.

---

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

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

[thulieblack]

😥

[asyncapi-bot]

@smoya We would like to express our gratitude for your contributions as a member of the Technical Steering Committee at the 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!