https://phabricator.wikimedia.org/source/blubber/

https://phabricator.wikimedia.org/diffusion/BECS/

should those be deactivated in Phabricator? (there is deactivate, disable publishing and delete)

I've marked most of the items as "n/a". I'll start doing the rest now that blubber is fully on GitLab.

Seems like a task template specifically for migration from Gerrit to GitLab might be in order.

Change 844528 had a related patch set uploaded (by Dduvall; author: Dduvall):

[integration/config@master] zuul: Remove blubber jobs

https://gerrit.wikimedia.org/r/844528

Change 844529 had a related patch set uploaded (by Dduvall; author: Dduvall):

[integration/config@master] jjb: Delete blubber jobs

https://gerrit.wikimedia.org/r/844529

Change 844528 merged by jenkins-bot:

[integration/config@master] zuul: Remove blubber jobs

https://gerrit.wikimedia.org/r/844528

Change 844529 merged by jenkins-bot:

[integration/config@master] jjb: Delete blubber jobs

https://gerrit.wikimedia.org/r/844529

In T317820#8330773, @dduvall wrote:

It's not clear to me how to archive a Diffusion project

Members of acl*sre-team or Diffusion-Repository-Administrators could use https://phabricator.wikimedia.org/source/blubber/edit/activate/ and https://phabricator.wikimedia.org/diffusion/BECS/edit/activate/

Phab project description / code repo field at https://phabricator.wikimedia.org/project/edit/2812/ should also get updated?

and I don't have access to modify the GitHub mirror.

In T317820#8330773, @dduvall wrote:

Done with everything except for GitHub and Diffusion. It's not clear to me how to archive a Diffusion project and I don't have access to modify the GitHub mirror.

GitHub automagically mirrors, so whatever you did on Gerrit trickles out there: https://github.com/wikimedia/blubber#readme

We can also archive it on GitHub. I wonder how we now stop mirroring from Gerrit and move mirroring to GitLab?

In T317820#8332255, @thcipriani wrote:

GitHub automagically mirrors, so whatever you did on Gerrit trickles out there: https://github.com/wikimedia/blubber#readme

We can also archive it on GitHub. I wonder how we now stop mirroring from Gerrit and move mirroring to GitLab?

I would think it would be on a repo by repo basis in the settings. Who has access to the wikimedia GitHub org? Seems like someone on our team should since we're the Gerrit/GitLab folks at WMF.

Mentioned in SAL (#wikimedia-operations) [2022-10-20T15:55:58Z] <mutante> phabricator (diffusion) - clicked "disable" and then "deactivate" on Blubber diffusion repo. it's now "inactive, publishing and syncing has been disabled https://phabricator.wikimedia.org/source/blubber/ T317820

In T317820#8332255, @thcipriani wrote:

In T317820#8330773, @dduvall wrote:

Done with everything except for GitHub and Diffusion. It's not clear to me how to archive a Diffusion project and I don't have access to modify the GitHub mirror.

GitHub automagically mirrors, so whatever you did on Gerrit trickles out there: https://github.com/wikimedia/blubber#readme

We can also archive it on GitHub. I wonder how we now stop mirroring from Gerrit and move mirroring to GitLab?

Usually we remove the repository from GitHub. This one has at least one issue filed though: https://github.com/wikimedia/blubber/issues/1 so we probably want to keep it or move that to Phabricator then the repo can be deleted.

For repositories hosted on our GitLab, I am not sure we need to replicate them back to GitHub since https://gitlab.wikimedia.org/repos/releng/blubber seems to give a good exposure to the world wide web. If somehow a repository requires replication to GitHub for running 3rd party integrations, that is to be determinated.

In T317820#8333057, @hashar wrote:

For repositories hosted on our GitLab, I am not sure we need to replicate them back to GitHub since https://gitlab.wikimedia.org/repos/releng/blubber seems to give a good exposure to the world wide web. If somehow a repository requires replication to GitHub for running 3rd party integrations, that is to be determinated.

I think this assumption is worth a more public discussion for repos other than Blubber. GitLab supports push mirroring. Having a consolidated view of commit activity across many Wikimedia related git repos visible on a user's GitLab profile is actually a benefit for those members of our community who take advantage of it. GitHub mirrors for MediaWiki repos have long been advertised via Extension detail pages among other locations. Composer package updates are currently automated using GitHub hooks. The community might decide that we no longer want to be associated with GitHub, but until that is the case I think it is reasonably easy to continue to mirror repos to GitHub after they have been moved from Gerrit to our local GitLab.

It's also likely to be true that people care about seeing their contributions mirrored to GitHub for reputational / career / social standing purposes, since evidence of participation there is treated as the de facto real-world proxy for having done open source work in a bunch of contexts.

I don't like this state of affairs, but it's worth acknowledging that people may have reasons to care.

In T317820#8333031, @dduvall wrote:

I would think it would be on a repo by repo basis in the settings. Who has access to the wikimedia GitHub org? Seems like someone on our team should since we're the Gerrit/GitLab folks at WMF.

FWIW, it is not on a repo-by-repo basis. Gerrit actively pushes (see replication settings for gerrit in puppet.

Also, 🎉 you're now an owner in the GitHub org.

+1 for keeping mirroring to GitHub.

We don't have mirrors for every repo on Gerrit. There was one manual step to mirroring—the repository had to be manually created in GitHub first. After that, mirroring worked automagically.

There are two problems with mirroring from GitLab:

1. How to do it
2. How to stop Gerrit from doing it: does archiving a repo in Gerrit mean it's still mirrored from Gerrit to GitHub if the GitHub repo exists? If that's the case: can we modify replication settings to stop it?

I made T321597: Mirror repositories hosted on our GitLab to GitHub as a new home for my thread jack of this ticket.