Community
Luxir is developed in the open on GitHub under the Apache License 2.0. This page is who is building it and how to take part.
People
Section titled “People”
Get involved
Section titled “Get involved”- Questions and ideas go to GitHub Discussions. Asking there rather than in a private message means the answer helps the next person too.
- Chat happens on the Luxir Discord server: quick questions, getting-started help, and talking through an idea before it becomes an issue. Anything worth finding again later belongs in Discussions.
- Bugs and feature requests go to GitHub Issues. For a
bug, include the commit or version, the request you sent, what came back, and what you expected.
A
curlreproduction against an empty collection is ideal. - Working on the engine starts with Build setup and the Codebase map. The contributing guide covers conventions, tests, documentation, and how changes are reviewed.
- Security problems go to security@luxir.org, not the issue tracker; the repository’s security policy says what to include and what to expect.
- Documentation lives in the repository’s
docs/directory and is published here on every change tomain; every docs page has an “Edit page” link.
Luxir follows the Apache Software Foundation’s code of conduct; concerns that cannot be raised publicly go to private@luxir.org. Contributions may use AI tools within the AI policy: you stay responsible for what you submit and can explain it in your own words, and communication with maintainers is written by people.
Governance
Section titled “Governance”Luxir is licensed under the Apache License 2.0, and contributions are accepted under the same license, so nobody’s work can later be relicensed out from under them. The project’s intent is to live under vendor-neutral, community governance for the long term; until that structure is in place, the people listed above make decisions in the open, on the issue tracker and in discussions, and welcome new committers who have shown sustained, careful contribution.