Git migration - website moved

[Ben Cooksley]

On Sat, Jun 14, 2025 at 8:32 AM <eo10nd at duesdings.de> wrote:

> Hi,
>

Hi Nico,


>
> > This has the unintented side effect that people that could commit
> directly to
> > their subteams area in SVN can no longer direct commit because git
> websites
> > are write protected for most people.
> >
> > For now please create Merge Requests and I will try to merge them ASAP.
> >
> > @sysadmin any idea how we can fix that so those who could commit to the
> l10n/
> > teams can still do it now?
>
> I'm not a sysadmin but generally what you (or the sysadmins) maybe can
> do is to allow everyone to merge Merge Requests into the master branch,
> but activate that a review by a code owner is required. And then you can
> create a CODEOWNERS file and write down the teams on the paths of their
> team pages.
> See https://docs.gitlab.com/user/project/codeowners/reference/
>
> You could also use push rules to limit teams to only change their
> directories, but it will probably be a bit more complicated than
> CODEOWNERS. Then they could even push directly to the master branch.
>

Unfortunately both CODEOWNERS and Push Rules are features limited to the
Premium and Ultimate versions of Gitlab (ie. the proprietary Enterprise
Edition).
They are therefore not available to us.


> Or you allow write access to the whole repo for all teams and intervene
> if the trust is violated.
>

That has generally been the KDE model for handling instances like this.

If technical needs dictate, we can add some protection rules in our hooks.


>
> Cheers,
> Nico
>
>
Thanks,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20250614/2bcef0f6/attachment.htm>