---
# System prepended metadata

title: Tauri Org Improvements

---

# Tauri Org Improvements

## Improvement Points

- Somebody to make decisions (or guide the team to a decision)
  - i.e. Do we do 1.4 or do we focus on 2.0? What does beta/RC look like?
  - Right now everyone is doing their own thing (awesome for discovering new things, slows us down for larger projects/milestones)
- Better transparency/structure for status such as audits, PRs, overall release progress, issues
    - Have a decent start with https://github.com/orgs/tauri-apps/projects/11
    - Simon also has an awesome board https://github.com/orgs/tauri-apps/projects/16/views/8
    - Need to involve security team to better capture status
- macOS issues are piling up and need triaged/assigned
- What does it mean to be a WG member?
  - Does is assume a certain level of contribution?
  - What reponsibilities do we expect from a WG member?
- Have tried GH boards to better organise a few times but without someone to really manage and advocate for the board it goes unused
- There's a backlog of non-code tasks and admin work that needs to be done
  - Book, keeping up with sponsorships, will defer to the board for more
- Track across repos (tauri-docs, RFCs, plugin repo, etc.)
- Maybe move to a normal release schedule (i.e. sprint-based approach)
- It's been hard to get everyone on the same page at a high-level of what's happening/coming up (i.e. _what's the status/scope of 2.0?_)