[
https://issues.apache.org/jira/browse/HUDI-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17054532#comment-17054532
]
Vinoth Chandar edited comment on HUDI-662 at 3/8/20, 10:37 PM:
---------------------------------------------------------------
cc [~vinoyang] [~smarthi] This seems like a model we can emulate .. NOTICE is
supposed to be for transitively carrying over all the NOTICEs from the
dependencies..
Pasting from ASLV2
{code}
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
{code}
is our NOTICE file complete in these respects? Previously, [~vbalaji] was
trying to automate this by concatenating all the NOTICE files from dependencies
(you may remember the super long NOTICE file that we kept trimming and
expanding)
We have a scripts/releases/generate_notice.sh which should ideally provide a
concatenated NOTICE from all jars.. Not sure if its working as intended.. But
this seems like a good model to try..
In short,
- list all the bundled dependencies and source dependencies with licenses in
LICENSE
- Fix the script and generate a NOTICE based on the dependencies's NOTICE
files.
Is it worth raising a LEGAL JIRA to confirm that maven central distribution of
these bundles do count as a binary distribution and thus we need to attribute
them?
was (Author: vc):
cc [~vinoyang] [~smarthi] This seems like a model we can emulate .. NOTICE is
supposed to be for transitively carrying over all the NOTICEs from the
dependencies..
Pasting from ASLV2
{code}
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
{code}
is our NOTICE file complete in these respects? Previously, [~vbalaji] was
trying to automate this by concatenating all the NOTICE files from dependencies
(you may remember the super long NOTICE file that we kept trimming and
expanding)
> Attribute binary dependencies that are included in the bundle jars
> ------------------------------------------------------------------
>
> Key: HUDI-662
> URL: https://issues.apache.org/jira/browse/HUDI-662
> Project: Apache Hudi (incubating)
> Issue Type: Bug
> Components: Release & Administrative
> Reporter: Vinoth Chandar
> Assignee: Vinoth Chandar
> Priority: Blocker
> Fix For: 0.5.2
>
>
> https://www.apache.org/legal/resolved.html is the comprehensive guide here.
> http://www.apache.org/dev/licensing-howto.html is the comprehensive guide
> here.
> Previously, we asked about some specific dependencies here
> https://issues.apache.org/jira/browse/LEGAL-461
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
