From: Carlos O'Donell <carlos@redhat.com>
To: Alejandro Colomar <alx@kernel.org>,
Eugene Syromyatnikov <evgsyr@gmail.com>
Cc: linux-man@vger.kernel.org,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
Amit Pinhas <amitpinhass@gmail.com>
Subject: Re: Removing in-source contribution records contributer
Date: Wed, 9 Apr 2025 17:15:21 -0400 [thread overview]
Message-ID: <856467f3-73b4-4b45-a2c4-f7b4f44b1de2@redhat.com> (raw)
In-Reply-To: <37qabjc65x7co7f3oiibpgwtvhnigk5z7tpmmzgrjhisi4nqmz@ypx33dbbltdn>
On 4/8/25 5:25 PM, Alejandro Colomar wrote:
> Hi Eugene,
>
> On Tue, Apr 08, 2025 at 08:00:19PM +0200, Eugene Syromyatnikov wrote:
>>>>> Every now and then, I consider if I should just remove all of those
>>>>> lines, to avoid confusing people. If anyone is interested in the
>>>>> history before git(1), one can certainly look at those lines in old
>>>>> versions of the pages. Anyone reading the mailing list opposes
>>>>> removing those lines? (I'll ask again before removing anything, with
>>>>> a proper subject line.)
>>>
>>> Okay, time has come to open this melon. :)
>>
>> In strace, FWIW, we have the following:
>> * the copyright notice looks like "Copyright (c) <year>-<year> The
>> strace developers.";
>
> Hmmm, interesting. And actually, it's more accurate than the usual
> copyright lines.
The value of the line "Copyright (c) The Foo Developers" is to indicate
that the works are copyrighted, and it avoids anyone who infringes from
arguing they "didn't know." It is in itself not a copyright statement.
What value is there in maintaining the year?
Note:
Copyright Notices in Open Source Software Projects (Steve Winslow)
https://www.linuxfoundation.org/blog/blog/copyright-notices-in-open-source-software-projects
--
Cheers,
Carlos.
next prev parent reply other threads:[~2025-04-09 21:15 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1739389071.git.amitpinhass@gmail.com>
2025-02-12 19:39 ` [PATCH v2 2/2] [PATCH v2] man/man2/kill.2: Add Amit Pinhas as a contributer Amit Pinhas
2025-02-12 20:26 ` Alejandro Colomar
2025-02-12 23:02 ` G. Branden Robinson
2025-02-12 23:20 ` Removing in-source contribution records contributer Alejandro Colomar
2025-04-07 23:05 ` Alejandro Colomar
2025-04-08 12:42 ` G. Branden Robinson
2025-04-08 20:18 ` Carlos O'Donell
2025-04-08 21:28 ` Alejandro Colomar
2025-05-09 12:54 ` Alejandro Colomar
2025-05-09 13:04 ` Stephen Kitt
2025-05-09 13:05 ` Mathieu Desnoyers
2025-05-09 13:14 ` Carlos O'Donell
2025-05-09 13:31 ` Alejandro Colomar
2025-05-09 13:39 ` Josef Bacik
2025-05-09 13:50 ` наб
2025-05-09 13:55 ` Michael Haardt
2025-05-09 14:14 ` Dave Martin
2025-05-09 14:39 ` Alejandro Colomar
2025-05-09 14:48 ` G. Branden Robinson
2025-05-09 15:43 ` Dave Martin
2025-05-09 18:49 ` Alejandro Colomar
2025-05-09 19:07 ` Alejandro Colomar
2025-05-12 11:40 ` Dave Martin
2025-05-09 14:16 ` Heinrich Schuchardt
2025-05-09 15:13 ` Tycho Andersen
2025-05-09 18:35 ` Alejandro Colomar
2025-05-09 20:56 ` Tycho Andersen
2025-05-09 21:11 ` Alejandro Colomar
2025-05-10 22:24 ` Tycho Andersen
2025-05-09 18:22 ` Christoph Lameter (Ampere)
2025-05-09 18:53 ` Alejandro Colomar
2025-05-09 18:31 ` Christoph Lameter (Ampere)
2025-05-09 19:11 ` Alejandro Colomar
2025-05-09 21:19 ` Andrew Morton
2025-05-09 21:25 ` Alejandro Colomar
[not found] ` <5681932.rdbgypaU67@sodium>
2025-05-10 11:02 ` Alejandro Colomar
2025-05-12 7:58 ` Sean Young
2025-05-12 18:51 ` Stefan Hajnoczi
2025-05-12 19:03 ` Thomas Gleixner
2025-05-19 7:40 ` Florent Revest
2025-04-08 18:00 ` Eugene Syromyatnikov
2025-04-08 21:25 ` Alejandro Colomar
2025-04-09 21:15 ` Carlos O'Donell [this message]
2025-04-09 23:25 ` Alejandro Colomar
2025-05-05 22:51 ` Alejandro Colomar
2025-05-06 9:22 ` Eugene Syromyatnikov
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=856467f3-73b4-4b45-a2c4-f7b4f44b1de2@redhat.com \
--to=carlos@redhat.com \
--cc=alx@kernel.org \
--cc=amitpinhass@gmail.com \
--cc=evgsyr@gmail.com \
--cc=g.branden.robinson@gmail.com \
--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