public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Stock image illustration (licensing)
Date: Tue, 06 Jun 2023 08:36:47 -0600	[thread overview]
Message-ID: <87fs74y7wg.fsf@meer.lwn.net> (raw)
In-Reply-To: <e6047201-7cf1-ecc4-ca68-490142f6f40b@gmail.com>

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> Hi,
>
> Imagine that there is a new Linux kernel contributor, contributing
> documentation patches. As it is the habit from her company, she adds
> stock images from various sources (which may or may not be related
> to the doc), e.g. freepik or pexels [1], as illustration.
>
> However, on the source file, the image requires attribution. Yet,
> the attribution instruction doesn't mention image license (she
> attributes as "Illustration of foo by bar on pexels"), hence
> all rights reserved. Can that stock image be added to the kernel
> docs (which is licensed under GPL)?

I am rather curious as to why you are asking this question.

Images, like everything else, need clear licensing.  Images that do not
have a GPL-compatible license cannot be added to the kernel.

But we are certainly not in the habit of decorating our documentation
with "stock images", so this is not a question that has ever come up.

jon

  reply	other threads:[~2023-06-06 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 14:21 Stock image illustration (licensing) Bagas Sanjaya
2023-06-06 14:36 ` Jonathan Corbet [this message]
2023-06-06 16:25 ` Greg Kroah-Hartman

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=87fs74y7wg.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox