We welcome not-experienced contributors, just don’t be afraid of the many small things we might want to tweak and be patient, we all were new contributors at some point.
Use git clang-format for instance for indentation/code style.
Use git rebase, we don’t use feat() prefix, adapt to how the other commits are written.
It would be something like runners/plugin: add a remindme timer plugin
SPDX-FileCopyrightText: 2026 dcog989
We like better non-anonymous contribution, dcog989 can’t legally designate a person, so this copyright is void, and the GPL could not be enforceable.
As an IP lawyer specializing in FOSS licensing and compliance (and co-author of the SPDX and REUSE specs), I beg to disagree.
Authors are often signing their works with pseudonyms, and it’s totally fine, as long as it is possible to identify them. What’s more, an author is perfectly at their own right to remain anonymous. It is the author’s right, not obligation, to be named.
That said, the REUSE spec, which you refer to, does ask for a contact (e.g. e-mail address). The reason for this is that should someone need to reach out to the author – either licensing/copyright or technical-wise – the contact metadata stays in the file too.
Nothing prevents KDE from asking contributors to contribute using their legal name, of course.