Re: Commit to Bluedevil repo

Ben Cooksley <[email protected]>
Newsgroups gmane.comp.kde.devel.general
Message-ID <CA+XidOGhhJXMDkrseQDNSppcm_oc7X1E+SrqDZoTYHaujj5B5w@mail.gmail.com>
On Tue, Dec 9, 2025 at 5:36 AM Ingo Klöcker <[email protected]> wrote:

> On Montag, 8. Dezember 2025 17:23:47 Mitteleuropäische Normalzeit Julius
> Künzel wrote:
> > 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/88222071c80bcbcee32071e
> > >>> 2c
> > >>> 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.
> >
> > 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.
>
> Okay. So Enol is allowed to commit (translations) to svn and this implies
> that
> they are also allowed to push directly to mainline git repos. Fair enough.
> With great power comes great responsibility.
>

Correct, all KDE Developer accounts - regardless of why it is granted - are
equivalent.

The only special repositories we have are the ones in the sysadmin/ and
websites/ groups on Invent, for which access is granted on an individual
basis, as these repositories either govern key parts of infrastructure
(repo-management, dns, ci-utilities, ci-images for instance) or represent
us in the public view (all websites/)

Given their place in the software supply chain there may be changes to
packaging/ in the future.


> Regards,
> Ingo


Thanks,
Ben
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.