-
-
Notifications
You must be signed in to change notification settings - Fork 926
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
Display license info for all gems #363
Comments
+1 Within most corporations, government institutions, foundations, etc., there is an expectation that we keep our licenses in order. Rubygems could really make our lives easier by providing this kind of information. |
@imkmf You should be able to mute notifications on this is. I thought it would be a nice way to collect the results of this project. But, if it really is a problem, of course I'll take that link out of the issue. |
All future issues will now reference bf4/gemproject#1 so this issue will quiet down |
This increases the discoverability of what license this gem uses. See rubygems/rubygems.org#363 for more info.
This increases the discoverability of what license this gem uses. See rubygems/rubygems.org#363 for more info.
This increases the discoverability of what license this gem uses. See rubygems/rubygems.org#363 or [this blog post](http://www.benjaminfleischer.com/2013/07/12/make-the-world-a-better-place-put-a-license-in-your-gemspec/) for more info.
This increases the discoverability of what license this gem uses. See rubygems/rubygems.org#363 or [this blog post](http://www.benjaminfleischer.com/2013/07/12/make-the-world-a-better-place-put-a-license-in-your-gemspec/) for more info.
So that tools like LicenseFinder can check licenses across gems better. see rubygems/rubygems.org#363 too
Licenses are in now. |
so that tools like LicenseFinder can check licenses across gems better. See rubygems/rubygems.org#363 too
From this thread: http://rubyforge.org/pipermail/rubygems-developers/2011-October/006881.html
We'll already have to go through every version to get the size data in #310, could do both at the same time here.
The text was updated successfully, but these errors were encountered: