Skip to content

Development

mrrizkin edited this page Oct 30, 2026 · 1 revision

Development

Layout

Path Role
crates/qd-core engine: protocol, discovery, sender, receiver
crates/qd qd CLI
crates/qd-daemon quicdropd: loopback HTTP/SSE API, history, approval plumbing
apps/desktop Tauri shell (outside the workspace) and the buildless ui/
packaging/ PKGBUILD, Flatpak manifest, desktop entry, AppStream data
.github/workflows/ ci gates, release artifacts on v* tags, flatpak bundle

Behavior belongs in qd-core; hosts only wire it up. Changing a frame shape or its meaning bumps PROTO_VERSION.

Recipes

just verify    # fmt check, clippy, workspace tests
just build     # release build of qd and quicdropd
just desktop   # run the Tauri app
just bench     # loopback end-to-end transfer benchmark
just bench-core

just fmt and just lint also cover apps/desktop.

Version tags

Tags are v<YEAR>.<ISO week>.<patch> in UTC:

just next-version   # print the next tag
just tag            # stamp, commit and tag

Conventions

  • Everything a peer sends is untrusted input; new limits get a constant and a check.
  • Keep apps/desktop/ui buildless: no npm, no bundler, colors come from CSS tokens.
  • Docs and comments state what is true now.
  • Commit no build output, keys, .env, or local state.

Clone this wiki locally