08.12.2025 13:12:52 Ingo Klöcker <[email protected]>: > On Montag, 8. Dezember 2025 10:02:06 Mitteleuropäische Normalzeit Konstantin > Kharlamov wrote: >> On Sun, 2025-12-07 at 02:06 +0100, Enol P. wrote: >>> I've just committed to master a change for a toolptip text in >>> Bluedevil's KCM. Revert it if necessary because I thought GitLab's >>> web IDE would be smarter enough to make a pull request instead. Sorry >>> if I missed any contributor guidelines for Bluedevil or if any commit >>> should be discussed in this mail list first. I'm just a translator >>> and my git knowledge is limited. >>> >>> The commit i've mentioned: >>> https://invent.kde.org/plasma/bluedevil/-/commit/88222071c80bcbcee32071e2c >>> 413a8f80db64947 >> >> FWIW, it's a pretty common mistake, and for this reason I usually >> disable "push" to master in project settings for projects I manage, so >> any possible commit could only go via merge-request and hence via CI. >> >> Just mentioning in case Bluedevil maintainers might want to do the >> same. > > In KDE it's usually explicitly allowed to push directly to master, but I > thought one needed to be in the KDE Developers group for this. > > It looks like Enol is in the KDE Developers group. I'm wondering whether this > is a mistake if they are "just a translator". On the other hand, there are > some translators who regularly fix typos or bad grammar in messages (Thanks, > folks!) and who should be in the KDE Developers group. > > Regards, > Ingo > I'm wondering whether this is a mistake if they are "just a translator".
The term KDE Developer is misleading. Everyone who needs/wants push access to the mainline git or svn repos (and follows the process) will become a "Developer" independent of whether they want to write code, documentation or translations. So, taking special repos such as websites and sysadmin aside, there is basically only one unified permission level on top of the default permissions every KDE account has. Cheers, Julius
