chore: Use project-neutral terminology - #672
Open
timflannagan wants to merge 1 commit into
Open
Conversation
Contributor
There was a problem hiding this comment.
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.
timflannagan
force-pushed
the
cleanup/use-project-neutral-wording
branch
from
September 1, 2026 16:58
1837a16 to
0a72b01
Compare
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
force-pushed
the
cleanup/use-project-neutral-wording
branch
from
September 1, 2026 17:03
0a72b01 to
be60325
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Additional Notes
Contextual uses of Enterprise and literal dependency-direction uses of
"downstream" remain unchanged. Persisted
agentregistry.solo.iolabels andannotations 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 testandmake linttargets were not run.