Lix is developed by a community of passionate users! We have no “benevolent dictator for life”, nor a small foundation board that governs the community (or fails to do so). Instead, we rely on teams of our developers and users to carry the burdens of maintenance and governance.

At our core, we are goverened by the Core team and the Community team. Both are supervised by our advisors, which are trusted friends or alumni. The code base is by our committers, who help review and merge changes.

• Our Governance
• Our Values
• Our Community Standards

We all hang around in community spaces, including on Matrix. Feel free to pop into the Lix channels and say hello — we’d love to hear what you think of Lix!

Core Team

The core team are the developers most directly responsible for the Lix project. These folks steer the technical direction of the project, but are also responsible for the administration.

Members (in alphabetical order):

• hexchen (@hexchen, she/her)
  hexchen is working primarily on maintaining and extending the Lix project infrastructure.

• jade (@lf-, they/them)
  jade is working on packaging, testing, infrastructure, tooling, review, stability, and a large amount of the writing in Lix. They recently graduated from a Computer Engineering program at UBC in Canada.

• Lily (@lilyinstarlight, she/they)

• Lunaphied (@Lunaphied, she/her [singular] or they/them [plural])
  Lunaphied spend a disproportionate amount of their time considering how to get FPGAs as far from Earth as possible. When they’re not working on Space Stuff, they consider doing the same for Nix regressions.

• pennae (aka “eldritch horrors”, they/them)
  The shadow at the end of a dark hallway. An ancient, nameless evil. Likes cookies

• piegames (@piegamesde, they/them)
  Originally joined for improving the Nix language and working on the evaluator, stayed for being the glue that holds organizations together. Passionate community builder.

• Qyriad (@Qyriad, she/her [singular] or they/them [plural])
  Build system experts who delve way, way too deep into tooling – so you don’t have to.

• raito (@RaitoBezarius, he/him)
  Raito is working on infrastructure, review of core parts in Lix and lands smalls contributions when bored. He focus on the ongoing asyncification work and general scalability of Lix for large build farm usecases. Additionally, interested into bridging the Snix project with Lix.

• Rebecca Turner (@9999years, she/her)
  Rebecca is working on the evaluator and error messages.

Community Team

The Community team is responsible for steering the community of this project, as well as moderation tasks. It also maintains the public-facing communication, does outreach and public relations on social media, and generally makes sure that we are a safe and pleasant project to be part of.

Members (in alphabetical order):

• hexchen (@hexchen:colon.at)
• jade (@jade_:matrix.org)
• k900 (@k900:0upti.me)
• lunaphied (@lunaphied:lunaphied.me)
• piegames (@piegames:flausch.social)
• qyriad (@qyriad:katesiria.org)

Governance advisors

Governance advisors are trusted community members who have access to the private governance discussion channels. They are responsible for holding our governance processes accountable to the community. They have no formal voting power, but their opinion is highly valued.

• Kate Temkin (@ktemkin, she/her [singular] or they/them [plural])
  Former Core team and Community team
• puck (@puckipedia, she/her [singular] or they/them [plural])
• Rutile (@CommentatorForAll, they/them [plural])
  Code owner of the functional2 test suite

Conflict of Interest Statements

As a community project, it’s important that project decisions are made exclusively for the benefit of the community, and don’t serve any other interests — including personal or corporate gain.

If a team member is unable to do so in any context, they are required to disclose the conflict of interest and to recuse themselves from any leadership decisions affected.

As transparency is important, we’ve included declarations from each core team member regarding any possible conflicts of interest.

• hexchen declare that they have no conflicts of interest regarding the governance of Lix.

• Jade works for Mercury, a financial services startup that uses Nix to build software. Should a governance decision involving these or any other financial ties arise, Jade will recuse herself from the relevant decision-making.

• Lily works for Shopify, a Canadian e-commerce company that uses Nix to build software. Should a governance decision involving these or any other financial ties arise, Lily will recuse herself from the relevant decision-making.

• Lunaphied declare that they have no conflicts of interest regarding the governance of Lix.

• pennae declare that they are beneficiary of a NLnet grant project on Lix. Should a governance decision involving these or any other financial ties arise, pennae will recuse themselves from the relevant decision-making.

• piegames declare that they have no conflicts of interest regarding the governance of Lix.

• Qyriad is a one-third owner of Tactile Metrology LLC (TMLLC), a company that currently sponsors Lix development. TMLLC declares that it has no financial stake in the future of Lix or Nix, no ties to the military-industrial-complex, and a strong commitment to avoiding such ties. TMLLC is owned by individuals, and not VC investors. In addition, they are beneficiary of a NLnet grant project on NixOS. Should any decision arise in which TMLLC’s interests are relevant, Qyriad will recuse herself from the relevant decision-making.

• raitobezarius declares that he’s self-employed in a cooperative, offers Nix-based consulting and training. He currently possess stakes in the cooperative in minority and may be involved in IT strategic decisions. Should a governance decision involving these or any other financial ties arise, raitobezarius will recuse himself from decision-making.

• Rebecca Turner works for Mercury, a financial services startup that uses Nix to build software. Should a governance decision involving these or any other financial ties arise, Rebecca will recuse herself from the relevant decision-making.

These declarations were last updated on Dec 23th, 2025, and are believed to be up-to-date to the current date. If the bolded date is more than 56 days in the past, feel free to reach out via our community channels to request these declarations be updated.