-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
licensing information out of date? #3198
Comments
This isn't a finished job but I made the following changes: * Updated path to the Ruby standard library * Removed Java libraries we no longer use from COPYING * Removed paths to jar files we no longer version * Added a few libraries we do use now * Updated CRuby's license * Added BSDL for CRuby's license I believe we're still missing some Java libraries.
I've made the changes you pointed out plus a few more, but we probably should do a bit more auditing.
Thanks for pointing out how stale this file had become. Hopefully it's a bit closer to being perfect now. Let's work together and see if we can get it there. |
If it's helpful, I can point you towards how the ASF handles these kinds of license notifications and explain how we apply the policy within Apache HBase. (it's how I ended up finding this issue. ;) ) |
One side question, is the JRuby+Truffle library always shipped with JRuby 9k / is it needed to run? Is Truffle from Oracle only licensed as GPL+CPE? I ask because I'm in the process of getting HBase to update our use of JRuby from 1.6.8 to 9k and a GPL dependency will be a blocker for us due to ASF policy. |
Did some quick research
Presuming that second bit is accurate, that should be fine for ASF projects. |
a quick answer regarding truffle. truffle only comes with the jruby-dist artifacts and jruby-jars.gem. all other maven artifacts do not depend or include truffle. jruby-core and jruby-complete to shade some dependencies and rename the asm package names. and then jruby-stdlib comes with a bunch of embedded gems and jars. I know how some maven projects pack those licenses into META-INF somehow. really need to look around a bit. maven itself does have a dedicated license for each single jar which comes with maven-dist tar-ball. I guess something like this is needed for jruby as well. |
COPYING has been updated and Truffle is not part of our dist or main Maven artifacts. For additional licensing info on Truffle we should open a followup issue since it is unrelated to 9.0.1.0. |
I don't think there are any Truffle licensing questions are there? The code in this repo is licensed as per headers. We include some Rubinius and rubinius-api code that is detailed in COPYING. Truffle is not bundled any more, so the actual license of Truffle doesn't matter. We're trying to be very clear about licensing so if there is any doubt at all let us know. |
@chrisseaton great. Then this issue should be enough then... |
It looks like the COPYING details for 9.0.0.0 didn't get updated for the switch to Ruby 2.2.
Presuming the included stuff in lib/ruby/stdlib | lib/ruby/truffle/mri is from a 2.2.0+ version, could we update things appropriately?
Expanding the section to cover the other implementations unders lib/ruby/truffle would also make it easier for downstream users of jruby.
The text was updated successfully, but these errors were encountered: