Clarify in license when code is read for reference how protections apply
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.3k
- Forks
- 808
- PR merge metrics
- No merged PRs in 30d
Description
First the reason for this: https://nothings.org/stb/stb_opus.html
As it stands, it’s hard to make other implementations of Opus decoder that could be made with a more permissive license so that it could be more easily embedded in other libraries.
As such, Opus adoption is slow in many areas - in gamedevelopment in particular, many closed platforms are very strict on the licenses that software (games) that runs in such platforms and this makes it hard for open source projects which use open source libraries.
It would be nice if a specific clause could exist in a way people could read the code to construct their own implementation of the decoder.
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
Start by reviewing the project's license and the linked stb_opus.html discussion to understand the requested treatment of code read for reference. Determine whether a license clause can address constructing an independent Opus decoder, with the wording and its legal implications resolved before considering the issue done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100