-
Notifications
You must be signed in to change notification settings - Fork 37
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
License text in the sources #3
Comments
Do you require the license text only in the git repository as a LICENSE.txt file or also as part of the gem bundle? I assume I don't need the full Apache 2.0 license, but simply the extract that can be found at the bottom of this project's README. Is that correct? |
I asked at the Fedora legal mailing list and answer is:
Here is the detailed answer: If I could try to interpret the answer: "the must" for Fedora is the full LICENSE file in the repository (then it can be packaged without problems). "The must" for upstream projects is the full license text in the gems. |
I was reading through the Apace 2.0 license, and in the appendix, it has the following section:
The given boilerplate is:
It would appear that this is the preferred text to include in my license.txt project file, no? If not, where is the copy-right stated? |
License and copyright are two different things. The copyright can be incorporated into files themselves (as comments or in documentation). The main problem here is the Section 4a about redistribution, where the license text itself is needed. For packaging I can pick the license text from the jmespath.rb repository. Although it may be better to follow legal experts advice and have the full text in the gem. |
Thank you for your patience. I've added the license to the project and the gem file. I went ahead and cut a 1.0.2 release with the file bundled. |
Hello,
could you provide license text in the sources?
I'm packaging jmespath gem for Fedora, and there are some information about licensing in guidelines:
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#License_Text
Apache 2.0 license:
http://www.apache.org/licenses/LICENSE-2.0.txt
The text was updated successfully, but these errors were encountered: