[ 
https://issues.apache.org/jira/browse/CALCITE-6098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807449#comment-17807449
 ] 

Julian Hyde commented on CALCITE-6098:
--------------------------------------

It is very likely the case that I copied from ORC. I remember looking at ORC's 
site and reading their .md source code before settling on Jekyll for Calcite. I 
don't remember whether I let Jekyll create the initial site or copied from ORC.

Did we just copy examples/skeleton files? If so, I don't think we need to add 
the Jekyll license to our NOTICE. It is analogous to me copying a Java "Hello 
world" program to start my project: it is so simple that there is only one way 
to do it, and since no creativity is required there is [nothing to 
copyright|https://www.linkedin.com/pulse/hello-world-copyrighted-ido-tuchman/].

> Remove mentions of Jekyll from LICENSE and NOTICE files
> -------------------------------------------------------
>
>                 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)

Reply via email to