open-telemetry / open-telemetry/opentelemetry-python
Follow up to OpenSSF questionnaire
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
I identified some improvements that can be made as follow ups to https://github.com/open-telemetry/opentelemetry-python/issues/4717 and running through the OpenSSF questionnaire
- Suggested: document a test policy for new major features in CONTRIBUTING.md. We already do this in practice but we should have a policy written down somewhere
- Suggested: add dynamic code analysis tool like https://github.com/google/oss-fuzz
- Suggested: add code coverage checks to CI and check that "test suite cover most (or ideally all) the code branches, input fields, and functionality"
Once these are fixed, the questionnaire should be updated https://www.bestpractices.dev/en/projects/11060
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 with CONTRIBUTING.md and the repository's CI configuration, then review the linked OpenSSF questionnaire and issue #4717. The work is done when the test policy is documented, dynamic analysis and coverage checks are added to CI, and the questionnaire is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, documentation, security, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100