Commit sigining and message policy

[Christoph Cullmann]

Hi,

On Tuesday, July 21st, 2026 at 19:43, Benson Muite <benson_muite at emailplus.org> wrote:

> 

> We are trying to come up with contribution guidelines for Mankala, a
> project we would like to bring to KDE. There is a commit policy
> available at:
> 

> https://community.kde.org/Policies/Commit_Policy
> 

> a) Is it ok to ask for signed commits for a project?

I think requiring that is as for KDevelop a no-go.


> b) If someone has used a coding agent, what is the best way to
> acknowledge this?  Should the commit message be co-authored, or contain
> an acknowledgement?  A number of KDE projects do not accept AI generated
> code (primarily due to licensing and ethical concerns), but others do.
> Of those that do, a few indicate co-authored and the name of the AI
> tool/agent - the commit policy was written before the use of AI agents.

There is an explicit statement for that in our policy:

Do not indicate code manipulation tools have authorship: Authorship is for humans, not tools. Code assistants and such must not be described in commits using tags like "Co-authored-by" or similar. Nor must they be listed as primary author.

Greetings
Christoph
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 343 bytes
Desc: OpenPGP digital signature
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20260721/4dcf5029/attachment.sig>