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

License text in the sources #3

Closed
valtri opened this issue Nov 29, 2014 · 5 comments
Closed

License text in the sources #3

valtri opened this issue Nov 29, 2014 · 5 comments

Comments

@valtri
Copy link
Contributor

valtri commented Nov 29, 2014

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

@trevorrowe
Copy link
Contributor

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?

@valtri
Copy link
Contributor Author

valtri commented Dec 2, 2014

I asked at the Fedora legal mailing list and answer is:

  1. the license text is needed also in gem file
  2. the full copy of the license is needed

Here is the detailed answer:
https://lists.fedoraproject.org/pipermail/legal/2014-December/002529.html

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.

@trevorrowe
Copy link
Contributor

I was reading through the Apace 2.0 license, and in the appendix, it has the following section:

 APPENDIX: How to apply the Apache License to your work.

  To apply the Apache License to your work, attach the following
  boilerplate notice, with the fields enclosed by brackets "[]"
  replaced with your own identifying information. (Don't include
  the brackets!)  The text should be enclosed in the appropriate
  comment syntax for the file format. We also recommend that a
  file or class name and description of purpose be included on the
  same "printed page" as the copyright notice for easier
  identification within third-party archives.

The given boilerplate is:

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

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?

@valtri
Copy link
Contributor Author

valtri commented Dec 4, 2014

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.

@trevorrowe
Copy link
Contributor

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.

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