Commit sigining and message policy

[Juraj Oravec]

Hello,

On utorok 21. júla 2026 19:42:15 stredoeurópsky letný čas Benson Muite 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?

There was a similar discussion on KDevelop mailing list a few weeks ago.
IIRC with a a result, that it is not worth it (for KDevelop).

https://mail.kde.org/pipermail/kdevelop-devel/2026-June/thread.html#63868

> 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.

I value knowledge and my own skills.

> Benson

Best regards,
Juraj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20260721/dd90e157/attachment.sig>