open-telemetry / open-telemetry/sig-developer-experience
Ruby Developer Experience Survey
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 7
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 3
Description
- differences from upstream spec:
- discrepancies - why?
- extra convenience
- most requested features
- API
- SDK
- Instrumentations/semantic conventions
- things to consider from other telemetry projects
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by reviewing the Ruby differences from the upstream specification and comparing other telemetry projects, then document discrepancies, requested API/SDK/instrumentation features, and relevant semantic conventions as the completed survey.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100