Philosophy & Core Values

Quantum Hue is a developer-focused open-source collective building native software utilities that bridge gaps in the modern Linux desktop and Android ecosystems.

Performance Matters

We avoid heavy runtimes and large containerized frames. By choosing native compiled technologies like Rust, C++17, and Kotlin, our software remains highly efficient, responsive, and easy on battery life.

Privacy by Design

We reject cloud dependencies for personal synchronization. If you transfer files or sync notifications (like in ValenceLink, Valence Cloud, and ValenceDrop), it happens directly over encrypted local channels or dedicated WebDAV instances. No proprietary cloud, no telemetry, no tracking.

Native Integration

We leverage low-level Linux primitives like eBPF for security telemetry, PipeWire and WirePlumber for media routing, and Wayland protocols for color management. Our interfaces use modern native GUI toolkits like Qt6 and GTK4.

Contribution Guide

We welcome contributions of all forms, from bug reports and documentation fixes to full feature additions. Here is how you can get started contributing to Quantum Hue projects:

1. GitLab Workflow

Our codebases are hosted on GitLab under the Quantum Hue namespace. We follow a standard forks-and-merge-requests model:

  • Fork the repository of the application you want to modify.
  • Create a branch for your changes (e.g., feature/your-feature-name or fix/issue-description).
  • Commit your changes with clear, descriptive commit messages.
  • Ensure all workspace tests pass and the code compiles without warnings.
  • Push to your fork and submit a Merge Request (MR) targeting the main branch of the upstream repository.

2. Code Standards & Testing

To maintain high software quality across our ecosystem, we request that contributors adhere to these rules:

  • Warnings: All code must compile warning-free (e.g., cargo build or make should run cleanly).
  • Formatting: Run the language formatter before committing (e.g., cargo fmt for Rust, clang-format for C++, or ktlint for Kotlin).
  • Tests: If you are adding logic, write corresponding unit tests to verify behavior and prevent future regressions.
  • Documentation: Keep the README, inline comments, and codebase documentation updated for any user-facing settings or design updates.

3. Licensing & Provenance

Quantum Hue projects are distributed under permissive or copyleft open-source licenses to guarantee user freedom:

  • Desktop integration/system utilities are typically licensed under GNU GPL v3.0 (or newer).
  • Flagship consumer software (like Chromatic Crucible) is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).
  • Please include standard SPDX-License-Identifier headers at the top of any new source files you create.