What license do you use for your Ruby gems?

[Jason Hsu, Rubyist]

I have created two Ruby gems (dvi_scrape and bsf_scrape), and I'm planning on creating a few more.

What license should I be using for my Ruby gems?  I'm creating these gems on my own and not on behalf of any particular organization.

[Robert Walker]

Jason Hsu, Rubyist wrote in post #1124297:

That's really up to you AFAIK. I typically use the MIT license on my
stuff, but choosing a license can be a fairly personal choice. It
depends on what you're trying to protect, or not protect, whatever the
case may be.

--
Posted via http://www.ruby-forum.com/.

[Jason Hsu, Rubyist]

On Friday, October 11, 2013 7:21:57 PM UTC-5, Ruby-Forum.com User wrote:

That's really up to you AFAIK. I typically use the MIT license on my
stuff, but choosing a license can be a fairly personal choice. It
depends on what you're trying to protect, or not protect, whatever the
case may be.

Why do you use the MIT license?  Under what circumstances would you use something else?

[Jordon Bedwell]

On Fri, Oct 11, 2013 at 9:54 PM, Jason Hsu, Rubyist
<jhsu8...@gmail.com> wrote:
> Why do you use the MIT license? Under what circumstances would you use
> something else?

When I want something less passive but still open and that takes
contributors into account: http://www.apache.org/licenses/LICENSE-2.0

[Joel Pearson]

I use the MIT license as well. It's common enough that users will
recognise it immediately, and covers the basics while being succinct.

[Robert Walker]

Jason Hsu, Rubyist wrote in post #1124349:

I think if you read through the short and simple MIT license it would
become very clear under what circumstances you would want to use
something else.

For example if I wanted to prevent others from directly making money
from my software. MIT specifically allows that.