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:20:36 +0700
From:   Bagas Sanjaya <bagasdotme@gmail.com>
To:     Richard Fontana <rfontana@redhat.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Documentation <linux-doc@ger.kernel.org>,
        Jonathan Corbet <corbet@lwn.net>,
        Thomas Gleixner <tglx@linutronix.de>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        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
Subject: Re: [PATCH RFC 1/4] LICENSES: Add SIL Open Font License 1.1
Message-ID: <ZUStVO0VSJ6CN_xe@debian.me>
References: <20231102120053.30630-1-bagasdotme@gmail.com>
 <20231102120053.30630-2-bagasdotme@gmail.com>
 <CAC1cPGyLGEwMBRGhwoGmGBeM8qTbuuUsbeZTiiMNUvk4MT75Gw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="mQMlOV5B+hEL++/T"
Content-Disposition: inline
In-Reply-To: <CAC1cPGyLGEwMBRGhwoGmGBeM8qTbuuUsbeZTiiMNUvk4MT75Gw@mail.gmail.com>
Precedence: bulk


--mQMlOV5B+hEL++/T
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Nov 02, 2023 at 10:09:57AM -0400, Richard Fontana wrote:
> On Thu, Nov 2, 2023 at 8:01=E2=80=AFAM Bagas Sanjaya <bagasdotme@gmail.co=
m> 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.
> >
> > 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
> I don't really  understand this, though maybe it doesn't practically matt=
er -
> "It's best to use it together
> +  with a GPL2 compatible license using "OR", as OFL-1.1 texts processed =
by
> +  the kernel's build system might combine it with content taken from more
> +  restrictive licenses."
>=20
> I didn't check if this text is just copied from that in other license fil=
es.

Yes, indeed I adapted it from LICENSES/dual/CC-BY-4.0.

>=20
> I'm not sure how this would actually come up in practice for OFL-1.1.
> I assume that typically the way OFL-1.1 can cover stuff in the kernel
> is through font files, and that therefore it would be unlikely for a
> source file to include any code covered by OFL-1.1. Indeed, as you
> say:
>=20
> > +  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
>=20
> Even if that did occur, the use of `OR` is only appropriate if the
> stuff covered by OFL-1.1 is actually dual-licensed.
>=20

Another alternative is to put license notice on CSS code that includes
the font. In this case, in Documentation/sphinx-static/fonts.css, the top
of the file should've been written as:

```
/* SPDX-License-Identifier: GPL-2.0 */
/* IBM Plex Sans, IBM Plex Mono, and Newsreader is licensed under the SIL O=
pen
 * Font License, version 1.1. See OFL.txt in the same directory as this file
 * for details. */
<actual stylesheet>
=2E..
```

Is above acceptable?

Thanks.

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

--mQMlOV5B+hEL++/T
Content-Type: application/pgp-signature; name="signature.asc"

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

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZUStVAAKCRD2uYlJVVFO
o9gLAQDXh5KuHQXosius1a/fheR87htYw1ghwPHEieWn7c3wCwEA845XRPFLf/07
dW6DDLQVWuFKmhu7qx9KDrsNapzPXQA=
=T3vu
-----END PGP SIGNATURE-----

--mQMlOV5B+hEL++/T--