Contribute / Dutchman CAD

Help make Dutchman better:
four ways, pick your level.

Start by using Dutchman Convert on your own designs. Tell us what didn’t come across, investigate with your AI, or take a fix through to a pull request. You choose how far to go.

Tier 1

Use it

Install Dutchman Convert, then convert as many of your own files as you can. Try whole folders, parts and assemblies. Open the results in SolidCraft and see what doesn’t come across yet.

dutchman --version
dutchman convert-all --out-dir converted ./my-designs
dutchman doctor ./my-designs --out checked

convert-all searches subfolders. doctor checks a folder, diagnoses failing designs and groups repeated findings. Keep both output folders outside your input library; use fresh output paths for a new run.

Tier 2

Report it

Every conversion shows you what it lost. Nothing is sent to us unless you send it. Choose the route that suits you:

  • Private DM. Message Dutchy on Discord. If you choose to send a design of your own that you have the right to share, send its STEP export too. Files sent this way are private by default and used only to fix the converter.
  • Anonymous report. Run the command below, review report-anon.json, then choose whether to share it. It contains counts and causes, without file names, paths or geometry.
  • GitHub issue. Open A file didn’t convert, or use the Library test report form for a batch. File one issue per distinct cause, with the reviewed anonymous report.
dutchman convert-all --out-dir converted --report-anon report-anon.json <files>

Replace <files> with your files or folders. Include the source program and version, the report’s versions block unchanged, and dutchman --version and solidcraft-cli --version output (or “none” if SolidCraft isn’t installed).

Report on Dutchman first, even if the cause is upstream. We work out whether a fix belongs in Dutchman, cadmpeg or SolidCraft, route it, and tell you when a Dutchman release includes it.

Tier 3

Diagnose it
with your AI

Point a local assistant at the failing file’s conversion report. Have it explain the failure stage and finding codes, trace the cause, and help you make a minimum reproduction. Keep private per-file reports local; give a remote chat assistant only the reviewed anonymous report.

dutchman repro part.f3d --out original-reproduction
dutchman repro small.f3d --out small-reproduction

Use your actual file names and fresh output folders. Follow kit/next-steps.md to rebuild a small example in your CAD program using generic shapes and simple public dimensions. Compare the two kits’ anonymous.json: the failure stage and complete set of finding codes must match; counts may shrink. A broad category without structured codes is only a candidate match.

Keep local-key.json and any geometry copied from the original on your computer. Rebuild from scratch before sharing. If the kit says no_failure_to_reproduce, this run succeeded; don’t claim a reproduced failure.

Tier 4

Fix it and
open a PR

Have your AI work on a branch in your fork of dutchman-cad/dutchman, starting from main. Read AGENTS.md and CONTRIBUTING.md before changing code. Rust 1.88 or newer is required.

Build and check a Dutchman change
cargo build --release
scripts/solidcraft-window.sh --print
python3 scripts/check-version-gates.py --base HEAD
python3 -m unittest discover -s scripts/tests -v
cargo fmt --all --check
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked
python3 scripts/changelog.py check
python3 scripts/changelog.py preview

Keep the PR to one topic, add a synthetic regression test with its origin recorded, update affected docs and skills, and add a changelog.d/ fragment. Open against main and make sure CI passes. Use your own account and review what will be published.

Native decoding belongs in cadmpeg; mapping and messages belong in Dutchman; a SolidCraft problem may need a fix there. Report on Dutchman first; we route it. Keep a Dutchman PR that needs an upstream change in draft until that change is merged and Dutchman’s pin includes it. Follow the destination repo’s contribution rules too.

These four website levels run from using the app to a PR. The repo’s “Want to go further?” guide numbers its four steps after reporting: reproduce, diagnose, fix upstream, finish in Dutchman.

Start a conversation

Give this to your AI

Choose your level, copy the prompt and paste it into your assistant. A local assistant can run the checks; a remote assistant can coach you using anonymous reports. The button only copies text.

For agents starting from a link: /llms.txt brings the commands, privacy rules and source guides together.

Other ways to help

Make a fixture

Build small, known designs from the fixture recipes. Type /volunteer on Discord for your personal portal link; the latest recipe booklet (PDF) is linked from that portal.

Take a stress-corpus batch

Help check the test parts in SolidCraft and FreeCAD. The take-part guide explains how to claim a batch and return your results.