Skip to content
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

GPLv2 license is obsolete and problematic in the Ruby ecosystem. #2

Open
nomoon opened this issue Jul 12, 2017 · 1 comment
Open

GPLv2 license is obsolete and problematic in the Ruby ecosystem. #2

nomoon opened this issue Jul 12, 2017 · 1 comment

Comments

@nomoon
Copy link

nomoon commented Jul 12, 2017

Following on to #1

It looks like this gem is currently only released under the terms of the obsolete copyleft GNU General Public License v2. This suggests that the gem cannot be combined with any Apache-licensed software (since the Apache 2.0 license is only compatible with the GPL v3), and also that any software that incorporates the gem must only be redistributed under the terms of the GPL v2. Since the vast majority of gems are released under permissive licenses like Ruby's own license, MIT (the most common license on Rubygems by far), BSD, Apache, and Unlicense, it may come as a surprise to some developers to find that they are bound to redistribute their code in a copyleft license that has also been obsolete since 2007.

This also means that any use of https://github.com/flori/mize or other gems that depend on it such as https://github.com/flori/amatch would enforce the GPLv2 on developers that intend to redistribute their code.

Please consider updating the license or dual-licensing the software. https://choosealicense.com/ can assist with deciding on a new one, and http://guides.rubygems.org/specification-reference/#license= provides useful information as well.

@rubyFeedback
Copy link

(1) It is not obsolete at all.
(2) The GPLv2 is not "viral" in regards to what is insinuated here. If this were the case, any read-file functionality
on a non-GPL file as such would be a violation, as would be system() in ruby for GPL-based software. This is
evidently incorrect. Otherwise the linux kernel could never be used in a BSD_centric environment.

I agree on the part that BSD licence may be more convenient for many projects, or LGPL. GPL, be it v2 or
v3, is always a trade-off. As a strict licence it will ensure guaranteed right of re-distribution, which the
BSD variants don't. I use BSD and GPLv2 just fine for my own ruby code; I don't use GPLv3. Note that
the claim that the apache licence is incompatible with GPLv2 is propaganda, as is your claim that the
"Unlicense" is popular in the ruby gem ecosystem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants