Ways to contribute
File a bug report
Issue templates walk you through the minimum we need: Windows build (winver), GPU and driver version, the failing scenario, and the relevant slice of sunshine.log.
Propose an idea
Big design changes start as a Discussion thread, not an Issue. Float the rough shape of the change first so we don’t waste your time on a PR that won’t land.
Open a pull request
Small, focused PRs land fastest. Match the existing code style (.clang-format, .prettierrc) and include a brief test plan in the description.
Improve the docs
Docs PRs are first-class — especially troubleshooting notes, hardware compatibility, and clarifications to the configuration reference.
Build & tooling at a glance
LuminalShine builds on Windows using clang with --fms-extensions — this differs from upstream Sunshine, and is what lets us pull in MSVC-specific Win32 features without committing to the full MSVC build chain. The Web UI is built with Vite, Vue 3, and Tailwind CSS, with Lucide and Simple Icons for iconography.
Licensing of contributions
By submitting a pull request you agree that your contribution is licensed under the same terms as the project — GNU GPL-v3. There is no CLA. We do ask that you only submit code you have the right to license.
Code of conduct
Be respectful, assume good faith, and keep discussions focused on the technical work. The NortheBridge Foundation reserves the right to remove comments and contributors that are disruptive to the project or hostile to other participants.