Skip to content

chore: Use project-neutral terminology - #672

Open
timflannagan wants to merge 1 commit into
agentregistry-dev:mainfrom
timflannagan:cleanup/use-project-neutral-wording
Open

chore: Use project-neutral terminology#672
timflannagan wants to merge 1 commit into
agentregistry-dev:mainfrom
timflannagan:cleanup/use-project-neutral-wording

Conversation

@timflannagan

@timflannagan timflannagan commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Description

Replace edition-specific and branded terminology in extension examples,
templates, and test fixtures with project-neutral language. Use "embedding
application" where "downstream" was shorthand rather than a literal dependency
relationship, and remove the vendor attribution from the UI footer. Clarify
that MCP registry compatibility routes are unauthenticated by default, while
existing authorization hooks can constrain anonymous reads.

Change Type

/kind cleanup

Changelog

NONE

Additional Notes

Contextual uses of Enterprise and literal dependency-direction uses of
"downstream" remain unchanged. Persisted agentregistry.solo.io labels and
annotations also remain unchanged so existing resources retain ownership and
compatibility across upgrades.

Focused Go package tests and ESLint for the changed footer passed. Broad
make test and make lint targets were not run.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR standardizes project-neutral terminology across the repo’s docs, templates, examples, and test fixtures, and removes the vendor attribution from the UI footer while preserving existing footer functionality.

Changes:

  • Removed vendor attribution text/link from the UI footer.
  • Updated docs/templates/test fixtures to use project-neutral wording (e.g., “extension”, “self-hosted”, “reference implementation”).
  • Adjusted various narrative comments and examples to align with the new terminology.

Reviewed changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
ui/components/footer.tsx Removes vendor attribution from the footer while keeping the rest of the footer intact.
pkg/registry/v1alpha1store/rebase_fuzz_test.go Updates terminology in fuzz-test commentary about authz seams.
pkg/cli/root_test.go Updates test fixtures that refer to “enterprise” to “extension”.
pkg/cli/README.md Updates downstream CLI customization examples to use project-neutral placeholders.
pkg/api/v1alpha1/scheme_test.go Renames a fixture resource name to project-neutral wording.
internal/registry/registry_app_test.go Renames a fixture reference to project-neutral wording.
internal/cli/skill/templates/hello-world/references/example_guide.md.tmpl Replaces “Enterprise systems” phrasing in an example guide.
internal/cli/frameworks/builtin/adk-python/templates/pyproject.toml.tmpl Removes vendor-specific attribution in template comments.
internal/cli/frameworks/builtin/adk-python/templates/{{.Name}}/agent.py.tmpl Rewords template comments to remove vendor-specific attribution.
internal/cli/common/gitutil/gitutil.go Updates wording around supported Git hosts for neutral terminology.
internal/cli/common/gitutil/gitutil_test.go Updates test case naming for neutral terminology.
docs/mcp-registry-compatibility.md Updates client configuration guidance to neutral terminology.
docs/governance/cncf/technical-review.md Rewords governance documentation to avoid “enterprise client” phrasing.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread docs/mcp-registry-compatibility.md Outdated
Comment thread internal/cli/common/gitutil/gitutil.go Outdated
Comment thread internal/cli/common/gitutil/gitutil_test.go Outdated
Comment thread pkg/registry/v1alpha1store/rebase_fuzz_test.go
@timflannagan
timflannagan force-pushed the cleanup/use-project-neutral-wording branch from 1837a16 to 0a72b01 Compare September 1, 2026 16:58
Replace edition-specific and branded names in documentation, examples, test
fixtures, and the footer attribution with project-neutral language for
embedders.

Contextual product references and persisted label and annotation namespaces
remain unchanged to preserve technical meaning and resource compatibility.

Signed-off-by: timflannagan <timflannagan@gmail.com>
@timflannagan
timflannagan force-pushed the cleanup/use-project-neutral-wording branch from 0a72b01 to be60325 Compare September 1, 2026 17:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants