---
# System prepended metadata

title: Meeting checklist

---

# Meeting checklist

- [ ] 1. Sanity checks
    - [ ] Any missing agenda items
    - [ ] Separation between regulated & *just documentation*
    - [ ] Is available time a requirement (for Domain Lead / Director)?
- [ ] 2. Gather necessary outcomes
    - [ ] Regulatory docs
    - [ ] Things to vote on
    - [ ] Things to document
    - [ ] Any feedback rounds for WG
- [ ] 3. 


## 1. Sanity

- Time requirement: definitely more on Domain Lead.
- Expectation from the board: check in with Domain Lead, for health (see appointing season)
- Allow resigning.
- Path to becoming a Domain Lead,
    - From WG: Nominations and Complaints.
    - Have appointing seasons, (Spring / Autumn appointing). Though not locked in regulation.

## 2. Outcomes

- Vote & regulation change.
- Explainer of model itself -> why we're doing this.
- Expectations doc for WG internally.
- Later discussion about how to track domain leads, who to talk to, etc.
- Separate point: how do I interact with the Board?

## Some references

Quoting [Governance model v1.0 (permanent beta)](https://hackmd.io/@Beanow/BJC5NXidj/%2FhG-Vp9XKRNCcpQESHz_Liw)

> ## Transitioning
>
>The main priority for transitioning should be **continuity**.
>
>- [ ] Phase 0: Mapping out current situation and desired domains
>- [ ] Phase 1a: [Formalizing Domain Lead roles](/dyhez9LuQNyPpvcvmES8SA)
>- [ ] Phase 1b: Appointing people with *current admin access* to corresponding Teams.
>      *This is expected to be very messy, and people will be in many teams. Reflecting reality.*
>- [ ] Phase 2: Appointing Domain Leads. Ensuring they have corresponding access too.
>- [ ] Phase 3: Gradually limit permissions and let people move teams per their interest & expertise.


Also for the roles:

> The associated qualifications, tasks and responsibilities SHALL be formalised by publication **as part of the Regulations of Tauri.**