Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Date: Wed, 5 Aug 2015 13:30:05 +0000 (UTC)
From: "Sam Ruby (JIRA)" <jira@apache.org>
To: legal-discuss@apache.org
Message-ID: <JIRA.12850296.1438271568000.377541.1438781405272@Atlassian.JIRA>
In-Reply-To: <JIRA.12850296.1438271568000@Atlassian.JIRA>
References: <JIRA.12850296.1438271568000@Atlassian.JIRA>
 <JIRA.12850296.1438271568689@arcas>
Subject: [jira] [Assigned] (LEGAL-222) Can HBase redistribute JRuby?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LEGAL-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sam Ruby reassigned LEGAL-222:
------------------------------

    Assignee: Sam Ruby

I would agree that [BSDL|https://github.com/ruby/ruby/blob/trunk/BSDL], and therefore the current Ruby License, is Category A.  Given clause 3A in the [1.92 license text|http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/tags/v1_9_2_320/COPYING?view=markup], I see no issue with this license being classified as category B.

I'll assign this to me, but Jim's on vacation, and I'm reticent to close this without either his OK or giving others ample time to comment.  That being said, if you have released before, and this is holding up a release, I would suggest proceeding and checking back before making the *next* release after that one.

As to your two questions: 

* I would agree that a JAR file is fine.

* I'm not sure what you are referring to with regards to "exemptions".  If you are referring to [LEGAL|http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/tags/v1_9_2_320/LEGAL?view=markup], then only the portions of that file that are relevant to your distribution would be necessary (i.e., it is OK to drop mention of files that you don't distribute).

> Can HBase redistribute JRuby?
> -----------------------------
>
>                 Key: LEGAL-222
>                 URL: https://issues.apache.org/jira/browse/LEGAL-222
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Sean Busbey
>            Assignee: Sam Ruby
>
> HBase currently relies on an older version of JRuby (1.6.8) that we redistribute via the jruby-complete jar made by that project.
> While cleaning up our license notifications (HBASE-14085) I've been verifying that we have any supplemental licensing info from included dependencies (that is, stuff beyond the license listed in a pom).
> The overall licensing for JRuby is CPL 1.0 and it mentions bundling some other works under a combination of licenses that are all categorized as various degrees of fine for inclusion by an ASF project ([ref jruby 1.6.8 COPYING information|https://github.com/jruby/jruby/blob/1.6.8/COPYING]).
> It also includes the ruby language files from MRI ruby 1.8 and 1.9 under "The Ruby License" ([ref jruby 1.6.8 LICENSE.RUBY details|https://github.com/jruby/jruby/blob/1.6.8/LICENSE.RUBY] and referenced no-op [LEGAL|https://github.com/jruby/jruby/blob/1.6.8/LEGAL]). These files are needed for jruby to function, so I can't e.g. excise them from the version we redistribute.
> The legal FAQ mentions that it's okay for ruby-implemented projects to have dependencies that are under the Ruby License, but it doesn't categorize the license generally or state if it's okay to redistribute.
> Can we redistribute this jar?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org