apache / incubator-fury

A blazingly fast multi-language serialization framework powered by JIT and zero-copy.

Home Page:https://fury.apache.org/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Discuss][License] do wen need to move license content from NOTICE to LICENSE file

chaokunyang opened this issue · comments

Is your feature request related to a problem? Please describe.

Fury borrowed some code from spark/guava/v8/etc. Currently we add the license of those project in NOTICE file.

Projects flink/pytorch use this method.

Other projects such as spark/arrow/etc all put license into LICENSE file.

Both ways look good to me, @tisonkun @pjfanning do you have any suggestions?

Additional context

#1440

It is my understanding that 3rd party licenses should be mentioned in our LICENSE and notices in those 3rd party projects should be mentioned in our NOTICE file. Not every Apache project seems to do this - so I could be wrong. It might be better to ask this on the general@incubator.apache.org list or something like the ASF legal-discuss mailing list.

It is my understanding that 3rd party licenses should be mentioned in our LICENSE and notices in those 3rd party projects should be mentioned in our NOTICE file. Not every Apache project seems to do this - so I could be wrong. It might be better to ask this on the general@incubator.apache.org list or something like the ASF legal-discuss mailing list.

It's my understanding too. Maybe both are legal, but mention 3rd party license in our license and mention notice in our notice reduce the confusion to people since its more intuitive