Re: Should we mention license of other projects in NOTICE file

2024-04-14 Thread Shawn Yang
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

Re: Should we mention license of other projects in NOTICE file

2024-04-13 Thread Justin Mclean
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

Re: Should we mention license of other projects in NOTICE file

2024-04-13 Thread Shawn Yang
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:

Re: Should we mention license of other projects in NOTICE file

2024-04-13 Thread John D. Ament
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

Should we mention license of other projects in NOTICE file

2024-04-12 Thread Shawn Yang
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