workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Jakub Kicinski <kuba@kernel.org>
Cc: corbet@lwn.net, workflows@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, gregkh@linuxfoundation.org,
	linux@leemhuis.info, broonie@kernel.org, krzk@kernel.org
Subject: Re: [PATCH docs v2] docs: maintainer: document expectations of small time maintainers
Date: Tue, 18 Jul 2023 18:55:28 +0200	[thread overview]
Message-ID: <25a50453-cbb6-4933-bb2f-79dfd2c76f9d@lunn.ch> (raw)
In-Reply-To: <20230718155814.1674087-1-kuba@kernel.org>

> +Selecting the maintainer
> +========================
> +
> +The previous section described the expectations of the maintainer,
> +this section provides guidance on selecting one and decribes common

s/decribes/describes

> +Maintainers must be human, however, it is not acceptable to add a mailing
> +list or a group email as a maintainer.

I would probably replace however, with therefore. 

> +Removing an inactive maintainer should not be seen as a punitive action.
> +Having an inactive maintainer has a real cost as all developeres have

Too many e's in developeres

Otherwise:

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  reply	other threads:[~2023-07-18 17:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 15:58 Jakub Kicinski
2023-07-18 16:55 ` Andrew Lunn [this message]
2023-07-18 17:34 ` Greg KH
2023-07-18 18:06 ` Krzysztof Kozlowski
2023-07-18 19:19 ` Benjamin Poirier
2023-07-18 19:55 ` Mark Brown
2023-07-19 18:26   ` Jakub Kicinski
2023-07-18 22:02 ` Shannon Nelson
2023-07-19  7:27 ` Leon Romanovsky
2023-07-19 17:54 ` Rob Herring
2023-07-19 18:36   ` Jakub Kicinski

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=25a50453-cbb6-4933-bb2f-79dfd2c76f9d@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=netdev@vger.kernel.org \
    --cc=workflows@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