Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) client-ip=2620:137:e000::3:2;
Date:   Mon, 6 Nov 2023 06:40:18 +0700
From:   Bagas Sanjaya <bagasdotme@gmail.com>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Documentation <linux-doc@vger.kernel.org>,
        Jonathan Corbet <corbet@lwn.net>,
        Thomas Gleixner <tglx@linutronix.de>,
        Akira Yokosawa <akiyks@gmail.com>,
        Stanislav Fomichev <sdf@google.com>,
        David Vernet <void@manifault.com>,
        Miguel Ojeda <ojeda@kernel.org>, James Seo <james@equiv.tech>,
        Daniel Vetter <daniel.vetter@ffwll.ch>,
        Federico Vaga <federico.vaga@vaga.pv.it>,
        Carlos Bilbao <carlos.bilbao@amd.com>,
        linux-spdx@vger.kernel.org, Richard Fontana <rfontana@redhat.com>
Subject: Re: [PATCH RFC 1/4] LICENSES: Add SIL Open Font License 1.1
Message-ID: <ZUgn4r182L57jRgs@debian.me>
References: <20231102120053.30630-1-bagasdotme@gmail.com>
 <20231102120053.30630-2-bagasdotme@gmail.com>
 <2023110222-renewed-monologue-008e@gregkh>
 <ZUSrOKDuvcSL6gOH@debian.me>
 <2023110317-unhealthy-playable-d5d6@gregkh>
 <ZUWV88wRf9suUQfH@debian.me>
 <2023110450-overview-charbroil-5101@gregkh>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="EqQct6nULlqsJlUU"
Content-Disposition: inline
In-Reply-To: <2023110450-overview-charbroil-5101@gregkh>
Precedence: bulk


--EqQct6nULlqsJlUU
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Nov 04, 2023 at 10:52:06AM +0100, Greg Kroah-Hartman wrote:
> On Sat, Nov 04, 2023 at 07:53:07AM +0700, Bagas Sanjaya wrote:
> > On Fri, Nov 03, 2023 at 09:49:54AM +0100, Greg Kroah-Hartman wrote:
> > > On Fri, Nov 03, 2023 at 03:11:36PM +0700, Bagas Sanjaya wrote:
> > > > On Thu, Nov 02, 2023 at 03:06:19PM +0100, Greg Kroah-Hartman wrote:
> > > > > On Thu, Nov 02, 2023 at 07:00:43PM +0700, Bagas Sanjaya wrote:
> > > > > >  LICENSES/dual/OFL-1.1 | 107 ++++++++++++++++++++++++++++++++++=
++++++++
> > > > >=20
> > > > > You add this license, but then never actually reference it in the=
 later
> > > > > changes, so it's going to be very confusing as to why it is here.=
  Any
> > > > > way to add it to the font files themselves so our checker tools c=
an
> > > > > handle this properly?
> > > >=20
> > > > There is TTF name string ID called "License". For example, on IBM P=
lex Sans,
> > > > the string value is:
> > > >=20
> > > > ```
> > > > This Font Software is licensed under the SIL Open Font License, Ver=
sion 1.1. This license is available with a FAQ at: http://scripts.sil.org/O=
FL
> > > > ```
> > > >=20
> > > > Checking that string requires scripting fontforge, and since the st=
ring value
> > > > may differ (but has the same license) across different fonts, scrip=
ting it
> > > > can be non-trivial.
> > >=20
> > > And is that in the files you added?  They are binary so it's hard to
> > > determine this :(
> >=20
> > Yes.
> >=20
> > >=20
> > > > >=20
> > > > > And, it's not going to work as a dual-license, you can't just sud=
denly
> > > > > dual-license those font files, right?
> > > >=20
> > > > I was thinking of putting OFL in LICENSES/exceptions instead due to=
 this
> > > > nature.
> > >=20
> > > Yes, it can not be a dual one.
> >=20
> > That's right!
> >=20
> > What about just saying below in the CSS file that includes the fonts?
> >=20
> > ```
> > ...
> > /* Some cool fonts are licensed under OFL 1.1, see
> >  * LICENSES/exceptions/OFL-1.1 for more information. */
> > ...
> > ```
>=20
> That's not in SPDX format :)

Yes, without it (CSS files of course should already have SPDX line); but I
highlight importing webfonts above, where due to binary nature of font file=
s,
we have to resort to simple license notice above (pre-SPDX) whenever about
to use them.

>=20
> Anyway, I think the meta-comment so far is "do we want to include fonts
> in the kernel source", right?  For that, I would argue "no, let's not
> deal with that mess for now".
>=20

So far I'm only concerned about including OFL fonts. In the cover letter,
I also considered non-free, paid fonts (like S=C3=B6hne), which IMO looks b=
etter
than IBM Plex. Of course, if someone submits a version of this series but
with S=C3=B6hne instead (hey because many other sites do use that font), Gr=
eg will
instantly reject it, right?

Thanks.

--=20
An old man doll... just what I always wanted! - Clara

--EqQct6nULlqsJlUU
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZUgn3AAKCRD2uYlJVVFO
o8ciAP9kH4RHvlmygSiGDHPGweVMR8cbIwKe1QszfT+QZBMp9QEA6mnjglHnpCDD
kMmnGWXVfyfkQeGY4DP/MvWXak1vNA4=
=7bhi
-----END PGP SIGNATURE-----

--EqQct6nULlqsJlUU--