public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Martin <Dave.Martin@arm.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Carlos O'Donell <carlos@redhat.com>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: Removing in-source contribution records contributer
Date: Mon, 12 May 2025 12:40:39 +0100	[thread overview]
Message-ID: <aCHeN7Kh3VNOGP5c@e133380.arm.com> (raw)
In-Reply-To: <juos3oxvdsxkwzwe5rcst3jft3wsnhh4dxs6xasvfk2nzp7jdo@h2tz4hvtkqp7>

Hi,

On Fri, May 09, 2025 at 09:07:47PM +0200, Alejandro Colomar wrote:
> Hi Dave,
> 
> On Fri, May 09, 2025 at 08:49:39PM +0200, Alejandro Colomar wrote:
> > Hi Dave,
> > 
> > On Fri, May 09, 2025 at 04:43:36PM +0100, Dave Martin wrote:

[...]

> > > Just a suggestion, would something like this work in README:
> > > 
> > > +   AUTHORS
> > > +       List of individuals and organizations that have contributed
> > > +       content to the project.
> > > +
> > 
> > Certainly.  Thanks!
> > 
> > > This will still be a true description regardless of whether the list
> > > is complete or if non page content contributors are included.  (There
> > > are probably plenty of borderline cases as to whether something counts
> > > as a page content contribution or not.)
> > 
> > Yep.  For now, I haven't documented it, but I've drawn the line at:
> > 
> > 	-  Had its name either in a copyright notice,
> > 	-  or in a source line saying something like "modified by"
> > 	-  or was 'Author' in a git commit.
> > 
> > Anyone who meets at least one of those has been included in CREDITS (to
> > be renamed to AUTHORS).
> > 
> > Exceptions are authors of code that was taken by this project, but who
> > didn't contribute to this project themselves.  For example, the regents
> > of the University of California wrote pages that have been incorporated
> > into this project, but they didn't consciously contribute to this
> > project.  Thus, I've retained their copyright notices, and didn't add
> > them to CREDITS.

Seems reasonable.

> I've applied both changes already (currently in my branch):
> 
> <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=98c87fcf783f20da7aae8adbe21e1954d9e8f310>
> <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=d5218b220e41a1ed031eea6219237fda0a93d9b2>

Looks good to me.  Thanks for the credit.

Cheers
---Dave

  reply	other threads:[~2025-05-12 11:40 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 [this message]
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
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=aCHeN7Kh3VNOGP5c@e133380.arm.com \
    --to=dave.martin@arm.com \
    --cc=alx@kernel.org \
    --cc=carlos@redhat.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