Skip to content

Latest commit

 

History

History
98 lines (82 loc) · 6.78 KB

publication.md

File metadata and controls

98 lines (82 loc) · 6.78 KB

Source publication and licensing

Technical documentation

Capy Canvas's original software and non-brand assets use MIT OR Apache-2.0: recipients choose either license. Every workspace crate inherits this declaration from the root manifest, and the About page reads that package metadata. Keep both license texts, third-party notices, and the separate branding terms. The names and designated capybara mark are not included in the software license grant.

The MIT option enables broader downstream reuse, including GPLv2 projects, as discussed in Graphite's relicensing proposal. It does not permit importing GPL-covered implementations into our permissively licensed source. Nor does it change Apache-only dependency terms; downstream consumers must assess their actual dependency graph. See Apache's compatibility guidance.

Included assets and provenance

Material Origin and distribution terms
Application Rust, WGSL, web UI and tests Project implementations, MIT OR Apache-2.0; the Oklab conversion exception is attributed separately.
apps/layer-web/icons/*.svg, except the Zen mark Original generic vector assets, MIT OR Apache-2.0. No GNOME icon set is vendored.
Four apps/layer-web/icons/layer-zen-*-symbolic.svg files listed in BRANDING.md Vector traces of owner-supplied capybara artwork; covered by the separate Capy Canvas Branding License. Looking up is the default app mark.
assets/brushes/*.pgm First-party numeric brush masks introduced during brush-engine development; not a redistributed commercial or GPL brush pack.
apps/layer-apple/iOS/AppIcon.png The iPad App Store icon: the default mark in #f6f5f4 at 880/1024 on #767676, the web icon's proportions, rendered with resvg and saved as RGB because the App Store rejects icons with an alpha channel. Covered by the Capy Canvas Branding License.
apps/layer-web/brush-previews/*.webp Runtime assets rendered from project presets by crates/layer-bench/src/previews.rs. Regenerate with cargo run --release -p layer-bench -- --brush-previews. No external reference images or fonts are used by that generator.
assets/filters/filter_preview_tiles.rgba and apps/layer-web/filter-previews/*.webp Runtime assets: procedural tiles from crates/layer-render-wgpu/src/filter_preview_tiles_tests.rs and each built-in filter rendered over them. Regenerate with the ignored write_filter_preview_tiles and write_bundled_filter_previews tests. No external reference images are used.
Oklab conversion functions Adaptation of Björn Ottosson's MIT reference; exact notice and local modifications are recorded in THIRD_PARTY_NOTICES.md.

Runtime controls may use system fonts and system-provided GTK resources; those resources are not copied into this source checkout. Research documents link to upstream documentation, papers and implementations. A reference is not a license to copy its code, figures, screenshots, textures or other artwork.

Adding dependencies

Add a dependency or vendored code only when the project cannot reasonably do without it. After adding or updating one, run cargo deny --locked check advisories licenses sources and add any required notice to third-party notices. Vendored crates follow the vendor rules.

Publication checks

Automated scans and source review reduce risk; they are not a legal guarantee of ownership or noninfringement. The branding policy reserves rights but does not register trademarks; obtain legal review before relying on it for enforcement. Repeat these checks before publishing:

  1. Review git diff --cached and git ls-files. Do not include local credentials, absolute personal paths, browser profiles, machine-specific logs, screenshots or build outputs. Scan the exact staged tree for secrets, not just the working directory. Inspect binary metadata and provenance whenever an asset changes.
  2. Install cargo-deny and run cargo deny --locked check advisories licenses sources. The allowlist checks build/dev dependencies and all platform targets. Missing licenses, unreviewed licenses and non-registry sources fail the gate. License expressions containing OR permit a choice; AND requires both terms.
  3. Keep Cargo.lock tracked. Check dependency updates and preserve every required upstream notice; a successful allowlist check does not fulfill those obligations.
  4. Run the checks for every area, including the Wasm target.
  5. Publish only the reviewed branch. When replacing history, preserve a private recovery copy outside the source checkout and verify that the public branch has only the intended root commit. New history does not erase old remotes, previously published commits or other people's clones. Rotate any exposed credential; a history rewrite alone cannot revoke it.

artifacts/ is entirely local and ignored, including review PNGs, benchmark reports, traces and historical baseline notes. Paths under that directory in design documents describe local outputs, not files included in a fresh clone. Build trees, generated Wasm bindings and local editor/agent state are also ignored. The runtime brush previews and the iPad icon above are the intentional exceptions for generated images: the frontends need the previews without running a GPU generator at startup, and Apple builds need the icon without an SVG renderer.

Separate binary-release gate

This audit prepares the source repository, not an executable release. Native packages and web bundles must ship the required notices for their exact Rust, toolchain and system dependencies. GTK/libadwaita and other system libraries retain their own terms, including applicable LGPL requirements. Do not assume that our MIT option relicenses them or satisfies redistribution obligations. Review actual packaged contents before publishing binaries, WebAssembly bundles, containers or vendored source archives.

CI checks RustSec advisories alongside licenses and sources. The advisory policy has two exact maintenance-notice exceptions: the bounded stroke-recording serializer and the decoder build-time macro. These do not suppress other advisories for those packages. Review upstream security disclosures as well; the advisory database does not contain every published implementation finding.

The web packager now generates a separate static distribution with Wasm dependency/toolchain notices, branding terms and runtime path checks. Those generated files stay in ignored dist/, not in the source repository. Review its output whenever dependencies or bundled assets change; native binary distribution remains a separate gate.