Skip to content
GitHubDownloadENES

Community

Build it with us.

Ixolo is developed in the open. Every contribution counts: code, testing on real hardware, documentation or teaching material.

How to contribute

  1. 1

    Fork it

    Clone the repository and create a branch for your change.

  2. 2

    Test locally

    Run the test suite in QEMU with releasetools/qemutest.py before sending anything.

  3. 3

    Open a pull request

    Against the devel branch. Continuous integration builds and tests it.

  4. 4

    Review

    We comment, iterate and merge it.

Contributor guide →

Issues

Report bugs and propose improvements.

GitHub Issues →

Conversation

Questions, ideas and help between users.

[CHAT] →

Teachers

Share labs and classroom material.

[MAILING_LIST] →

Code of conduct

A respectful space for everyone.

Read the code →

Tested it on real hardware?

Physical machines are where we need help most. Open an issue with the machine model, whether it booted (UEFI or BIOS) and the console output.

Code of conduct

  • Be respectful and assume good faith. Criticise code and ideas, not people.
  • No harassment, discrimination or personal attacks, in any channel.
  • Help newcomers: everyone started by not knowing how a kernel boots.
  • Report problems privately to the maintainer: David Montero.

Draft. The full text will follow the Contributor Covenant 2.1.

News and release notes

The latest from the project.

[DATE] · Release

Ixolo [VERSION] is here

Multiprocessor amd64, journaling MFS, UEFI and an experimental Wayland desktop.

[DATE] · Project

New name, same soul

Why this MINIX 3 fork is now called Ixolo, and who Xolo is.

[DATE] · Engineering

SMP on amd64: a tale of two bugs

A pointer truncated to 32 bits and a race in the scheduler. How we found them.