open-telemetry / open-telemetry/sig-developer-experience
Rust 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
The issue mentions no files, tests, or entry points. Start by reviewing the listed areas: upstream-spec differences, requested API and SDK features, instrumentations and semantic conventions, and related telemetry projects. Done means producing a Rust developer experience survey covering those topics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100