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

data/list.txt and test/tests.txt licenses #137

Closed
voxik opened this issue Apr 7, 2017 · 3 comments
Closed

data/list.txt and test/tests.txt licenses #137

voxik opened this issue Apr 7, 2017 · 3 comments
Assignees

Comments

@voxik
Copy link

voxik commented Apr 7, 2017

The data/list.txt header states the file is licensed under Mozilla Public License, v. 2.0 and test/tests.txt refers to public domain. Shouldn't this be mentioned somewhere along other license information in README and in .gemspec "licenses" field? Would you mind to include the MPLv2 license file?

Since your gem is going to be require by RoR 5.1, I am trying to package it for Fedora and Fedora Guidelines [1] encourages me to ask you for this.

Thx for your help.

@weppos
Copy link
Owner

weppos commented Apr 9, 2017

The Gemspec licenses section refers to the license adopted for the lib (or at least this is my current interpretation), and in fact is correctly contains MIT that is the license adopted for this project.

The "Mozilla Public License" applies exclusively to the PSL (the list itself).

I can add a mention to the README. Would that be sufficient for you?

@weppos weppos self-assigned this Apr 9, 2017
@voxik
Copy link
Author

voxik commented Apr 9, 2017

In RPM world, the "license" field lists all licenses of all files included in the package. I can't see any reason why it should be different for gems. Unfortunately there is no governance body which could provide answer for the gem case, so I leave it up to you.

But listing the licenses in README would definitely help. Thx.

@weppos weppos closed this as completed in 16a502f Jun 28, 2017
@weppos
Copy link
Owner

weppos commented Jun 28, 2017

Sorry for the delay. I added the info to the README.

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

No branches or pull requests

2 participants