[jira] [Commented] (STREAMS-664) Fix LICENSE
[
https://issues.apache.org/jira/browse/STREAMS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150328#comment-17150328
]
Steve Blackmon commented on STREAMS-664:
This was helpful. I believe because nothing outside the project AS 2.0 source
files are bundled in the source release, no changes to the root LICENSE file
are needed, but we will need a separate LICENSE for the binary release.
I think the next action here will be to create a LICENSE file residing in
streams-dist which will be packaged into the root of the binary/bytecode
release, along with the text of all bundled dependency licenses, and refer to
each in turn.
The license texts for direct and transitive dependencies can be dynamically
retrieved and/or updated by org.codehaus.mojo:license-maven-plugin. We'll need
to update our release manager instructions per STREAMS-593 to run this step
before any release, and describe how to edit the streams-dist/LICENSE based on
whether any new license files appear or disappear, confirming that new licenses
are not category-X in the process.
> Fix LICENSE
> ---
>
> Key: STREAMS-664
> URL: https://issues.apache.org/jira/browse/STREAMS-664
> Project: Streams
> Issue Type: Task
>Reporter: Steve Blackmon
>Assignee: Steve Blackmon
>Priority: Major
>
> Per email from Justin to dev list 4/11/2020
> {color:#d5dade}- There seems to be a few things missing from LICENSE{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (STREAMS-664) Fix LICENSE
[
https://issues.apache.org/jira/browse/STREAMS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149731#comment-17149731
]
Justin Mclean commented on STREAMS-664:
---
See https://www.apache.org/dev/licensing-howto.html on how to do this. I would
not suggest you copy Spark, last I looked it was a poor example to follow.
Dependancies should not be listed in LICENSE only what is actually bundled in
the release artefact. This means that the LICENSE and NOTICE files are often
different for both the source release and the binary release.
> Fix LICENSE
> ---
>
> Key: STREAMS-664
> URL: https://issues.apache.org/jira/browse/STREAMS-664
> Project: Streams
> Issue Type: Task
>Reporter: Steve Blackmon
>Assignee: Steve Blackmon
>Priority: Major
>
> Per email from Justin to dev list 4/11/2020
> {color:#d5dade}- There seems to be a few things missing from LICENSE{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (STREAMS-664) Fix LICENSE
[
https://issues.apache.org/jira/browse/STREAMS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17149618#comment-17149618
]
Steve Blackmon commented on STREAMS-664:
I took a look at LICENSE files of several apache TLPs peripheral to Streams.
Accumulo, Any23, Flink, Jena, Juneau, Spark, and Zeppelin.
Some of these include additional statements below the text of the main Apache
License, while others do not.
>From research on lists.apache.org, it seems the main reason LICENSE would need
>additional details is if source code from other projects / license types has
>been copy/pasted into source repo, or is otherwise packaged in the binary
>release, except for as a maven dependency.
Even if we begin shipping a binary artifact based on the Uber-jar produced by
building streams-dist I can't think of any additional disclosures that would
need to go under LICENSE as all source code is original property of Apache
Streams and our binary won't include anything aside from compiled streams jars
and transitive dependencies whose license details will be covered in detail
under NOTICE.
Can anyone think of a reason we'd need to augment our LICENSE? Am I confused
in my understanding of this at all?
> Fix LICENSE
> ---
>
> Key: STREAMS-664
> URL: https://issues.apache.org/jira/browse/STREAMS-664
> Project: Streams
> Issue Type: Task
>Reporter: Steve Blackmon
>Priority: Major
>
> Per email from Justin to dev list 4/11/2020
> {color:#d5dade}- There seems to be a few things missing from LICENSE{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
