Become a RTK Maintainer ! Updated

[aeppling]

Hello RTK community !

RTK is growing fast, with more contributors, PRs, and ideas than ever. To keep things moving smoothly, we’re looking for new maintainers.

We’ve already made an announcement about this. Since then, we’ve refined how we want to bring in new maintainers, and we’re now ready to start discussions with you to recruit our first Ecosystem Maintainers.

We’ve introduced two types of maintainers to progressively build a clean process and strong collaboration between contributors. For now, we’re starting by recruiting Ecosystem Maintainers only. As the project evolves, we’ll soon begin accepting Core Maintainers as well.

To learn how to apply and let us know you’re interested in becoming a maintainer, check this document:
Apply to become a Maintainer

🔧 Core Maintainers

Core Maintainers are responsible for the core of RTK

They have a broader scope and higher responsibilities and permissions, including:

• Maintaining core functionalities and architecture
• Reviewing and merging PRs for release with core team
• Defining project direction and standards with core team
• Ensuring consistency across the entire project
• Refactoring for optimization, standardization & conformity

🌱 Ecosystem Maintainers

Ecosystem Maintainers are responsible for specific environments inside the cmds/ folder (e.g. git, system, etc.).
They own and manage their ecosystem end-to-end:

• Responsible for the quality of filters
• Review and ensure quality of contributions
• Maintain consistency with the rest of the RTK ecosystem
• Help shape and grow their specific domain
• Handle issues and PRs related to their environment (still need security and quality review from core maintainers for release)

If you’ve been contributing and want to get more involved, we’d love to hear from you !