# Descriptions for Domain Leads

> In order to efficiently fulfill its tasks, the Board may establish specialized committees and taskforces, as well as assign named roles to qualified individuals to provide advice and assistance on specific issues. The associated qualifications, tasks and responsibilities SHALL be formalised by publication as part of the Regulations of Tauri.

https://dracc.commonsconservancy.org/0035/#governance

Examples:
- https://dracc.commonsconservancy.org/0030/
- https://dracc.commonsconservancy.org/0032/

Both predate Tauri (I mean, you should all know the number 35 by heart right?) And I'm not a fan of the specifics of the roles they set up, like the Chair must ensure meeting minutes, imo the Chair should minimize meetings and prefer async :joy:

But there's interesting tidbits, like how fiduciary responsibility is given to the other roles, without reducing the responsibility of the Board.

---

## Ideas from examples to check:

- [ ] Terms & elections for these lead roles?
- [ ] Give Leads voting rights (such as for Board elections?)
- [x] How to resign from a role.
- [x] "The Tauri Board MAY delegate the right to handle certain decisions to an individual officer, committee or taskforce, this does not reduce the responsibility of the Tauri Board.
The individuals fulfilling the roles defined in this Regulation act as fiduciaries with regard to the Tauri Programme, and their duties include, but are not limited to, the fiduciary duty of care and the fiduciary duty of loyalty." (needs a terminology sweep)
- [ ] ~~Hard limit on 2-3 size?~~
- [ ] ~~Non-remunerate positions only~~ (in other words, exclusively volunteers, unpaid)

## Thoughts on voting & terms


We do keep flexibility (middle blue post-it). But in addition the elections may offer a good opportunity to ensure the seats are fairly accessible. Like a point in time re-evaluation

Would suggest having Lead elections as an idea for later improvement.
Mainly because it makes the necessary regulation changes *even bigger* and harder to review.

----

Formal proposal language from here:

## Directors

_Unchanged from statutes._

## Chair

_Unchanged from statutes._

## Domains

Domains are specific areas of interest within the Tauri Programme.
The Tauri Board may define or change these Domains with a simple majority vote.
Currently they are:
- Governance
- Operations
- Development
- Community

## Domain Leads

For each Domain the Tauri Board SHALL seek to appoint **two or three Domain Leads**.

When there are less than two, for example due to lack of qualified candidates, Board Directors may act as interim-leads. And with a simple majority vote, the Board can allow for more than three Domain Leads.

Individuals may be a Domain Lead for multiple Domains, however in the interest of maintaining a healthy workload and for continuity of the Tauri Programme, it's highly preferred for individuals to be a Domain Lead for one Domain at a time. Likewise, it's preferred for Board Directors acting as interim-leads to vacate this secondary role as soon as two or more qualified Domain Leads are appointed.

The Tauri Board MAY delegate the right to handle certain decisions to Domain Leads, this does not reduce the responsibility of the Tauri Board. Domain Leads act as fiduciaries with regard to the Tauri Programme, and their duties include, but are not limited to, the fiduciary duty of care and the fiduciary duty of loyalty.

- The Tauri Board is responsible for keeping on file, a [signed Pledge](https://dracc.commonsconservancy.org/0016/) before appointing Domain Leads.

#### Common to all:
Domain Leads may directly implement changes within their respective Domains. When faced with highly controversial decisions they SHALL defer to a Board decision. Any Domain Lead decision may be overruled by the Tauri Board.

In order to assist with tasks in their Domain, Domain Leads may create Teams, appoint or remove Team members and decide how those Teams should function. Team members should generally not be required to act as fiduciaries or sign the Pledge. Instead the Domain Leads remain responsible, and privileges for Team members should be adjusted accordingly. Although exceptions may be made with approval of the Tauri Board.

- Having time to be actively involved is a qualification for all roles.
(How else would one ensure continuity and fiduciary care in the areas of responsibility?)

## Governance Domain Lead

Qualifications:

Responsibilities & privileges:
- Ensures governance model is transparent and well documented.
- Ensures decision making isn't needlessly kept private.
- May (co-)submit a proposal for the Tauri Board to vote on.
:thinking_face: maybe this should be common to all.

## Operations Domain Lead

Qualifications:
- Has good intuition about when better tools can help, and when their maintenance and opportunity cost may harm.
- Understands that continuity and security are equally important.
- Hates it when GitHub Actions spams their mailbox with failed builds.

Responsibilities & privileges:
- Ensures the tools to be used by contributors are adequate, and operational.
- Looks to ensure tasks can be performed by as many qualified contributors as possible.
Taking risks of the tasks and privileges, and trust of contributors into account.
(For example by modeling after the Governance Model)
- Can make project-wide tooling decisions.
- Can enforce access control / privilege models, in line with these objectives.

## Development Domain Lead

Qualifications:

Responsibilities & privileges:
- Ensures code repository access is sound, uses review practices, has maintainers.
- Can make technical decisions escalated to them.
- Has administrative access to any tools or services required for development, so long as this doesn't interfere with Operations.

## Community Domain Lead

Qualifications:

Responsibilities & privileges:
- Ensures the public messaging and our community follows Code of Conduct, and is welcoming.
- Ensures our community provides the help and resources people need to use our software and tools.
- Can make decisions on what representative messaging looks like.
- Can make moderation decisions.
- Has administrative access to any tools or services required for public messaging or community management, so long as this doesn't interfere with Operations.