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.
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.
Jason Hsu, Rubyist wrote in post #1124297:
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.
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?
When I want something less passive but still open and that takes contributors into account: http://www.apache.org/licenses/LICENSE-2.0
I use the MIT license as well. It's common enough that users will recognise it immediately, and covers the basics while being succinct.
Jason Hsu, Rubyist wrote in post #1124349: