Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add missing license to gemspecs #1

Open
bf4 opened this issue Jul 18, 2013 · 2 comments
Open

Add missing license to gemspecs #1

bf4 opened this issue Jul 18, 2013 · 2 comments
Assignees

Comments

@bf4
Copy link
Owner

bf4 commented Jul 18, 2013

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:

  1. From the stats I've collected, find all gems without a license specified in the gemspec
  2. Map the result to a list of github 'username/reponame' guessed from urls specified in the gemspec
  3. Remove from the list any gems with a username on the blacklist
  4. Remove from the list any gems that I've already processed (whether I created an issue or not)
  5. Check all the open and closed issues for the word 'license' or 'licence'
  6. If not found, create an issue 'License missing from gemspec'
  7. 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

@ghost ghost assigned bf4 Jul 18, 2013
This was referenced Jul 18, 2013
This was referenced Nov 26, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants