Skip to content

docs(mini_memo): use openvelaClaw brand name to reduce trademark risk - #636

Closed
tanghao-xiaomi wants to merge 1 commit into
open-vela:dev-ai-contest-2026from
tanghao-xiaomi:docs-rename-velaclaw-brand
Closed

docs(mini_memo): use openvelaClaw brand name to reduce trademark risk#636
tanghao-xiaomi wants to merge 1 commit into
open-vela:dev-ai-contest-2026from
tanghao-xiaomi:docs-rename-velaclaw-brand

Conversation

@tanghao-xiaomi

Copy link
Copy Markdown
Collaborator

Summary

Rename the brand-styled references VelaClaw to openvelaClaw in the mini_memo guide, to reduce trademark risk. Prefixing with the open-source project name openvela (with capital C in Claw) is a lower-risk brand form than the bare VelaClaw.

  • 18 CamelCase brand mentions VelaClaw -> openvelaClaw (prose, tables, headings, and descriptive comments in code blocks).

  • The actual framework API identifiers are intentionally left unchanged:

    • lowercase code: velaclaw_client_open(), velaclaw_ask, @system.velaclaw
    • uppercase macro: VELACLAW_DAEMON

    These are the real API/feature names that participants call, so renaming them here would break the examples.

Scope

  • Single file: docs/zh-cn/contest_2026/ai_hardware/mini_memo_guide.md
  • Documentation-only change; no code or API behavior affected.

Note

This only adjusts brand wording in one contest doc. Renaming the underlying framework feature (the velaclaw API / @system. namespace) is out of scope and would require a coordinated upstream change.

Rename the brand-styled references 'VelaClaw' to 'openvelaClaw' in the
mini_memo guide prose. The lowercase code identifiers (velaclaw_client_open,
velaclaw_ask, @system.velaclaw) and the VELACLAW_DAEMON macro are the actual
framework API and remain unchanged.
@tanghao-xiaomi

Copy link
Copy Markdown
Collaborator Author

Superseded by #638, which combines the rename and the CI check into a single PR. Closing this one.

tanghao-xiaomi added a commit that referenced this pull request Jul 28, 2026
Add a lightweight PR check that fails when the CamelCase brand form
'VelaClaw' appears in any Markdown file. The convention is to use
'openvelaClaw' (lowercase 'openvela' prefix, capital 'C') as the brand
name in prose, to reduce trademark risk.

The check is intentionally case-sensitive and does NOT flag:
  - lowercase code identifiers: velaclaw, @system.velaclaw,
    velaclaw_client_open, velaclaw_ask (real framework APIs)
  - uppercase macro: VELACLAW_DAEMON (real Kconfig / macro name)

Note: this check depends on the brand rename in #636 being merged
first. Otherwise the base branch's existing 'VelaClaw' occurrences
would cause subsequent PRs to fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant