ThorVG Role & Responsibility Guidance

[hermet]

Dear ThorVG contributors and collaborator

We’re excited to announce the introduction of an official role structure for the ThorVG project!

As the project grows and more contributors join the community, we believe it’s essential to define clear responsibilities and expectations across different levels of involvement. This structure will help us maintain code quality, improve collaboration, and support long-term sustainability of the project.

🧭 What’s New?

We’ve formally introduced the following roles:

• Project Lead: Sets the overall vision and makes final decisions
• Maintainer: Senior technical leader with strategic and governance responsibilities
• Core Contributor: Active module owner with write access, Codebase gatekeeper, reviewer, and technical leader
• Contributor: Anyone who contributes code, documentation, or ideas

Each role has a clearly defined set of responsibilities, decision-making boundaries, and contribution expectations.

You can read the full role definitions here: Roles & Responsibilities

💡 Why This Matters

This role structure is not about hierarchy — it's about clarity, trust, and collaboration. It ensures contributors know how to grow, who to reach out to, and how decisions are made. It also helps us recognize and empower those who are actively maintaining and improving the project.

If you’ve been contributing actively and are interested in taking on a more formal role, feel free to reach out to the maintainers or the project lead directly.

Let’s keep building a strong, transparent, and welcoming open-source community together.

Thank you for being part of ThorVG.

Regards Hermet.