Create/import repo to https://gitlab.wikimedia.org/cloudvps-repos/copypatrol

Is that a normal group for these? I'd have put it at https://gitlab.wikimedia.org/toolforge-repos/copypatrol (mainly because that can be easily created from toolsadmin, whereas the other needs someone else to do it from what I can see).

I'd have put it at https://gitlab.wikimedia.org/toolforge-repos/copypatrol

CopyPatrol is no longer a Toolforge tool.

I know, but there is still a tool account called copypatrol that we can use for the repository. This is how we do it for https://gitlab.wikimedia.org/toolforge-repos/wsexport /toolforge-repos/wsexport for example. It doesn't seem like many tools use https://gitlab.wikimedia.org/cloudvps-repos /cloudvps-repos at the moment.

@brennen @bd808 Is there a preference for VPS tools to have their repos under /cloudvps-repos rather than /toolforge-repos?

I'd guess that's because most VPS projects don't host their code in GitLab.

We (CopyPatrol maintainers) should not have the code under toolforge-repos since it does not run on Toolforge.
If it were up to me, the repo wouldn't be migrated to GitLab since GitLab is an inferior experience to GitHub and Gerrit. (I won't move the backend repo off GitHub.)

If you don't want to migrate the repo then it doesn't need to be, as far as I know. (I was only looking at this because I'm moving a few others and thought I could help here too.)

In T395401#11232164, @Samwilson wrote:

@brennen @bd808 Is there a preference for VPS tools to have their repos under /cloudvps-repos rather than /toolforge-repos?

There is no rule for or against. There was some discussion of removing the /cloudvps-repos grouping entirely in the past, but I think it was decided that having it exist with low adoption is fine too.

In T395401#11232222, @JJMC89 wrote:

If it were up to me, the repo wouldn't be migrated to GitLab since GitLab is an inferior experience to GitHub and Gerrit. (I won't move the backend repo off GitHub.)

I would have walked by without asking if this only mentioned Gerrit as being superior to GitLab, but I would love to know more about what you find superior in GitHub workflows to what is possible on gitlab.wikimedia.org. Maybe there is something we can fix in configuration or documentation to get to pull/merge request workflow parity for your use cases.

In T395401#11247984, @bd808 wrote:

In T395401#11232164, @Samwilson wrote:

@brennen @bd808 Is there a preference for VPS tools to have their repos under /cloudvps-repos rather than /toolforge-repos?

There is no rule for or against. There was some discussion of removing the /cloudvps-repos grouping entirely in the past, but I think it was decided that having it exist with low adoption is fine too.

xref T387062: Retire /cloudvps-repos, merge to /repos