open-telemetry / open-telemetry/opentelemetry-ruby
Migrate semantic conventions code generation to weaver
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
Semantic Convention tooling group is deprecating build-tools in favor of new code-generation tool - weaver, see https://github.com/open-telemetry/build-tools/issues/322 for the details.
Build-tools are compatible with the latest version of semantic-convention (1.28.0), but might become incompatible with the future versions of semantic-conventions. New features (such as event definition) are added to the weaver only and won't be supported by the build-tools.
Migration steps are documented here along with some non-normative guidelines on the code organization and artifact stability.
Looking for volunteers and happy to help or provide any additional details.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the migration steps in the linked semantic-conventions code-generation documentation and the referenced build-tools issue. Then locate this repository's semantic-convention code-generation integration and identify what currently depends on build-tools. Done means migrating that integration to weaver while preserving the repository's generated artifacts and following the documented organization and stability guidelines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100