chore: introduce new maintainers setup

Author: derberg

CONTRIBUTING.md

@@ -1,11 +1,34 @@
 # Contributing to AsyncAPI
+
 We love your input! We want to make contributing to this project as easy and transparent as possible.
 
-## Contribution recognition
+## Table of Contents
+
+- [Contribution Recognition](#contribution-recognition)
+- [Guidelines for New Contributors](#guidelines-for-new-contributors)
+- [Few Tips for Effective Contributions](#few-tips-for-effective-contributions)
+- [Summary of the Contribution Flow](#summary-of-the-contribution-flow)
+- [Code of Conduct](#code-of-conduct)
+- [Our Development Process](#our-development-process)
+- [Issues](#issues)
+- [Bug Reports and Feature Requests](#bug-reports-and-feature-requests)
+- [Pull Requests](#pull-requests)
+- [Conventional Commits](#conventional-commits)
+- [Maintainer Roles](#maintainer-roles)
+  - [Triager](#triager)
+  - [Committer](#committer)
+  - [Champion](#champion)
+  - [Maintainer Role Matrix](#maintainer-role-matrix)
+- [License](#license)
+- [References](#references)
+
+---
+
+## Contribution Recognition
 
 We use [All Contributors](https://allcontributors.org/docs/en/specification) specification to handle recognitions. For more details read [this](https://github.com/asyncapi/community/blob/master/recognize-contributors.md) document.
 
-## Guidelines for new contributors 
+## Guidelines for New Contributors
 
 1. Read the [generator docs](https://www.asyncapi.com/docs/tools/generator) to get an overview of what the project is about.
 2. While reading through the docs one might identify issues (e.g., broken links, text formatting issues, etc.).
@@ -16,7 +39,7 @@ We use [All Contributors](https://allcontributors.org/docs/en/specification) spe
 7. Instead of creating entirely new tests, consider enhancing existing ones by adding more edge cases to include additional test scenarios.
 8. We encourage contributors to help improve code quality by reviewing reported issues on [SonarCloud](https://sonarcloud.io/project/issues?issueStatuses=OPEN%2CCONFIRMED&id=asyncapi_generator) and suggesting improvements, identifying false reported issues that may need to be removed, and proposing fixes for valid issues.
 
-## Few tips for effective contributions
+## Few Tips for Effective Contributions
 
 1. **Join the AsyncAPI Slack Workspace** - Connect with maintainers and fellow contributors in the `#generator` channel on [AsyncAPI Slack](https://www.asyncapi.com/slack-invite) to ask questions, share ideas, and get help.  Also, consider attending the **weekly Knowledge Sharing meetings held every Wednesday**; details are shared in the channel.
 2. Understanding how the Generator works is key to making valuable contributions. You can start by actively following along and executing the steps given in the [generator template tutorial](https://www.asyncapi.com/docs/tools/generator/generator-template). Hands-on practice will provide you with a comprehensive understanding of how the Generator processes templates and allow you to experiment with customization.
@@ -28,7 +51,7 @@ We use [All Contributors](https://allcontributors.org/docs/en/specification) spe
 8. Collaborate with Other Contributors – If someone else has already raised an issue and you are interested in contributing to it, please communicate with them and collaborate instead of raising a separate PR independently. Working together leads to better contributions and avoids duplication of efforts. Open source is driven by **collaboration, not competition**.
 9. **Respond to Maintainer Reviews Promptly** - If a maintainer requests changes or provides feedback on your PR, please try to address them within **7 days**. If you’re unable to respond by then, the PR may be closed. Contributors are always welcome to open a new PR once they’re ready to continue.
 
-## Summary of the contribution flow
+## Summary of the Contribution Flow
 
 The following is a summary of the ideal contribution flow. Please, note that Pull Requests can also be rejected by the maintainers when appropriate.
 
@@ -59,13 +82,17 @@ The following is a summary of the ideal contribution flow. Please, note that Pul
     └───────────────────────┘
 ```
 
+
 ## Code of Conduct
+
 AsyncAPI has adopted a Code of Conduct that we expect project participants to adhere to. Please [read the full text](./CODE_OF_CONDUCT.md) so that you can understand what sort of behaviour is expected.
 
 ## Our Development Process
+
 We use Github to host code, to track issues and feature requests, as well as accept pull requests.
 
 ## Issues
+
 [Open an issue](https://github.com/asyncapi/asyncapi/issues/new) **only** if you want to report a bug or a feature. Don't open issues for questions or support, instead join our [Slack workspace](https://www.asyncapi.com/slack-invite) and ask there. Don't forget to follow our [Slack Etiquette](https://github.com/asyncapi/community/blob/master/slack-etiquette.md) while interacting with community members! It's more likely you'll get help, and much faster!
 
 ## Bug Reports and Feature Requests
@@ -76,7 +103,7 @@ Please use our issues templates that provide you with hints on what information
 
 **Please, make sure you open an issue before starting with a Pull Request, unless it's a typo or a really obvious error.** Pull requests are the best way to propose changes to the specification. Get familiar with our document that explains [Git workflow](https://github.com/asyncapi/community/blob/master/git-workflow.md) used in our repositories.
 
-## Conventional commits
+## Conventional Commits
 
 Our repositories follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification. Releasing to GitHub and NPM is done with the support of [semantic-release](https://semantic-release.gitbook.io/semantic-release/).
 
@@ -93,10 +120,91 @@ What about MAJOR release? just add `!` to the prefix, like `fix!: ` or `refactor
 
 Prefix that follows specification is not enough though. Remember that the title must be clear and descriptive with usage of [imperative mood](https://chris.beams.io/posts/git-commit/#imperative).
 
-Happy contributing :heart:
+## Maintainer Roles
+
+To help scale maintenance of the monorepo, we define three key roles: **Triager**, **Committer**, and **Champion**.
+
+### Triager
+
+Triagers help manage issues and pull requests (PRs) across the entire project.
+
+**Types:**
+- `Code`: A code triager is responsible for triaging code-related topics.
+- `Docs`: A docs triager is responsible for triaging documentation-related topics.
+
+One person can be both a code and docs triager. However, this is not required, as `generator` is a large project with extensive documentation that benefits from having people focused solely on docs.
+
+**Responsibilities:**
+- Label issues and PRs
+- Close or reopen issues
+- Provide feedback and reviews
+- Ensure contributor guidelines are followed
+- Ensure PRs are of high quality and fullfil all the requirements
+
+**Scope:**
+- Applies to the entire monorepo (not scoped to specific templates)
+
+**Notes:**
+- Triagers **cannot** merge pull requests.
+- Being active and consistent as a triager is the first step toward becoming a committer.
+- Even though triagers cannot merge PRs and their approvals do not enable a PR to be merged, it is encouraged that triagers review and approve PRs using GitHub's functionality to indicate that the PR is accepted at the triage level.
+
+
+### Committer
+
+Committers are maintainers who can approve and merge PRs.
+
+**Responsibilities:**
+- Review and merge PRs
+- Guide contributors
+- Maintain high code/documentation standards
+
+**Scope:**
+- Some committers have access to the full monorepo (`core maintainers`)
+- Others may have scoped access to specific area, like for example templates (`template champions`)
+
+**Notes:**
+- Committers play a vital role in onboarding and mentoring other contributors and triagers.
+
+### Champion
+
+Champions are committers who **own a specific area** of the codebase (e.g., a template, documentation, website). In other words, champions have write access to the repository, but through proper configuration in the `CODEOWNERS` file, their approval counts only for specific areas of the repository.
+
+**Types of Champions:**
+- **Template Champion** – Responsible for specific template(s) (e.g., Go, Markdown, Java, etc.).
+- **Docs Champion** – Focuses on improving and maintaining generator's documentation.
+
+**Becoming a Champion:**
+- Regular, meaningful contributions in a focused area
+- Active reviews, examples, tests, and documentation
+- No limit to how many champions per area
+
+**Notes:**
+- Champions can merge PRs in their area of ownership.
+- All champions are considered committers for their respective areas.
+
+---
+
+### Maintainer Role Matrix
+
+| Responsibility        | Triager | Committer (Champion) | Committer (Core Maintainer) |
+|-----------------------|:-------:|:----------------:|:-----------------------------:|
+| Label issues/PRs      | ✅ | ✅ | ✅ | 
+| Close/reopen issues   | ✅ | ✅ | ✅ | 
+| Review PRs            | ✅ | ✅ | ✅ |
+| Approve PRs           | ❌ | ✅ (within scope) | ✅ |
+| Merge PRs             | ❌ | ✅ (within scope) | ✅ | 
+| Modify repository settings | ❌ | ❌ | ✅ |
+---
 
 ## License
-When you submit changes, your submissions are understood to be under the same [Apache 2.0 License](https://github.com/asyncapi/asyncapi/blob/master/LICENSE) that covers the project. Feel free to [contact the maintainers](https://www.asyncapi.com/slack-invite) if that's a concern.
+
+By contributing, you agree that your submissions are under the [Apache 2.0 License](https://github.com/asyncapi/asyncapi/blob/master/LICENSE). Contact maintainers if this is a concern.
 
 ## References
-This document was adapted from the open-source contribution guidelines for [Facebook's Draft](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md).
+
+This document was adapted from:
+
+- [Facebook’s Draft Contributor Guide](https://github.com/facebook/draft-js/blob/master/CONTRIBUTING.md)
+- [Modelina Champion Guidelines](https://github.com/asyncapi/modelina)
+- [Website Triager/Committer Guidelines](https://github.com/asyncapi/website/blob/master/CONTRIBUTING.md#maintainers-setup)