The Liminix Developers Manual is at https://www.liminix.org/doc/development.html
Automated builds are run on each push to the
main branch. This tests
- 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
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 firstname.lastname@example.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.