Beanow avatar Hallo! I'm Robin van Boven (@Beanow), a software engineer based in the Netherlands. Currently I'm a Tauri Board Director, employed by CrabNebula, and would love to continue for another term as a Board Director. About 2½ years ago I helped with establishing the Tauri Programme and joined as a Board Director. Some of the areas I worked on during this term are: Created processes and templates for the Board, to follow regulations more easily. Made sure we have multiple admins on important services (reducing our bus factor risk). Proposed and co-authored the "Domains and Teams" governance model.

Hello world! After a Board meeting today. There's a few updates to share. The long discussed #"Domains and Teams governance model" ** is currently being voted on**. With the preliminary result it looks like it will pass. We should have an update when the vote closes next week :smile:. If it does pass it makes the regulatory changes to start using the new model, and creates the first four domains. Which segues to the next major topic. On July 16th the non-profit Tauri Programme will be 2 years old. And 5 of 7 Board seats will be up for election. Plus very likely 4 Domains who need Leads! After discussing, we think that for the election all Working Group members should be able to cast a vote on the next term's Board Directors. Realising it's the first time we hold an election on this scale with relatively short notice, mistakes will be made :sweat_smile: but that it's better than an "election" within a small group. To make that possible, we're looking for people who want to help with the organisation of this election. It would involve several publications, looking for candidates, explaining the roles of Board Director and Domain Leads, presenting candidates, closing out the last term, sharing the result... but also how votes should be cast. (Voting systems are harder than you'd expect.)

README Governance model overview Board proposal draft New Regulation Expectations First Domains Domain: Development Archive / reference About Director + Domain Lead

Domain: Development The main activity for Tauri. Developing and maintaining the Tauri software. Some keywords to describe the area of interest: Code maintainers - Package releases - Codebase Security R&D - API documentation - Bug triaging An effective Development Domain results in: High value software for Tauri users.

:warning: This is a DRAFT. See GitHub for the exact version being voted on. name: Proposal about: Template to create a proposal & formal vote labels: 'type: proposal, status: drafting' Status [x] Drafting [ ] Voting [ ] Concluded

:warning: This is a DRAFT. See GitHub for the exact version being voted on. Title: Domains, Domain Leads and Teams within Tauri DRACC: 00XX, TAUR-000X Category: Regulatory Scope: Programme Authors: van Boven, R. Date: TBD This document is copyright: The Commons Conservancy and Tauri. It can be used under a Creative Commons Attribution 4.0 International license.

Not every aspect of the new governance model needs to be turned into regulation for the Tauri Programme, so there is a split into several documents. A holistic explanation of the model. Governance model overview Aimed at WG members interested in the governance model. A draft of the formal Board proposal. The regulations being proposed. Essentially an "attachment" for the formal Board proposal. An "expectations" document. This is a document that keeps track of important assumptions or expectations which are not part of the regulation changes, but need to be communicated elsewhere.

Previously called "Governance model v1.0". Overview Diagram Why We're a growing project! And to keep up with everything that's happening, it's essential that people who want to help are empowered to do so. Reorganizing the working group is part of that. Right now it can be unclear who's working on what, who to ask a particular question, and when it's OK to do something or if you need a review. So this structure aims to be:

In the regulation proposal: Individuals MAY be a Domain Lead for multiple Domains and/or be a Board Director at the same time. However it's strongly preferred for them to hold only one such role at a time, in order to promote diverse and meritocratic leadership and limit risks. Domain Lead for multiple Domains When it comes to being a Domain Lead for multiple Domains, there are some reasons why that's not preferred, but allowed. The pros: A trusted and qualified person will have the ability to help out in this role, which they couldn't if they were barred from the role due to a 1-role limit.

These are important to note and communicate, but not part of the regulation. The path to becoming Domain Lead. And offboarding. Have appointing seasons, (Spring / Autumn appointing). Though not locked in regulation. Board should check in. So Domain Lead is like an opt-in and renewal position. To create regular check in moments. About 6 months is a good period. Resigning always an option. Only gotcha is if any (access) transfers need to happen. Such as making sure we don't lose admin access to something. Or ongoing projects get a new point of contact. This is a shared responsibility in the regulation, to account for the unforseen situations. However in practice it should be a Board responsibility to plan for offboarding and avoid needing this clause to be used. The Board will be notifying someone resigning of the status:

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:

[ ] 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

What As the Board find & communicate high-level priorities for the Tauri Programme. Ensure an ongoing discussion / evaluation of those priorities happen. Why Time is one of the most important resources for an engineer / contributor. And priorities help in deciding what (not) to spend your time on. While my belief is that the Tauri Board is not in a position to "top-down" tell anyone what to do, we can be of service by doing the (possibly contentious) work of putting out an advisory for priorities. Making it easier for people to work towards the same goals, if they so desire. And reducing cognitive load for others.

Based on paper scribbles, it should give a rough idea of what I imagine the different domains to be doing. Tauri Board Trademarks - Funding - (IP) Assets - Credentials & Admin access Controversial topics - Domain Lead escalations - Bus-factor & continuity An effective Board results in: Alignment and continuity (resilience, constant flow) Domain: Governance & Guidance Teams - Project Management - Process - Domain Lead Meetings

Note: I've disabled editing after the meeting. Thanks for all the input, I'll write up PRs based on this to finalize them. Goals Get started dogfooding Initiatives plugin. Start with the most underserved ones (like CredCon / Maker partnership). Side goals