open-telemetry / open-telemetry/community
Add guidelines about allowed licenses for dependencies
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 314
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 13
Description
The Copyright section in the CONTRIBUTING doc talks about licenses allowed for contributed code. In addition to that we need to explicitly call out the exact list of licenses allowed for dependencies to make it clear for all contributors.
It is going to be the same list. We only allow dependencies that are no-less permissive than Apache license. Borrowing this nice image from Wikipedia which clearly shows what can be combined with Apache 2.0 to result in Apache 2.0 (incoming arrows are fine, outgoing are not):
This issue came up here: https://github.com/open-telemetry/opentelemetry-js-contrib/pull/348
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
Open the CONTRIBUTING document and read its Copyright section first. Add the exact dependency-license list described in the issue, using the same list allowed for contributed code and the Apache 2.0 compatibility guidance. Done means contributors can clearly identify which dependency licenses are permitted.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100