wmopbot can be parted with !part by any of the ops in #wikimedia-ops

It probably got replaced with the bot which means it will be a patchset to action

Lets just do it, and then see if anyone complains.

With the lack of context about what PLbot is/was, I'm assuming you are talking about the bot on WikiData Wiki (https://www.wikidata.org/wiki/User:PLbot)?

Please file separate bugs or issues as separate tasks so its easier to keep track of issues

not a issue with the extension, only the local wiki config

Note there is/was some work to move to the DB model for more config compared to the files, T239355: Deprecate phabricator's fixed_settings.yaml (in puppet) and just use phabricator's built in configuration tools

Isn't this what the Beta-Cluster is for? or the docker enviroments?

Please link to the community consensus for the change to be actioned.

Fixed, It's been renamed in the past so I suspect it was hit with T224662: After renaming a project in Phabricator, its /tag/projectname URL ends up as a 404

I'm bolding declining this for now, We've turned issues off on all our mirrored repos (at least in the WMF org account), I believe the only uses of GitHub issues is the research repos that choose to use them

If GitHub choses to use the repo about/description slug to populate a <title> </title> instead of the repo name or mixing them together, seems a upstream issue.

I suspect this is a Upstream github issue…

If you email T&S via ca (@) wikimedia.org referencing this Phab ticket, they can check to see what email is in the database for the referenced account and assist with password resets

That's currently not always the case.

CSR tag should on a proper CSR task (not that they are actually getting reviewed)

I'm suspecting this may be T226797: CentralAuth login session and auto-login no longer work across wikis in Safari and Firefox

It looks like @Magnus tracks tasks relating to Baglama2 over on BitBucket (https://bitbucket.org/magnusmanske/glamtools/issues?status=new&status=open), There looks to be already a task open for the issue https://bitbucket.org/magnusmanske/glamtools/issues/96/the-tool-baglama-2-is-not-showing-data

If its been broken for ~3 years without much(/any?) complaints, Wouldn't it be better to remove it so we don't have to main the tech debt form it?

@rook If you want to attempt to self serve and generate a patchset, The file to update is channels in labs/tools/wikibugs2, More instructions can been seen at https://www.mediawiki.org/wiki/Wikibugs#Source (And the following Config. Channels page section)

This task should be spilt in two as its relating to two different things, then data can be pulled from WMF wikis to see how utilized they are

In T336357#8844321, @BTullis wrote:

The Bishopfox wikitech account I created yesterday will just be dormant, since we don't have any readily available process for deleting or renaming it.

Its a much wider scope of works above compared to the simple quick fix, but have we ever looked at alternative ircds lately? From vague memories a few years ago, Inspircd can do everything our custom patches did as part its core functions and module setup so wouldn't need to (re)build packages to make changes and jsut action everything via its config files

but not exposing that information is still an improvement.

What DNS documentation? I doubt very much of that is within scope for mwwiki (https://www.mediawiki.org/wiki/Project:About#What_MediaWiki.org_is_not)