Hi Justin,
JIRA has been reopened and added information about license.
Also added Google Fonts and Source Sans Pro license information
in Apache Kylin's LICENSE file.
It looks like Google Fonts included Source Sans Pro, and has it's
own license agreement, suppose Google has done such legal stuff already.
So my question is: Which license should to be declare in downstream
of
Google Fonts? Is it good enough to only add Google Fonts license, or
should
to add all hierarchy dependencies licenses?
Would love to have your guide and inputs for this.
Thank you very much.
Luke
Best Regards!
---------------------
Luke Han
On Fri, Oct 23, 2015 at 5:10 AM, Justin Mclean <jus...@classsoftware.com>
wrote:
> HI,
>
> > You need to update the LICENSE file for Kylin to include the one for
> AdminLTE.
>
> The files in question are not part of AdminLTE [1] that I can see. Even
> if they were they would have different copyright owners and a different
> LICENCE to AdminLTE. An educated guess is that they are the Source San Pro
> font and that is copyright Adobe and license under the SIL Open Font
> License [2]. It would be best to double check the font metadata in the
> files as that usually includes their licensing information.
>
> Thanks,
> Justin
>
> 1. https://github.com/almasaeed2010/AdminLTE
> 2. http://www.fontsquirrel.com/license/source-sans-pro
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
