[
https://issues.apache.org/jira/browse/QUARKS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220425#comment-15220425
]
Kathy Saunders commented on QUARKS-34:
--------------------------------------
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)