Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:7 as permitted sender) client-ip=2620:137:e000::3:7;
Date:   Fri, 3 Nov 2023 15:11:36 +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: <ZUSrOKDuvcSL6gOH@debian.me>
References: <20231102120053.30630-1-bagasdotme@gmail.com>
 <20231102120053.30630-2-bagasdotme@gmail.com>
 <2023110222-renewed-monologue-008e@gregkh>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="/KWzKcdL50ByjLLA"
Content-Disposition: inline
In-Reply-To: <2023110222-renewed-monologue-008e@gregkh>
Precedence: bulk


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

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:
> > Add the license text along with appropriate tags for reference and
> > tooling. The text is taken from the text as distributed in Google
> > Fonts's zip files.
> >=20
> > As the license itself may or may note be compatible with GPLv2,
> > let's take on the err side and require combining it with
> > GPL-compatible licenses when using the license.
> >=20
> > Cc: linux-spdx@vger.kernel.org
> > Cc: Richard Fontana <rfontana@redhat.com>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> > ---
> >  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 can
> handle this properly?

There is TTF name string ID called "License". For example, on IBM Plex Sans,
the string value is:

```
This Font Software is licensed under the SIL Open Font License, Version 1.1=
=2E This license is available with a FAQ at: http://scripts.sil.org/OFL
```

Checking that string requires scripting fontforge, and since the string val=
ue
may differ (but has the same license) across different fonts, scripting it
can be non-trivial.

>=20
> And, it's not going to work as a dual-license, you can't just suddenly
> dual-license those font files, right?

I was thinking of putting OFL in LICENSES/exceptions instead due to this
nature.

>=20
> >  1 file changed, 107 insertions(+)
> >  create mode 100644 LICENSES/dual/OFL-1.1
> >=20
> > diff --git a/LICENSES/dual/OFL-1.1 b/LICENSES/dual/OFL-1.1
> > new file mode 100644
> > index 00000000000000..00b8db08bd0e54
> > --- /dev/null
> > +++ b/LICENSES/dual/OFL-1.1
> > @@ -0,0 +1,107 @@
> > +Valid-License-Identifier: OFL-1.1
> > +SPDX-URL: https://spdx.org/licenses/OFL-1.1
> > +Usage-Guide:
> > +  Do NOT use this license for code, but it's acceptable for fonts (whe=
re the
> > +  license is specifically written for them). It's best to use it toget=
her
> > +  with a GPL2 compatible license using "OR", as OFL-1.1 texts processe=
d by
> > +  the kernel's build system might combine it with content taken from m=
ore
> > +  restrictive licenses.
> > +  To use the SIL Open Font License 1.1, put the following SPDX tag/val=
ue pair
> > +  into a comment according to the placement guidelines in the licensin=
g rules
> > +  documentation:
> > +    SPDX-License-Identifier: OFL-1.1
>=20
> Where did this Usage-Guide from?

Adapted from LICENSES/dual/CC-BY-4.0.

Thanks.

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

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

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

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZUSrNAAKCRD2uYlJVVFO
owOVAQDfc6tg3jOz4yW4hs8/7Tdj2N5B9WFJcdKKBu41RNyd5AEAmor1Fmesa51e
GupVUCytz7URedQA/dvn3osN4cGy0ww=
=tuOf
-----END PGP SIGNATURE-----

--/KWzKcdL50ByjLLA--