Skip to main content

2026-03-18 - Governance weekly

  • Date: 2026-03-18
  • Participants: raito, horrors, piegames, rootile, kate, Qyriad.
  • Topic: Lix governance weekly

Agenda

  • Job channel
  • Inactive core team members
  • Retrospective on the 2.95 release situation
  • Various status updates from @raito for AFNix
  • LixCon 2026 status

Conclusion / Action items

Job channel

Lix will postpone exploring a job channel idea until past LixCon and will mesh this problem with a sponsorship policy.

Inactive core team members

https://git.lix.systems/lix-project/lix-website/pulls/69 is approved and merged along https://git.lix.systems/lix-project/lix-website/pulls/70.

  • Lily Foster
  • 9999years (Rebecca Turner)

are disboarded from the core team role in the Lix project. Thanks for all their help and support towards the Lix project.

@piegames will adjust the governance document to better match our current procedures.

The Lix core team will examine in a future meeting whether to maintain a "historical core team member" section.

Retrospective release situation

Split into two topics:

  • the current 2.95 crisis, @raito @kate @horrors are addressing it.
  • how to avoid repeating this mistake? post-poned to future meetings as we would like to have Jade part of this.

Status updates from @raito

LixCon 2026

  • @raito expects more core team talks for LixCon and will pester core team members in private.
  • @raito needs graphical design for LixCon, @hexchen seems sick and someone needs to take over. @kate offered to work on this.
  • DGNum proposed a meeting at M-1 for LixCon but Lix did not respond. @kate propose we set up a weekly (in 4 weeks) between DGNum and Lix for LixCon. @raito proposed a scheduling link to both sides.

Future agenda

  • Examining our posture on perfectionism vs incremental changes.
  • Historical core team members section.

Meeting notes / Discussion

NoAgenda:

meeting
notesJob channel
    pennae: We want to do it mostly for employees than employers. pennae: We should maybe make it the other way around and let people post they're looking for jobs. kate: it would prove difficult for companies to actually operate with this due to the whole bias. kate: having employers post ads as long as they behave in our code of sufficientconduct. qualitylet's were takenshelve this time.topic as there might not be enough demands to justify the costs of doing it right, at least, after lixcon. @piegames own the fact of starting a draft on sponsorship policy. Inactive core team members
      Merge https://git.lix.systems/lix-project/lix-website/pulls/70 and https://git.lix.systems/lix-project/lix-website/pulls/69 Qyriad: what about the proposal for alumni/emeritus section? Kate: thinks this would be good to be able to list historical core team members to permit core team members to use this for hiring decisions. pennae: wouldn't archive.org satisfy this objective too? Kate: a hiring manager would not bother with that. No objection to merge these two PRs. @piegames will adjust the governance document to better match our current procedures Retrospective release situation
        QA is required for 2.95.1 & 2.94.1 releng for 2.95.1 is owned by @raito if no one else will do it Feature / merge freeze policy for releases owned by @raito but after LixCon Testing commonly used 3rd party programs (direnv / devenv) with new Lix releases Static builds should go into Hydra for the next releases, not sure we should put them back into CI
          expensive we do not need them very often AFNix: convert releng to Hydra and automatic things [Status update, Raito] LixCon talks from the core team [Status update, Raito] Fundraising for Lix project [AFNix] [Status update, Raito] Sponsorship of Mercury in LixCon [Status update, Raito] AFNix project representative [AFNix]
            https://docs.afnix.fr/policies/afnix-membership.html [Status update, Raito] LixCon 2026
              We need graphic design for LixCon DGNum team has proposed a meeting Scheduling a weekly between DGNum and Lix for LixCon