microsoft / microsoft/winml-cli

[winml] [P2] Multiple brand spellings in use (`WML`, `WinML`, `winml`, `Windows ML`, `ModelKit`)

Open
#510 2 comments 0 reactions 2 assignees View on GitHub

@fenghuaxueyue98 is already working on this.

Since Jul 10, 2026.

  • #1092 by @fenghuaxueyue98 — open
bug dev experience P2 quality triaged
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 --help first line: WML ModelKit - Accelerate Model Deployment on WinML. (uses WML and WinML in the same sentence).
  • winml --version prints: winml, version 0.0.2 (lowercase winml).
  • winml export --help first line: Export HuggingFace model to ONNX format with HTP. (no brand).
  • winml inspect panel header reads WinML Inference Class.
  • winml sys table headers read Windows ML for the OS service and winml for 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 ModelKitWinML ModelKit in the top-level docstring.
  • Make winml --version print WinML 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.