The Project Lead is appointed by the Mautic Council.
The most important aspect of the role of the Project Lead is to enable Mautic to succeed, and more specifically to:
and also to:
This includes (but is not limited to) creating and supporting community structures, supporting team leads in organising and managing their teams, and empowering volunteers.
The Project Lead also has primary responsibility for supporting in-person events and meetups, global events like Mauticon, and being a bridge between the community and key stakeholders.
They hold overall responsibility for all the Community channels such as the Forums, Slack, Mautic.org etc. and support the community teams who manage these channels.
The Project Lead owns the community and product strategy. They help teams to understand how they can mobilise resources to execute against the community strategy, and support teams in any matters relating to community management.
The Project Lead also has the ability to appoint and remove volunteers to roles in the community teams. Where the community makes such decisions as outlined in the governance model, the Project Lead reserves a right of veto over a nomination (for important reasons only).
The same applies to strategic decisions - there is a right to veto strategic decisions, but the intention is that this should only be used in exceptional circumstances where it has not been possible to reach a consensus.
Found errors? Think you can improve this documentation? edit this page