Development
Liminix development is hosted at https://gti.telent.net/dan/liminix (or if you’d rather use Github, there’s a mirror at https://github.com/telent/liminix).
Development manual
The Liminix Developers Manual is at https://www.liminix.org/doc/development.html
Automated builds
Automated builds are run on each push to the main
branch. This tests
that
- every device image builds with nixpkgs stable
- the build for the “qemu” target also builds with nixpkgs unstable
- the build for the “qemu” target is executed with a fake network upstream to test
You can view the build output at build.liminix.org. The tests are defined in ci.nix.
Contributing
Contributions are welcome, though in these early days there may be a bit of back and forth involved before patches are merged: please get in touch by email to devel@liminix.org before you invest a lot of time into a code contribution I haven’t asked for. Just so I know it’s expected and you’re not wasting time doing something I won’t accept or have already started on.
-
The primary avenue to code contribution is email-based: just send your patches to the emailing list. Check out the tutorial at git-send-email.io for more instructions on tooling that can make this simpler.
-
If that looks too daunting but you’re familiar with Github, you can instead open a Github PR - but just be aware you may not get a response as quickly.
Code of Conduct
Liminix is dedicated to providing a harassment-free experience for everyone. We do not tolerate harassment of participants in any form.
The Liminix Code of Conduct applies to all Liminix spaces, including the IRC channel, mailing lists, and any Github forums, both online and off. Anyone who violates this code of conduct may be sanctioned or expelled from these spaces at the discretion of the project leadership.