Get involved
Community
Early-stage project. Small, responsive maintainer. The best way to help right now is to open a Discussion with what you built — real setups inform the docs more than anything else.
Where to go
- GitHub DiscussionsFirst stop for anything that isn't a bug. Questions, ideas, what-you-built showcases. Replies within 72 hours, usually less.Browse discussions →
- GitHub IssuesBug reports and feature requests. Please search first — duplicates cost everyone's time. Include platform, version, and reproduction steps.Open an issue →
- Security disclosuresDo not file security issues on public Issues. Follow the process in SECURITY.md — private channel, scoped to the maintainer.See SECURITY.md →
- DiscordOpens once active-user count crosses ~100. Follow Discussions for the announcement — the invite will go out there first.Coming soon
Quick triage
- It crashed — where do I file that?
- GitHub Issues. Attach the OS-generated crash report (macOS Diagnostic Reports, Windows Event Viewer, Linux coredump) and the LumaSync log file. Log locations.
- My hardware isn't recognised — is this a bug?
- Probably not a bug, probably an unsupported chip. Check USB controllers first. If it IS a CH340 or FT232 and still fails, open an issue with
lsusb/ Device Manager output. - I want a feature — will you build it?
- Discussions → Ideas. Explain the use case (what problem, who has it). Popular asks with clear scope make it to issues; vague asks get a polite "not planned".
- I have a question about Philips Hue itself.
- That's upstream — try the Hue developer portal or the Hue subreddits. If the question is specifically about how LumaSync uses Hue, come back to Discussions.
House rules
LumaSync follows a standardCode of Conduct. Short version: be helpful, be specific, and don't be a jerk. Disagreement is fine; dismissiveness isn't. Project is MIT-licensed; contribution guidelines live inCONTRIBUTING.md.