On Wed, Jun 8, 2011 at 9:42 AM, Krum B. [email protected]
I am interested in the general way that a Ruby/Rails developer approaches
this problem. Okay, she finds some gem that is needed for her project,
executes “gem install”, no agreements are asked, and the gem is installed
successfully. But has she checked the License.txt file before that ? I mean,
do Rails developers have this habit ? Because if you just install blindly
thousands of gems… at one point in time you’ll be simply lost in all these
Since a) Gems are delivered as plain ol’ Ruby scripts, and b) Ruby is
highly dynamic, you’ll quickly notice that pretty much all gems are
under one form of OSS license or another. Which means “licensing is
not a big deal”.
I’m guessing you are hailing from an enterprise-y / corporate
background (I’m asking because that’s where licensing question are the
That being said, I believe that it will be useful to have a way
(an optional way, of course) to enforce agreement during gem install.
Why? You did research the libraries you need, and made sure that they
meet your requirements long before you issued the install command,
Also: “optional” and “enforcement” don’t belong together. Either it’s
a user-configurable setting (which would have to be off by default,
otherwise you break deployment scripts), or it’s an
author-configurable setting which isn’t really optional from the
A method of solution is perfect if we can forsee from the start,
and even prove, that following that method we shall attain our aim.