docs: add research findings for license and tags auto-derivability in V1 registry#471
Merged
jaydeluca merged 1 commit intoMay 18, 2026
Conversation
✅ Deploy Preview for otel-ecosystem-explorer ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jaydeluca
approved these changes
May 18, 2026
Member
jaydeluca
left a comment
jaydeluca
left a comment
There was a problem hiding this comment.
looks good. perhaps as part of the next step, we could add these fields to the components metadata in the V2 registry as part of the watcher?
Contributor
Contributor
Author
|
Hi @jaydeluca Thank you for the feedback and for merging this. That is a great suggestion, I will look into adding these fields to the V2 registry component metadata as part of the watcher in a follow up. |
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
2 participants
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.
This PR adds the research findings for issue #461.
The investigation checked existing V1 registry entries at
opentelemetry.io/data/registry across all five component types (receiver,
exporter, processor, extension, connector) to answer whether the license
and tags fields can be generated automatically when creating new V1 entries
from V2 data.
The short answer is yes for both.
Every single collector entry in V1 uses license: Apache 2.0. All
opentelemetry-collector and opentelemetry-collector-contrib components are
Apache 2.0 by project policy, so this can just be hardcoded during generation.
For tags, every entry follows the same three-tag formula: go, the component
type, and collector. Since the component type is already in V2 metadata and
the other two are fixed for all collector components, the entire tags list
is predictable without any manual input.
With these two fields confirmed as auto-derivable, the only field that truly
requires a human reviewer when generating a new V1 entry is authors. The
createdAt field can be approximated from git history. This makes Proposal B
from issue #119 much lighter to implement than originally estimated.
Closes #461