Thanks Justin for your information. We can remove Font-Awesome dependencies and use new fonts in future.
I have fixed these issues, will create a new RC. Best, Jingsong On Tue, May 23, 2023 at 1:01 PM <jus...@classsoftware.com> wrote: > > Hi, > > > Font-Awesome has different licenses for code and fonts. So I just > > introduce two license files: LICENSE.font-awesome-code and > > LICENSE.font-awesome-fonts. Copy the contents of their respective > > licenses. > > > > And in LICENSE file: > > > > MIT License > > ----------- > > docs/static/font-awesome/css/* from > > https://github.com/FortAwesome/Font-Awesome version 6 > > > > SIL OFL 1.1 License > > ------------ > > docs/static/font-awesome/fonts/* from > > https://github.com/FortAwesome/Font-Awesome version 6 > > That would be the right approach, however the SIL OFL is Category B and can’t > be included in a source release, so it would be best to replace it with > something else. > > > Is it correct to copy all the contents of the NOTICE file? > > You can, but it’s better to only copy the relevant bits to the 3rd party code > you are using. > > Kind Regards, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
