Lix contributors
Information you might want if you're thinking about contributing to Lix
Lix Beta Guide
Thank you for choosing to help us in our beta! There is a lot of work-in-progress documentation a...
Information organisation
Lix has a lot of information as a project, and we want to make it accessible in a way that it can...
Why Lix?
(page under construction. editor's note: parts of https://pad.lix.systems/lix-manifesto (PRIVATE)...
Style Guide
Not just about code, a style guide is a list of decisions we've made, that we want to be consiste...
Language and terminology
Language Most existing Lix documentation is written in British English. We intend to continue wit...
Code
Code changes Tests If at all practicable, all new code should be tested to some extent. If writin...
Operations
Operational Conventions Code Review Self Stamping and Merging On our Gerrit, core members have pe...
Working in the Lix codebase
See also: See also: https://git.lix.systems/lix-project/lix/src/branch/main/doc/manual/src/contri...
Codebase overview
The Lix system is constituted of two broad parts, the evaluator and the store daemon. The two pie...
Freezes and recommended contributions
Suggested contributions Consider taking an issue marked E-help wanted: assign it to yourself and ...
Bug tracker organisation
We have a repo of directly imported nix bugs at https://git.lix.systems/nixos/nix. Please don't f...
Gerrit
What is Gerrit and why do people like it? Gerrit is a code review system from Google in a similar...
Improving build times
Setup Use a clang stdenv: nix develop .#native-clangStdenvPackages Then delete build/ if you were...
Backport guide
Don't forget, using Gerrit is a bit different than other systems. single commits try git cherry-p...
Misc tips
buildbot user style to make the pulsing pills bearable @keyframes pulse_animation { 0% { transf...
Building Locally
See hacking.md in the Lix repo for the main documentation. Extra tips can go here.
RISC-V support
Goal: install lix on a riscv64-linux system The target is a DevTerm R-01, so it's an AllWinner D1...
Branches
The Lix repository contains multiple releases in parallel. The branches work as follows: main. ...
Design documents
This category contains design documents written by the Lix team, which may or may not be implemen...
regexp engine investigation
nix uses libstdc++'s std::regex. it uses whatever version of libstdc++ the host system has. which...
Dreams
This page documents the dreams of the Lix team. These are features which we have generally not ro...
Language versioning
This document is extremely a draft. It needs some editing and discussion before it can be made in...
Docs rewrite plans
Here, for now (public edit link): https://pad.lix.systems/lix-docs-planning
Release names
Release names are the names of frozen desserts. There's a list on Wikipedia of frozen desserts, b...