Signing all patches and email to this list
Alejandro Colomar
maintainerHi,
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 <[email protected]> Date: Fri Nov 10 01:10:00 2023 +0100
CONTRIBUTING: Please sign your emails with PGP
Signed-off-by Alejandro Colomar <[email protected]>
CONTRIBUTING +23 -0
@@ -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. + + There are many ways you can sign your patches, and it + depends on your preferred tools. You can use + git-send-email(1) in combination with mutt(1). For that, + do the following. + + In <~/.gitconfig>, add the following section: + + [sendemail] + sendmailcmd = mutt -H - && true + + And then, patched mutt(1) to enable encryption in batch and + mailx modes, which is disabled in upstream mutt(1). + Hopefully, mutt(1) will merge the patch, so it'd be easier + to do this. You can find the patch here: + <https://gitlab.com/muttmua/mutt/-/merge_requests/173>. + Patches If you know how to fix a problem in a manual page (if not, see "Reporting bugs" below), then send a patch in an email.
Signature · 1 line
<https://www.alejandro-colomar.es/>