From: Carlos O'Donell <carlos@redhat.com>
To: "Andries E. Brouwer" <aeb@cwi.nl>, Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
libc-alpha@sourceware.org
Subject: Re: man-pages-6.14 released
Date: Thu, 26 Jun 2025 16:41:16 -0400 [thread overview]
Message-ID: <3e82680d-149c-4a67-b838-bc73c0be3e4e@redhat.com> (raw)
In-Reply-To: <20250509121454.GA952723@if>
On 5/9/25 8:14 AM, Andries E. Brouwer wrote:
> 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.
I agree with Andries.
This is also my interpretation, you cannot remove these entries without
express permission from the copyright holder.
In glibc we did not remove any copyright notices, but *added* under DCO
"Copyright, The GNU Toolchain authors."
Example:
1 /* Map in a shared object's segments from the file.
2 Copyright (C) 1995-2025 Free Software Foundation, Inc.
3 Copyright The GNU Toolchain Authors.
4 This file is part of the GNU C Library.
...
--
Cheers,
Carlos.
next prev parent reply other threads:[~2025-06-26 20:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 23:15 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
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 [this message]
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=3e82680d-149c-4a67-b838-bc73c0be3e4e@redhat.com \
--to=carlos@redhat.com \
--cc=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
all inboxes | Powered by JetHome®