[
https://issues.apache.org/jira/browse/QUARKS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220425#comment-15220425
]
Kathy Saunders edited comment on QUARKS-34 at 3/31/16 6:48 PM:
---------------------------------------------------------------
I wanted to add more context to what I did so far on license and Notices.
I found conflicting information about what needs to be represented in the
Notices file and what does not. I took the conservative approach and put
everything in my patch that may need a notice. I looked at several other
Apache projects and modeled my updates after some of those. I did find
differences between projects. I also think that a license and notice required
for a release will be different than that required for the source code, so we
need to come up with a strategy for those two types of licenses.
Here's what I did
- Walked through the entire tree of the Quarks repository, looking for third
party code.
- For each unique piece of code, look into the license and notices. This
includes projects shipped within other projects. For example, Scala is present
in the Kafka distribution, so I included Scala.
For each non-Quarks sub-component, took the following actions:
- If Apache license and nothing specific in the notices file, then do nothing.
I don't think we need to call those out in the Quarks license or Notices.
- If Apache license, and there are specific notices in the Notice file of the
sub-component, I copied them into the Quarks Notices file. It's not clear
whether this is required, as there is differing advice on this on Apache web
pages, but it seems like the most conservative approach. An example of this is
the notice for Apache httpcore:
Just now
I wanted to add more context to what I did so far on license and Notices.
I found conflicting information about what needs to be represented in the
Notices file and what does not. I took the conservative approach and put
everything in my patch that may need a notice. I looked at several other Apache
projects and modeled my updates after some of those. I did find differences
between projects. I also think that a license and notice required for a release
will be different than that required for the source code, so we need to come up
with a strategy for those two types of licenses.
Here's what I did
Walked through the entire tree of the Quarks repository, looking for third
party code.
For each unique piece of code, look into the license and notices. This
includes projects shipped within other projects. For example, Scala is present
in the Kafka distribution, so I included Scala.
For each non-Quarks sub-component, took the following actions:
If Apache license and nothing specific in the notices file, then do
nothing. I don't think we need to call those out in the Quarks license or
Notices.
If Apache license, and there are specific notices in the Notice file of the
sub-component, I copied them into the Quarks Notices file. It's not clear
whether this is required, as there is differing advice on this on Apache web
pages, but it seems like the most conservative approach. An example of this is
the notice for Apache httpcore:
This project contains annotations derived from JCIP-ANNOTATIONS
Copyright (c) 2005 Brian Goetz and Tim Peierls. See http://www.jcip.net
- If another class-A license, then copy it into the license file. Not sure
this is required, but I saw examples like this in other places. I did this
with Scala.
- If a Class-B license, add notes in the Notices file pointing to the source
code. From what I read, this can be put in Notices or README, but the examples
I found had it in the NOTICES. Here's an example:
The following components are provided under the Eclipse Public License 1.0. See
project link for details.
(Eclipse Public License - Version 1.0) iot-java Jar
(https://github.com/ibm-messaging/iot-java)
Summary: I think we need to decide how we want to handle licenses for the
source vs. future releases. I'm also very open to other opinions about whether
all of the notices are required and which files they should be in.
was (Author: kssaunders):
I wanted to add more context to what I did so far on license and Notices.
I found conflicting information about what needs to be represented in the
Notices file and what does not. I took the conservative approach and put
everything in my patch that may need a notice. I looked at several other
Apache projects and modeled my updates after some of those. I did find
differences between projects. I also think that a license and notice required
for a release will be different than that required for the source code, so we
need to come up with a strategy for those two types of licenses.
Here's what I did
- Walked through the entire tree of the Quarks repository, looking for third
party code.
- For each unique piece of code, look into the license and notices. This
includes projects shipped within other projects. For example, Scala is present
in the Kafka distribution, so I included Scala.
For each non-Quarks sub-component, took the following actions:
- If Apache license and nothing specific in the notices file, then do nothing.
I don't think we need to call those out in the Quarks license or Notices.
- If Apache license, and there are specific notices in the Notice file of the
sub-component, I copied them into the Quarks Notices file. It's not clear
whether this is required, as there is differing advice on this on Apache web
pages, but it seems like the most conservative approach. An example of this is
the notice for Apache httpcore:
- If the license is Apache and there is nothing special in the notices file
> Work on License and Notices files for Quarks
> --------------------------------------------
>
> Key: QUARKS-34
> URL: https://issues.apache.org/jira/browse/QUARKS-34
> Project: Quarks
> Issue Type: Task
> Components: Miscellaneous
> Reporter: Kathy Saunders
> Assignee: Kathy Saunders
> Labels: legal
>
> Update the notices file wit the IBM copyright so the source file copyrights
> can be changed. Review the included software and update the license or
> notices as appropriate.
> http://www.apache.org/dev/licensing-howto.html
> http://apache.org/legal/resolved.html#criteria
> http://www.apache.org/legal/src-headers.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
