---
References:
- [Governance Github Repo](https://github.com/tauri-apps/governance-and-guidance/blob/main/governance-model/Domains.md)
- [Governance Model](https://hackmd.io/@Beanow/BJC5NXidj/%2FhG-Vp9XKRNCcpQESHz_Liw)
- [Tauri Governance](https://tauri.app/about/governance)
- [Alumni Status]([https://hackmd.io/@jacobbolda/SkRuFYap3](https://hackmd.io/@jacobbolda/SkRuFYap3))
- [Astro Governance](https://github.com/withastro/.github/blob/main/GOVERNANCE.md)
- [Statutes of Tauri](https://dracc.commonsconservancy.org/0035/#governance)
---

## Governance

This document outlines the governance model for Tauri, including detailed descriptions of roles, processes, and voting procedures.

## Project Hierarchy

### Tauri Board

The **Tauri Board** is the central decision maker, dedicated to advising and providing resources to the community. It is comprised of a minimum of 3 and a maximum of 7 board members and is represented by a chairperson that is elected by the other board members.

### Domains

**Domains** are the core pillars within Tauri, functioning as organizational units. Each domain emphasizes the trajectory of the work and the projects undertaken. There is at least one domain lead for Tauri's for domains: community, development, operations, and security.

**Domain Leads** are responsible for the strategic elements of their domain, including its success or failure (defined through KPIs).

### Activities

Whereas domains define the broader areas of interest, **Activities** dive deeper into the specific tasks and projects under each domain. They are a managerial convenience, organizing issues, PRs, and administrative tasks under a single Github issue tracked at the repo and project board level.

Every activity is a mini-project with challenges, timelines, and deliverables. New activities should start in the `Discussion` section on GitHub before being green-lit by a Domain Lead. Here, the community can propose and vote on new features and initiatives.

**Team Leads** are responsible for the day-to-day execution of activities.

###### Tauri's Core Domains

1. **[Community](https://hackmd.io/KVne3y9lT5O3Jm7nXO5awQ):** Looks after both the public face of Tauri and the resources the broader community relies on.
2. **[Development](https://hackmd.io/JYemU4b7SYGfL4l2tAnXxQ):** Drives the innovation behind Tauri. Handles the design, creation, and refinement of Tauri's tools, platforms, and systems.
3. **[Operations](https://hackmd.io/zPSy1ACWQzWYY3MVMtCODw):** Provides resources and support to the organization and its domain.

## Contributor Levels

Tauri thrives thanks to its community. From code improvements to sharing Tauri on social media, every contribution is vital. We've introduced the **Working Group** to recognize and reward those contributions.

The Working Group is categorized into **five levels**, each with its unique privileges and responsibilities.

### Level 1 - Contributor

Anyone who has actively contributed to Tauri's success, regardless of the scale, is recognized at this level.

###### Examples of recognized contributions

- **GitHub:** Merged pull requests, detailed bug report, or RFC.
- **Community:** Answering questions and assisting the community on GitHub, Discord, Stack Overflow, etc.
- **Content Creation:** Blog posts, videos, podcasts, or livestreams about Tauri.

###### Privileges

- Discord role: `@contributor`
- Discord name color: `light blue`
- Access to contributor-exclusive events
- Access to `#working-group` channel on Discord

###### Responsibilities

- No additional responsibilities or time commitments.

### Level 2 - Maintainer

Dedicated contributors involved in the prolonged maintenance and betterment of Tauri.

###### Criteria for Recognition

- Demonstrated sustained commitment over a significant period (a few months).
- Not based on quantity but consistent quality contributions.

###### Privileges

- Inherits all privileges from the Contributor level.
- Discord role: `@maintainer`
- Discord name color: `blue`
- Member of the `tauri` organization on Github
- Direct branch push access
- Ability to review and merge certain GitHub PRs
- Ability to take on the additional role of `@mod`

###### Responsibilities

- Uphold Tauri's community values.
- Active engagement on Discord, especially in the `#support` channel.
- Triaging issues.
- PR reviews and merges.

### Level 3 - Team Lead

Members with significant influence over Tauri's trajectory, overseeing key domain activities.

###### Criteria for Recognition

- Nominated by a Domain Lead.

###### Privileges

- Inherits all privileges from the Maintainer level
- Discord role: `@team-lead`
- Discord name color: `yellow`
- Specialized code access on GitHub

###### Responsibilities

- Lead and own specific domain activities.
- Advocate for Tauri's long-term health and prosperity.

### Level 4 - Domain Lead

Among the most trusted in the Tauri community, these members carry significant authority within their domain, acting as the primary decision-maker.

###### Criteria for Recognition

- Must sign the [Pledge](https://dracc.commonsconservancy.org/0016/)
- Adhere to [Commons Conservancy's Governance Rules](https://dracc.commonsconservancy.org/0035/#governance)

###### Privileges

- Discord role: `@domain-lead`
- Discord name color: **yellow**

###### Responsibilities

- Decision-making within the domain.
- Expertise and deep understanding of the domain's scope.
- Alignment and supervision of domain activities.
- Addressing domain-specific concerns.
- Providing mentorship, especially to team leads within the domain.
- Tracking KPIs related to the domain.

## Specialized Roles

In addition to the Working Group structure, the Board might introduce distinct roles aimed at fulfilling specific strategic directives beyond the allotted scope.

### Moderator

**Moderators** are the guardians of the community, ensuring adherence to Tauri's [Code of Conduct](https://github.com/tauri-apps/tauri/blob/dev/.github/CODE_OF_CONDUCT.md).

###### Privileges

- Discord role: `@mod`
- Discord name color: **red**
- Access to the `#mod` channel on Discord.
- Ability to address `AutoMod` alerts.

### VIP

**VIP** is a special designation for those who contribute to the Tauri ecosystem in a meaningful way. This could involve writing a blog post, streaming, or advocating for Tauri.

###### Criteria for Recognition
- Requires endorsements from at least two Maintainers (L2 or higher).
- Demonstrated results in expanding the presence of the Tauri ecosystem.

###### Privileges

- Discord role: `@vip`
- Discord name color: **light blue**
- Access to the `#vip` channel on Discord.
- Extended support and resources from the Tauri community.

### Board Member

The backbone of Tauri, Board Members dictate the project's overarching decisions, ensuring its sustainability and health.

###### Criteria for Recognition

- Must sign the [Pledge](https://dracc.commonsconservancy.org/0016/)
- Adhere to [Commons Conservancy's Governance Rules](https://dracc.commonsconservancy.org/0035/#governance)

###### Privileges

- Discord role: `@board`
- Discord name color: **yellow**

###### Responsibilities

- Serve for a 2 year term.
- Introducing new domains and roles.
- Structuring and refining the project's processes.
- Upholding the Statutes and Regulations as defined by the [Commons Conservancy](https://dracc.commonsconservancy.org/0035/#governance)

### Chairperson

The **Chairperson** represents the Tauri Board and, therefore, the project.

###### Criteria for Recognition

- Is an existing member of the board.
- Needs to be voted in by the other sitting board members.

###### Privileges

- Veto authority for board decisions.

### Alumni

**Alumni** are revered members, previously active Maintainers (L2 and above) who have shifted their focus away from Tauri but remain part of its history.

###### Privileges

- Discord role: `@alumni`
- Discord name color: **light blue**
- Access to the `#alumni` channel on Discord.
- Retained recognition within the governance repository.

## Role Transition: Becoming an Alumni

Contributor roles are granted for as long as the person wishes to engage with the project. However, over time an active community member may choose to step away from Tauri to work on other things. A member's circumstances can and will change, and we want to help prevent any feelings of guilt in the event one can no longer contribute.

The **Alumni** role is an acknowledgment for those previously in contributor roles but who are no longer involved. On assuming Alumni status, members exchange their previous roles, with its privileges and duties, for the Alumni role and its benefits.

For the community's security, Alumnus access to code and administrative functions are revoked. However, if the circumstances change, we welcome Alumni back, to resume their role as a member of the Working Group.

Rejoining the project as a contributor (L1 or above) will automatically revoke your Alumni status.

## Voting Procedure

Certain project decisions (like governance changes and membership nominations) require a vote.

#### General Voting Guidelines

- Voting is optional; members can abstain.
- Non-voting members within 3 days are deemed to have abstained.
- Informal votes, such as nominating a new contributor, can take place in the `#voting` channel. These votes only require a simple thumbs up (👍) or thumbs down (👎) to be recorded.
- The Tauri community reserves the right to cast a more formal vote, if needed. In this circumstance, votes should accompany a written proposal that documents the candidate, their qualifications for assuming the position, and any additional resources. Proposals that lack the required documentation can be deemed invalid by Domain Leads or Board Members.

#### Special Considerations

- Any two board members may jointly organize a vote of the Tauri Board on any subject.

### Voting: Chairperson

**Who can vote:** Board Members only
**Type of vote:** Formal (electronic)
**Consensus:** <>
**Tie breaker:** <>
**Process:** <>

### Voting: Board Position

**Who can vote:** Maintainers (L2 or higher)
**Type of vote:** Formal (electronic)
**Consensus:** <>
**Tie breaker:** <>
**Process:** <>

### Voting: Domain Lead (L4)

**Who can vote:** Maintainers (L2 or higher)
**Type of vote:** Formal (electronic)
**Consensus:** <>
**Tie breaker:** <>
**Process:** <>

### Voting: Team Lead (L3)

**Who can vote:** Domain Leads
**Type of vote:** Informal
**Consensus:** <>
**Tie breaker:** <>
**Process:** <>

## Community Feedback

Feedback is vital for the success of any project. The Tauri Working Group is committed to addressing every request we receive.

For those interested in the evolution of our features:

- The [[Public Roadmap]] is your go-to for voting on proposed features.
- New feature suggestions are presented as Activities in the Discussion board.
- Once approved by the Domain Lead, these features are prioritized and integrated into the Roadmap.
- Always refer to the Roadmap to monitor open Activities, provide your insights, and keep track of unresolved issues. It's your central hub for staying involved and informed.

Always refer to the Roadmap to monitor open Activities, provide your insights, and keep track of unresolved issues. It's your central hub for staying involved and informed.