Ambiguous gempsec "licenses" attribute
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 4k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 81
Description
The current spec for Gems lead to some ambiguities in the license documentation.
The spec suggest to use "licenses" attribute for multiple licenses. https://guides.rubygems.org/specification-reference/#licenseslicenses ....yet there is nothing that says if all the licenses would apply or if this is a choice among the list of licenses. Therefore having this list of licenses is ambiguous:
- GPL-2.0
- MIT
could either meanGPL-2.0 or MITorGPL-2.0 and MITand these are two very different licenses.
My suggestion would be to deprecate the "licenses" in favor of the single "license" string and allow to use SPDX license expressions in the "license" field. These are not ambiguous: GPL-2.0 and MIT is an example of such expression.
Tell me how I can help to make this happen.
I will abide by the code of conduct.
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 the Gems specification reference linked in the issue, focusing on the license and licenses attributes and the ambiguity around multiple licenses. The issue is done when the project agrees on the intended semantics and documents an actionable specification change, including whether SPDX expressions are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100