All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Fri, 3 Nov 2023 15:20:36 +0700	[thread overview]
Message-ID: <ZUStVO0VSJ6CN_xe@debian.me> (raw)
In-Reply-To: <CAC1cPGyLGEwMBRGhwoGmGBeM8qTbuuUsbeZTiiMNUvk4MT75Gw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]

On Thu, Nov 02, 2023 at 10:09:57AM -0400, Richard Fontana wrote:
> On Thu, Nov 2, 2023 at 8:01 AM Bagas Sanjaya <bagasdotme@gmail.com> 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.
> 
> I don't really  understand this, though maybe it doesn't practically matter -
> "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."
> 
> I didn't check if this text is just copied from that in other license files.

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

> 
> 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:
> 
> > +  Do NOT use this license for code, but it's acceptable for fonts (where the
> > +  license is specifically written for them). It's best to use it together
> 
> Even if that did occur, the use of `OR` is only appropriate if the
> stuff covered by OFL-1.1 is actually dual-licensed.
> 

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 Open
 * Font License, version 1.1. See OFL.txt in the same directory as this file
 * for details. */
<actual stylesheet>
...
```

Is above acceptable?

Thanks.

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-11-03  8:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 12:00 [PATCH RFC 0/4] Documentation: Web fonts for kernel documentation Bagas Sanjaya
2023-11-02 12:00 ` [PATCH RFC 1/4] LICENSES: Add SIL Open Font License 1.1 Bagas Sanjaya
2023-11-02 14:06   ` Greg Kroah-Hartman
2023-11-03  8:11     ` Bagas Sanjaya
2023-11-03  8:49       ` Greg Kroah-Hartman
2023-11-04  0:53         ` Bagas Sanjaya
2023-11-04  9:52           ` Greg Kroah-Hartman
2023-11-05 23:40             ` Bagas Sanjaya
2023-11-02 14:09   ` Richard Fontana
2023-11-03  8:20     ` Bagas Sanjaya [this message]
2023-11-02 12:00 ` [PATCH RFC 2/4] Docmentation: Use IBM Plex Sans for page body Bagas Sanjaya
2023-11-02 12:00 ` [PATCH RFC 3/4] Documentation: Use Newsreader font for document headings Bagas Sanjaya
2023-11-02 12:00 ` [PATCH RFC 4/4] Documentation: Use IBM Plex Mono as monospace font Bagas Sanjaya
2023-11-02 12:17 ` [PATCH RFC 0/4] Documentation: Web fonts for kernel documentation Bagas Sanjaya
2023-11-02 16:41 ` Miguel Ojeda
2023-11-03 14:30 ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZUStVO0VSJ6CN_xe@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=carlos.bilbao@amd.com \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=federico.vaga@vaga.pv.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=james@equiv.tech \
    --cc=linux-doc@ger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rfontana@redhat.com \
    --cc=sdf@google.com \
    --cc=tglx@linutronix.de \
    --cc=void@manifault.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.