From: Matthew House <mattlloydhouse@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: Signing all patches and email to this list
Date: Wed, 15 Nov 2023 18:28:42 -0500 [thread overview]
Message-ID: <20231115232848.693843-1-mattlloydhouse@gmail.com> (raw)
In-Reply-To: <20231115212015.6446-1-alx@kernel.org>
On Mon, Nov 13, 2023 at 6:46 PM Alejandro Colomar <alx@kernel.org> wrote:
> Hi,
>
> I'd like to ask contributors to sign their emails to this list with a
> PGP key; especially for mails that include patches, but ideally all of
> them. Of course, it's a suggestion, and there wouldn't be any
> enforcement other than asking. What do you think of that?
>
> I've prepared some text for ./CONTRIBUTING; please review. It also
> depends on mutt(1) maintainers, if they want to patch mutt(1) to allow
> crypto operations in batch and mailx modes.
>
> Thanks,
> Alex
>
> ---
>
> commit f7ba049d975a4b323c8086b2fc859687e4fc1d4e (HEAD -> sign)
> Author: Alejandro Colomar <alx@kernel.org>
> Date: Fri Nov 10 01:10:00 2023 +0100
>
> CONTRIBUTING: Please sign your emails with PGP
>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
>
> diff --git a/CONTRIBUTING b/CONTRIBUTING
> index 475244c13..204e04fb3 100644
> --- a/CONTRIBUTING
> +++ b/CONTRIBUTING
> @@ -56,6 +56,29 @@ Description
>
> help
>
> + Sign your emails with PGP
> + Please sign all of your emails sent to the mailing list,
> + including your emails containing patches, with your PGP
> + key. This helps establish trust between you and other
> + contributors of this project, and prevent others
> + impersonating you.
If this is meant to be a suggestion rather than an obligation, then I'd
prefer if it had an explicit statement to the effect that it is (strongly?)
encouraged but not mandatory. If I were reading CONTRIBUTING for the first
time, I'd be inclined to read the bare imperative "Please sign all of your
emails" as a hard requirement, and be scared off on account of not even
having a PGP key.
Thank you,
Matthew House
next parent reply other threads:[~2023-11-15 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231115212015.6446-1-alx@kernel.org>
2023-11-15 23:28 ` Matthew House [this message]
2023-11-15 23:39 ` Signing all patches and email to this list Alejandro Colomar
2023-11-13 23:46 Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 11:27 strncpy clarify result may not be null terminated Jonny Grant
2023-11-12 11:26 ` [PATCH v2 1/3] string_copying.7: BUGS: *cat(3) functions aren't always bad Alejandro Colomar
2023-11-17 21:43 ` Jonny Grant
2023-11-18 0:25 ` Signing all patches and email to this list Matthew House
2023-11-18 23:24 ` Jonny Grant
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=20231115232848.693843-1-mattlloydhouse@gmail.com \
--to=mattlloydhouse@gmail.com \
--cc=alx@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).