Add missing license to gemspecs
bf4 opened this issue · 2 comments
Some companies will only use gems with a certain license.
The canonical and easy way to check is via the gemspec
via e.g.
spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']
There is even a License Finder to help companies ensure all gems they use
meet their licensing needs. This tool depends on license information being available in the gemspec.
Including a license in your gemspec is a good practice, in any case.
If you need help choosing a license, github has created a license picker tool
I've written a blog post, as well: Make the world a better place; put a license in your gemspec
This is how I create issues:
- From the stats I've collected, find all gems without a license specified in the gemspec
- Map the result to a list of github 'username/reponame' guessed from urls specified in the gemspec
- Remove from the list any gems with a username on the blacklist
- Remove from the list any gems that I've already processed (whether I created an issue or not)
- Check all the open and closed issues for the word 'license' or 'licence'
- If not found, create an issue 'License missing from gemspec'
- Update my list of processed gems so the same repo is never processed twice
I'm doing this via a script as a public service. :) So far, it's going pretty well. Apparently, I was mentioned on Ruby5.
also see
- surfacing licenses on rubygems.org - which includes a reference to most of the issues I created before creating this issue and repo.
- Rubygems guide recommends including a license in your gemspec
- adding a license to bundler-generated gems, defaults to 'MIT'
- Rails plugin new defaults license to MIT
"As you can image, scanning your repository for a LICENSE file or parsing the README"