2026-08-03 – Governance Weekly

Date: 2026-08-03
Participants: raito, rootile, horrors, piegames
Meeting notes backlog checkin [piegames]
[piegames]: Restructuring of meeting notes in the pad complete, pinged raito for further processing
[piegames]: Waiting for more meeting notes to restructure (transcriptions etc.)
[piegames]: Discussion notes have been moved, automatic sorting is broken and I won't debug it
[piegames]: Documenting how to do discussion notes still TBD
[raito]: Didn't start yet, hopes to do >50% of the notes by the end of the week
[rootile]: Still waiting for the recordings to transcribe
Maintenance of Hydra [rootile]
recent hydra breakages/regressions; yet again
Who is responsible for Hydra working on latest lix?
hydra in lix CI?
Discussion:
Technically ma27 is the only person working on Hydra
Hydra lacks good tooling to facilitate maintenance
Putting hydra in CI has been a goal from the start, but it's complicated
Past discussion of putting hydra in-tree in Lix
What expectations of maintenance do we want to set for Hydra?
Add to announcement list looking for people to help out
Base problem with Hydra is not that is breaks, but that it stops compiling any time Lix has any architectural changes.
Hydra is mostly maintained for releases, not for Lix on Main (needs documenting)
Hope for an RPC-native Hydra replacement
Action items
Document Hydra is currently maintained for Lix releases
Discuss moving Hydra into Lix tree with Ma27
Announcement looking for more maintainers specific to lix-on-main
Release plans for 2.96 [raito]
A couple of issues remaining in the milestone on Forgejo (some labeled blocking)
https://git.lix.systems/lix-project/lix/issues/686 needs some help
Discussed https://git.lix.systems/lix-project/lix/issues/1145
Discussion:
Release sooner rather than later
Aim for September?
Re-organisation plans [raito]
Code review and development policies
Document in the wiki: How to do a code review?
Document how to send a change
Document +2/-2 etiquette
Document porting patches from CppNix to Lix (talk with us first)
Formal leadership roles
Make it easier to accept/reject changes w.r.t. architectural direction of the project
Clarify the owners and stakeholders to reduce cognitive load
Want a technical leader
Admin lead?
Currently, raito is SPOF on lots of admin stuff
Discussion:
We already have https://wiki.lix.systems/books/contributing/chapter/intro-to-gerrit, but mostly scoped to Gerrit in general (I think)
https://wiki.lix.systems/books/contributing section needs revisiting and working through
How to update the technical leader?
tech lead must be core team member
Maybe have a shared VaultWarden?
AFNix will owns all the Lix resources
Action items
Make a proposal for code review and dev policy, make it reviewed by the core team
Review the existing contributing / intro-to-gerrit architecture and make suggestions in which direction should we go
piegames can take care of enacting the changes
Document team lead on the team page on the homepage, and mention it in the contributing guides
Let's try to derisk the SPOF that raito is as an admin person of the project, via attracting new contributors
Lix quarter calls [raito]
It has been a year since we've established our Governance, and we haven't had any town halls
If doing it, presence of core team would be important
Discussion:
Raito takes care of the town halls
Core team will be present