PGP signing commits

--nextPartEaPTPPl9SIuqEK_UWTg1dg
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Martin Bednar <martin-bVyCAMn5I1PtwjQa/[email protected]>
To: [email protected]
Subject: PGP signing commits
Date: Thu, 11 Jun 2026 21:12:18 +0200
Message-ID: <d5dYUs89Rt-aH5Psi3HFYw-bVyCAMn5I1PtwjQa/[email protected]>
MIME-Version: 1.0

Hi, 

On the topic of requiring GPG signed commits, opened here:
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/896#note_1519822

I believe this warrants a wider discussion.

I'm all for it, as in anything going into master should be PGP signed. I am 
however worried that it creates yet another hurdle for one off contributions, 
as we have had a few in the past few months. Any thoughts on that?

Should we enforce this at gitlab level?

And on a slightly related note: Anyone going to Akademy?

Martin.

--nextPartEaPTPPl9SIuqEK_UWTg1dg
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQSQahp3QLKdvHTT9rcGyo/AjsPylgUCaisIkhsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIACgkQBsqPwI7D8pbo6gD/blPj11mdKnXl8rSOzkKR
ve1/Ht6GXS5aB1s9tQK+uJYA/3ulPb6TRIQFTmBySXo8wbaKFl3/HCqtrNsc+mV1
6eMB
=Demo
-----END PGP SIGNATURE-----

--nextPartEaPTPPl9SIuqEK_UWTg1dg--