open-telemetry / open-telemetry/opentelemetry-python
Document all entry points somewhere
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
We should publicly document which entry_points we load stuff from -- what their names are and what types of things we expect the entry_point to load in.
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 locating the Python packaging configuration and the code that loads entry points. Inventory the entry point names and the expected types of loaded objects, then document them publicly. Done means every loaded entry point is listed with its name and expected type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100