microsoft / microsoft/winml-cli
[winml] [P2] Multiple brand spellings in use (`WML`, `WinML`, `winml`, `Windows ML`, `ModelKit`)
- Dominant language
- Python
- Stars
- 40
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 50
Description
Severity: P2
Command: winml
Category: Naming Consistency — pick one canonical product name and use it everywhere.
Repro:
uv run winml --help
uv run winml --version
uv run winml export --help
Actual: Five different forms appear in user-visible output:
winml --helpfirst line:WML ModelKit - Accelerate Model Deployment on WinML.(uses WML and WinML in the same sentence).winml --versionprints:winml, version 0.0.2(lowercase winml).winml export --helpfirst line:Export HuggingFace model to ONNX format with HTP.(no brand).winml inspectpanel header readsWinML Inference Class.winml systable headers readWindows MLfor the OS service andwinmlfor the CLI.
Expected: Pick one canonical capitalization (e.g. WinML ModelKit for the product, winml only as the literal command name) and use it in every place a user can read it: top-level docstring, every subcommand docstring, --version output, every panel/table title, README.md, and pyproject.toml. Concretely:
- Replace
WML ModelKit→WinML ModelKitin the top-level docstring. - Make
winml --versionprintWinML ModelKit, version 0.0.2 (winml CLI).
Why it matters: Users searching docs/issues for the product name need one term. Marketing/legal usually require one canonical capitalization too.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.