License missing from gemspec #9

Closed
bf4 opened this Issue Nov 1, 2013 · 2 comments

Comments

Projects
None yet
2 participants
@bf4

bf4 commented Nov 1, 2013

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the gemspec of your last release.

via e.g.

spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']

Including a license in your gemspec is an easy way for rubygems.org and other tools to check how your gem is licensed. As you can imagine, scanning your repository for a LICENSE file or parsing the README, and then attempting to identify the license or licenses is much more difficult and more error prone. So, even for projects that already specify a license, including a license in your gemspec is a good practice. See, for example, how rubygems.org uses the gemspec to display the rails gem license.

There is even a License Finder gem to help companies/individuals ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec. This is an important enough issue that even Bundler now generates gems with a default 'MIT' license.

I hope you'll consider specifying a license in your gemspec. If not, please just close the issue with a nice message. In either case, I'll follow up. Thanks for your time!

Appendix:

If you need help choosing a license (sorry, I haven't checked your readme or looked for a license file), GitHub has created a license picker tool. Code without a license specified defaults to 'All rights reserved'-- denying others all rights to use of the code.
Here's a list of the license names I've found and their frequencies

p.s. In case you're wondering how I found you and why I made this issue, it's because I'm collecting stats on gems (I was originally looking for download data) and decided to collect license metadata,too, and make issues for gemspecs not specifying a license as a public service :). See the previous link or my blog post about this project for more information.

philr added a commit that referenced this issue Nov 3, 2013

@philr

This comment has been minimized.

Show comment
Hide comment
@philr

philr Nov 3, 2013

Member

I have added the license option to the gemspec file in the (older but still maintained) 0.3 branch. The license option was already specified in the master branch gemspec file and included in releases from version 1.0.0 onwards.

Thanks for letting me know.

Member

philr commented Nov 3, 2013

I have added the license option to the gemspec file in the (older but still maintained) 0.3 branch. The license option was already specified in the master branch gemspec file and included in releases from version 1.0.0 onwards.

Thanks for letting me know.

@philr philr closed this Nov 3, 2013

@bf4

This comment has been minimized.

Show comment
Hide comment
@bf4

bf4 Nov 4, 2013

Ah, I see. Thanks for following up :)

bf4 commented Nov 4, 2013

Ah, I see. Thanks for following up :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment