All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.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>,
	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
Date: Thu, 2 Nov 2023 15:06:19 +0100	[thread overview]
Message-ID: <2023110222-renewed-monologue-008e@gregkh> (raw)
In-Reply-To: <20231102120053.30630-2-bagasdotme@gmail.com>

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.
> 
> 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.
> 
> 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 ++++++++++++++++++++++++++++++++++++++++++

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?

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

>  1 file changed, 107 insertions(+)
>  create mode 100644 LICENSES/dual/OFL-1.1
> 
> 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 (where the
> +  license is specifically written for them). 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.
> +  To use the SIL Open Font License 1.1, put the following SPDX tag/value pair
> +  into a comment according to the placement guidelines in the licensing rules
> +  documentation:
> +    SPDX-License-Identifier: OFL-1.1

Where did this Usage-Guide from?

thanks,

greg k-h

  reply	other threads:[~2023-11-02 14:06 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 [this message]
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
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=2023110222-renewed-monologue-008e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akiyks@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=carlos.bilbao@amd.com \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=federico.vaga@vaga.pv.it \
    --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.