public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andries E. Brouwer" <aeb@cwi.nl>
To: Alejandro Colomar <alx@kernel.org>
Cc: "Andries E. Brouwer" <aeb@cwi.nl>,
	linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
	libc-alpha@sourceware.org
Subject: Re: man-pages-6.14 released
Date: Fri, 9 May 2025 14:14:54 +0200	[thread overview]
Message-ID: <20250509121454.GA952723@if> (raw)
In-Reply-To: <bn2rs76dkhejmthy2wvul4ho26zzlwtkfg474ztiwggkxz7f3d@g25omktsd3ug>

Hi Alejandro,

> > I wonder about the legal status of such a change.
> > There is ownership of the pages, and a license that allows
> > others to do certain things.
> 
> I also wonder about it.  We discussed it for several (~3) months, and I
> documented links to the discussion in the commit message:
> 
> commit 9f2986c34166085225bb5606ebfd4952054e1657
> Author: Alejandro Colomar <alx@kernel.org>
> Date:   Fri Apr 11 02:19:48 2025 +0200
> 
>     *, CREDITS: Unify copyright notices
>     
>     Link: <https://lore.kernel.org/linux-man/jpin2dbnp5vpitnh7l4qmvkamzq3h3xljzsznrudgioox3nn72@57uybxbe3h4p/T/#u>
>     Link: <https://www.linuxfoundation.org/blog/blog/copyright-notices-in-open-source-software-projects>

So I read this last link, and see

"Don’t change someone else’s copyright notice without their permission
You should not change or remove someone else’s copyright notice unless
they have expressly (in writing) permitted you to do so. This includes
third parties’ notices in pre-existing code."

The main topic of that link is how one should document new contributions,
and writing "by the contributors of the foo project" is OK for new stuff,
of course provided the new contributor agrees.
In my opinion it is illegal to change existing copyright notices,
unless you get permission from all people involved, which seems unlikely.

Andries

  reply	other threads:[~2025-05-09 12:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 23:15 man-pages-6.14 released Alejandro Colomar
2025-05-09 11:26 ` Andries E. Brouwer
2025-05-09 12:02   ` Alejandro Colomar
2025-05-09 12:14     ` Andries E. Brouwer [this message]
2025-05-09 12:28       ` Alejandro Colomar
2025-05-09 12:48         ` Vincent Lefevre
2025-05-09 12:57           ` Alejandro Colomar
2025-05-09 13:11             ` Vincent Lefevre
2025-06-26 20:41       ` Carlos O'Donell
2025-06-26 21:04         ` Alejandro Colomar
2025-06-26 23:01           ` Carlos O'Donell
2025-06-26 23:14             ` Alejandro Colomar
2025-06-27  0:08               ` Andries E. Brouwer
2025-06-27  0:45                 ` Alejandro Colomar
2026-02-08 22:04               ` Alejandro Colomar
2025-06-27  0:20             ` Vincent Lefevre
2025-06-27  4:23               ` Alejandro Colomar
2025-06-27  7:49                 ` Vincent Lefevre
2025-06-27 13:09                   ` Alejandro Colomar

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=20250509121454.GA952723@if \
    --to=aeb@cwi.nl \
    --cc=alx@kernel.org \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@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