Skip to content

Section: Community

Contributing

How to report bugs, propose features and contribute code to Kuro.

Kuro is open source and built with community contributions in mind. You can help by reporting bugs, suggesting ideas, improving the code or just sharing feedback.

Ways to contribute

Before you start

Branch structure

dev is the main branch and the repository's default branch. stable is the release branch. Urgent fixes, such as security patches, can go directly to stable. The contribution guide (opens in a new tab) has the full branch diagram.

Set up a development environment

Get the source
git clone https://github.com/Kuro-Browser/Kuro-Desktop.git

Before setting up a development environment, read the building guidelines (opens in a new tab) that the contribution guide points to. Skipping them can lead to avoidable build errors.

Architecture expectations

Kuro is organized into independent systems, so a feature can evolve without affecting unrelated parts. When you contribute:

  • Keep Kuro-specific code separate from upstream code wherever practical, and make it clear which code is upstream, which is a Kuro modification, which is Kuro-exclusive and which is platform-specific.
  • Keep systems modular. Avoid putting large amounts of unrelated logic in a single file.
  • Avoid unnecessary platform-specific code, so macOS and Linux can follow Windows without major restructuring.
  • Prefer quality over quantity. Every system should prioritize reliability, security, privacy and performance, followed by maintainability, modularity, accessibility and user control.

Pull requests, code style and testing

License

Kuro is distributed under the Mozilla Public License 2.0 unless otherwise specified. See the LICENSE (opens in a new tab) file.