[
https://issues.apache.org/jira/browse/CALCITE-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stamatis Zampetakis updated CALCITE-6098:
-----------------------------------------
Summary: Update LICENSE and NOTICE for Jekyll website template (was:
Remove mentions of Jekyll from LICENSE and NOTICE files)
> Update LICENSE and NOTICE for Jekyll website template
> -----------------------------------------------------
>
> Key: CALCITE-6098
> URL: https://issues.apache.org/jira/browse/CALCITE-6098
> Project: Calcite
> Issue Type: Task
> Affects Versions: 1.36.0
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Labels: pull-request-available
>
> The NOTICE file contains the following statement:
> {noformat}
> The web site includes files generated by Jekyll.{noformat}
>
> However, there is nothing in the [LICENSE of Jekyll
> |https://github.com/jekyll/jekyll/blob/3f3a283018a976da11a0bfcc13a20d43d37ee29f/LICENSE]
> that requires such attribution.
> According to the instructions of composing the [NOTICE
> file|https://infra.apache.org/licensing-howto.html#mod-notice] for ASF
> projects we shouldn't add anything in there that is not *legally* required.
> Moreover the generated files are not necessary licensed under the same
> LICENSE with the generator.
> JavaCC, ANTLR, and lots of other source generators use a variety of licenses
> but the generated output is not licensed under the same terms. For instance,
> Calcite uses JavaCC, which is licensed under
> [BSD-3|https://github.com/javacc/javacc/blob/master/LICENSE] but both the
> grammar as well as the generated .java files are AL2.
> As long as we are not packaging bits of Jekyll in Calcite there is no need to
> add explicit mentions in LICENSE or NOTICE files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
