Again about Relicensing KDE’s Source Code

To get started with KDE development, newcomers usually first sent patches. Having sent several patches, the newcomers are typically encouraged by us (the reviewers) to apply for a KDE contributor account. This application includes the question of “who encouraged you to apply for a KDE contributor account”.

Then, the KDE sysadmins contact the mentioned developers to make sure the application is valid and trustworthy.  Hence, you, as someone who encouraged others to apply for an account, get a mail with the subject “Developer account application approval […]”.

To all KDE contributors: Given you probably also were involved with getting other contributors involved with KDE, please follow these steps:

  1. Filter your KDE mails for “Developer account application approval”
  2. For each contributor, get the contributors commit name (you can look this up on > Prople.
  3. Check, whether the new contributor added him/herself to the script.
  4. If not, please send this contributor a mail and encourage him/her to add him/herself to this script.

You really should check this, since you are also responsible for getting these new contributors commit access.

I did that with 8 contributors. 7 already added themselves within one week. Only one is not reachable by mail anymore… So it seems to work quite well.

3 thoughts on “Again about Relicensing KDE’s Source Code

  1. Hi,

    thanks for another heads-up. I already noticed the re-licensing efforts some time ago but did not pay much attention as I was terribly busy with other things. Furthermore, as I only contributed some, imho, minor changes, I wasn’t sure if I should also include myself in that script.

    Thanks to your hint for looking people up via I actually realized that I also should include myself. So, great thanks for that pointer. :)

    Just in case, here is the direct link to the re-licensing page:
    I know, it is also provided prominently in the re-licensing check script but I just mention it here so it is easier to look up when reading your post.

    Thanks a lot again. I will add myself asap. :)


  2. What about the “secondary_mail_addresses” array? Do developers have to add their “secondary” mail address there? How do they know which is their “primary” mail address?

    1. The author is typically listed as “John Doe <>”. Now, if you change your mail address on and start committing with a changed mail, then you appear as different authors, which is wrong. The secondary_mail_addresses allows the script to be smart, and still find out that the committer is the same person.

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top