Divide "Maintainer" role into two categories: Triager and Committer

[quetzalliwrites]

Currently, each AsyncAPI repository has a single level of maintainers, each responsible for various project parts. Their duties range from issue triage to PR (Pull Request) approval and merging.

We propose introducing two distinct levels of maintainers to manage an increasing workload and divide responsibilities more clearly. Originally proposed and implemented in our /website repository, we found this change to maintainer roles has expedited work on the website project while facilitating the onboarding of new maintainers.

NOTE: Even though AsyncAPI first implemented this concept in the /website project, this approach has already been implemented in other OSS communities such as Django, React, Kubernetes, and Node.js.

🗳️ Divide "Maintainer" role into two categories: Triager and Committer

• Triager: Inspired by the Node.js community, triagers assess newly opened issues and pull requests. Assigned the "Triage" role on GitHub, they are responsible for labeling issues and pull requests, commenting on, closing, and reopening them, and assisting users and novice contributors. Triagers aspiring to become committers should collaborate with existing committers to gradually acquire more rights, such as approving and merging simple bug fixes.

• Committer: Committers are tasked with approving pull requests and maintaining the project. They receive the "Maintainer" role on GitHub and are responsible for the technical direction of the website, reviewing and approving pull requests, and onboarding new committers and triagers.

Both committers and triagers are included in the CODEOWNER file. We would maintain the existing division of duties based on specific topics. As such, triagers may focus exclusively on code-related or documentation-related issues and pull requests.

[Amzani]

I love this idea @alequetzalli

[Amzani]

How and who will be managing permissions? triager/committer

(As a current maintainer - I don't have admin access).

cc @alequetzalli @derberg @fmvilas

[quetzalliwrites]

@Amzani As for managing permissions, I would assume only the higher level of commiters, but unsure of who exactly has those permissions. 🤔 Perhaps the others know more.

• committers will be granted write permissions.
• triagers will only be granted read permissions.

[Amzani]

@alequetzalli @derberg
I didn't see any description of higher level of commiters, for me it's still unclear how these permissions will be managed.
For example, I'm a studio maintainer but unable to manage this kind of permission as I mentioned.

[quetzalliwrites]

Honestly, I have the same question as you! 😁 (FYI, higher level of committers is just a phrase I wrote myself, it's not an actual term we've using.. feel free to ignore my phrasing if I confused you heh)

I do not know who has the repo settings permission access, I genuinely would like the answer to that question myself.

@fmvilas @magicmatatjahu @derberg Can one of your folks please clarify who has these permission settings in this repo and who/why is awarded that admin access?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️