Re: Should we mention license of other projects in NOTICE file
Hi Justin, Thanks for your replyment, I fixed the license and notice issue in https://github.com/apache/incubator-fury/pull/1507 according to the advice from this thread and PJ. Best Regards, Chaokun Yang On Sun, Apr 14, 2024 at 9:07 AM Justin Mclean wrote: > Hi, > > Any license information goes in LICENSE, not NOTICE. If you include > something that is MIT or BSD licensed, nothing goes in the NOTICE. The > NOTICE file will include re-located copyright statements removed from files > and the contents of any Apache code you have included NOTICE files. > > 1. is BSD licensed, so just put the text in LICENSE > 2. is Apache licensed, It’s a good idea to list that in the LICENSE file > (but not required). It has no NOTICE file, so there is nothing to go in > your NOTICE file. > > Kind Regards, > Justin > > > On 13 Apr 2024, at 3:53 pm, Shawn Yang wrote: > > > > Dear Community, > > > > I'm fixing the license issue of Apache Fury to comply with ASF > requirements > > for the first release for Fury under ASF. > > > > Currently we borrowed some code from other projects such as > > v8-fast-api-calls.h[1] in v8 and Preconditions[2] in guava. We mentioned > > their license in our NOTICE file[3]. > > > > I'm wondering whether we should move those mentions into the LICENSE > file, > > and mention the NOTICE of those projects in our NOTICE instead. > > > > I did some research, but didn't know which is better: > > 1) Projects like flink[4] and pytorch[5] mention the license of other > > projects in the NOTICE file. > > 2) But other projects such as spark[6] and arrow[7] all put the mentions > > into the `LICENSE` file. > > > > Are those both ways legal? Do we have a best practice here? > > > > 1. > > > https://github.com/apache/incubator-fury/blob/main/javascript/packages/hps/src/v8-fast-api-calls.h > > 2. > > > https://github.com/apache/incubator-fury/blob/main/java/fury-core/src/main/java/org/apache/fury/util/Preconditions.java > > 3. https://github.com/apache/incubator-fury/blob/main/NOTICE > > 4. https://github.com/apache/opendal/blob/master/NOTICE > > 5. https://github.com/pytorch/pytorch/blob/main/NOTICE > > 6. https://github.com/apache/spark/blob/master/LICENSE > > 7. tttps://github.com/apache/arrow/blob/main/LICENSE.txt > > > > > > Best regards, > > Chaokun Yang > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: Should we mention license of other projects in NOTICE file
Hi, Any license information goes in LICENSE, not NOTICE. If you include something that is MIT or BSD licensed, nothing goes in the NOTICE. The NOTICE file will include re-located copyright statements removed from files and the contents of any Apache code you have included NOTICE files. 1. is BSD licensed, so just put the text in LICENSE 2. is Apache licensed, It’s a good idea to list that in the LICENSE file (but not required). It has no NOTICE file, so there is nothing to go in your NOTICE file. Kind Regards, Justin > On 13 Apr 2024, at 3:53 pm, Shawn Yang wrote: > > Dear Community, > > I'm fixing the license issue of Apache Fury to comply with ASF requirements > for the first release for Fury under ASF. > > Currently we borrowed some code from other projects such as > v8-fast-api-calls.h[1] in v8 and Preconditions[2] in guava. We mentioned > their license in our NOTICE file[3]. > > I'm wondering whether we should move those mentions into the LICENSE file, > and mention the NOTICE of those projects in our NOTICE instead. > > I did some research, but didn't know which is better: > 1) Projects like flink[4] and pytorch[5] mention the license of other > projects in the NOTICE file. > 2) But other projects such as spark[6] and arrow[7] all put the mentions > into the `LICENSE` file. > > Are those both ways legal? Do we have a best practice here? > > 1. > https://github.com/apache/incubator-fury/blob/main/javascript/packages/hps/src/v8-fast-api-calls.h > 2. > https://github.com/apache/incubator-fury/blob/main/java/fury-core/src/main/java/org/apache/fury/util/Preconditions.java > 3. https://github.com/apache/incubator-fury/blob/main/NOTICE > 4. https://github.com/apache/opendal/blob/master/NOTICE > 5. https://github.com/pytorch/pytorch/blob/main/NOTICE > 6. https://github.com/apache/spark/blob/master/LICENSE > 7. tttps://github.com/apache/arrow/blob/main/LICENSE.txt > > > Best regards, > Chaokun Yang - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Should we mention license of other projects in NOTICE file
Hi John, Thanks for your detailed replyment. I didn't know that flink has a build stage to aggregate license files into the final license. I'll update the license and notice file later. Thanks for your reminder. Best regards, Chaokun Yang On Sat, Apr 13, 2024 at 8:55 PM John D. Ament wrote: > On Sat, Apr 13, 2024 at 1:54 AM Shawn Yang > wrote: > > > Dear Community, > > > > I'm fixing the license issue of Apache Fury to comply with ASF > requirements > > for the first release for Fury under ASF. > > > > Currently we borrowed some code from other projects such as > > v8-fast-api-calls.h[1] in v8 and Preconditions[2] in guava. We mentioned > > their license in our NOTICE file[3]. > > > > I'm wondering whether we should move those mentions into the LICENSE > file, > > and mention the NOTICE of those projects in our NOTICE instead. > > > > The NOTICE file is to be used to aggregate any notices you have. It is > fine to mention that you're using something in your NOTICES file, including > original sources for the content. The licenses those for those files needs > to be in your license file. Here's an example from another project [1] > [2]. > > [1]: https://github.com/apache/daffodil/blob/main/LICENSE#L359-L387 > [2]: https://github.com/apache/daffodil/blob/main/NOTICE > > > > > > I did some research, but didn't know which is better: > > 1) Projects like flink[4] and pytorch[5] mention the license of other > > projects in the NOTICE file. > > > > Looking at flink (I can't speak to non-ASF projects) what they do is fine. > They don't store all of the licenses in the main license file, instead they > have a subdirectory and during their build they aggregate the license files > together to produce the final license. It's important to remember that we > evaluate based on the source release contents, not the git repository > layout. > > > > 2) But other projects such as spark[6] and arrow[7] all put the mentions > > into the `LICENSE` file. > > > > Are those both ways legal? Do we have a best practice here? > > > > 1. > > > > > https://github.com/apache/incubator-fury/blob/main/javascript/packages/hps/src/v8-fast-api-calls.h > > 2. > > > > > https://github.com/apache/incubator-fury/blob/main/java/fury-core/src/main/java/org/apache/fury/util/Preconditions.java > > 3. https://github.com/apache/incubator-fury/blob/main/NOTICE > > 4. https://github.com/apache/opendal/blob/master/NOTICE > > 5. https://github.com/pytorch/pytorch/blob/main/NOTICE > > 6. https://github.com/apache/spark/blob/master/LICENSE > > 7. tttps://github.com/apache/arrow/blob/main/LICENSE.txt > > > > > > Best regards, > > Chaokun Yang > > >
Re: Should we mention license of other projects in NOTICE file
On Sat, Apr 13, 2024 at 1:54 AM Shawn Yang wrote: > Dear Community, > > I'm fixing the license issue of Apache Fury to comply with ASF requirements > for the first release for Fury under ASF. > > Currently we borrowed some code from other projects such as > v8-fast-api-calls.h[1] in v8 and Preconditions[2] in guava. We mentioned > their license in our NOTICE file[3]. > I'm wondering whether we should move those mentions into the LICENSE file, > and mention the NOTICE of those projects in our NOTICE instead. > The NOTICE file is to be used to aggregate any notices you have. It is fine to mention that you're using something in your NOTICES file, including original sources for the content. The licenses those for those files needs to be in your license file. Here's an example from another project [1] [2]. [1]: https://github.com/apache/daffodil/blob/main/LICENSE#L359-L387 [2]: https://github.com/apache/daffodil/blob/main/NOTICE > > I did some research, but didn't know which is better: > 1) Projects like flink[4] and pytorch[5] mention the license of other > projects in the NOTICE file. > Looking at flink (I can't speak to non-ASF projects) what they do is fine. They don't store all of the licenses in the main license file, instead they have a subdirectory and during their build they aggregate the license files together to produce the final license. It's important to remember that we evaluate based on the source release contents, not the git repository layout. > 2) But other projects such as spark[6] and arrow[7] all put the mentions > into the `LICENSE` file. > > Are those both ways legal? Do we have a best practice here? > > 1. > > https://github.com/apache/incubator-fury/blob/main/javascript/packages/hps/src/v8-fast-api-calls.h > 2. > > https://github.com/apache/incubator-fury/blob/main/java/fury-core/src/main/java/org/apache/fury/util/Preconditions.java > 3. https://github.com/apache/incubator-fury/blob/main/NOTICE > 4. https://github.com/apache/opendal/blob/master/NOTICE > 5. https://github.com/pytorch/pytorch/blob/main/NOTICE > 6. https://github.com/apache/spark/blob/master/LICENSE > 7. tttps://github.com/apache/arrow/blob/main/LICENSE.txt > > > Best regards, > Chaokun Yang >
Should we mention license of other projects in NOTICE file
Dear Community, I'm fixing the license issue of Apache Fury to comply with ASF requirements for the first release for Fury under ASF. Currently we borrowed some code from other projects such as v8-fast-api-calls.h[1] in v8 and Preconditions[2] in guava. We mentioned their license in our NOTICE file[3]. I'm wondering whether we should move those mentions into the LICENSE file, and mention the NOTICE of those projects in our NOTICE instead. I did some research, but didn't know which is better: 1) Projects like flink[4] and pytorch[5] mention the license of other projects in the NOTICE file. 2) But other projects such as spark[6] and arrow[7] all put the mentions into the `LICENSE` file. Are those both ways legal? Do we have a best practice here? 1. https://github.com/apache/incubator-fury/blob/main/javascript/packages/hps/src/v8-fast-api-calls.h 2. https://github.com/apache/incubator-fury/blob/main/java/fury-core/src/main/java/org/apache/fury/util/Preconditions.java 3. https://github.com/apache/incubator-fury/blob/main/NOTICE 4. https://github.com/apache/opendal/blob/master/NOTICE 5. https://github.com/pytorch/pytorch/blob/main/NOTICE 6. https://github.com/apache/spark/blob/master/LICENSE 7. tttps://github.com/apache/arrow/blob/main/LICENSE.txt Best regards, Chaokun Yang
