Wikimedia-Site-requestsPublicDiscussion between users working on #Wikimedia-Site-requests and #Wikimedia-Extension-setup
@Dereckson When you created new wikis last week, most of the configuration patches finally merged were missing configuration values (logo paths, $wgNamespaceNames, etc). I think those were lost in the middle of rebases, etc. I have uploaded patches to try to fix them. Also, I don't think gorwiki should've been created at all with no MessagesGor.php existing at all. Now we should translate and fix the whole lot of namespaces there and hope no conflicts arise when running namespaceDupes.php. Regards.
Hello. Not filling a task because I have not confirmed the issue in depth, but I can't see the logo at hu.wikiquote. I have tried with reloading, refreshing and skin change w/o success. Maybe something is not loading from my side or there's a general issue. Thanks for your help. Regards.
I'm really not sure if we can proceed T196732 (probably will include creating another set of copy upload domain whitelist for arwiki and manage its content according to arwiki's EDP, I'd oppose dropping whitelist at all, even it's limited to trusted on wiki per the task linked). I'd like to see opinions of others.
FWIW that user right should be upload-by-url (T181506: `upload_by_url` user right should be `upload-by-url`). Renaming it is easy, but requires creating a deprecation variable/period and I don't know how to do that, otherwise I'd have attempted it myself :-)
The swift back-end will copy the file. And that's something not really reliable, infrastructure should be configured to allow logical references to a physical file. That's something for ops to implement (we've somewhere a task for that, probably as a blocker for the upload.wikimedia.org whitelist task).
I am not aware of such existance nor familiar with their EDP (I cannot read a word of Arabic). But if the primary use is to transfer files from/to Commons; arwiki is in the set of beta testers for FileImporter/Exporter extension so they can do that already; and as such I'd say to decline. Thanks.
I've found T129087. Do we really allow sysops to grant pseudobots to _everyone_? Their rationale seems to be "avoid need for a bureaucrat". https://bn.wikisource.org/w/index.php?title=%E0%A6%AC%E0%A6%BF%E0%A6%B6%E0%A7%87%E0%A6%B7:%E0%A6%AC%E0%A7%8D%E0%A6%AF%E0%A6%AC%E0%A6%B9%E0%A6%BE%E0%A6%B0%E0%A6%95%E0%A6%BE%E0%A6%B0%E0%A7%80%E0%A6%B0_%E0%A6%A4%E0%A6%BE%E0%A6%B2%E0%A6%BF%E0%A6%95%E0%A6%BE&group=flood
We have some other cases (well, a lot of other cases). Still, I don't think that's a good idea, especially when it is being abused (see https://bn.wikisource.org/w/index.php?title=%E0%A6%AC%E0%A6%BF%E0%A6%B6%E0%A7%87%E0%A6%B7:%E0%A6%AC%E0%A7%8D%E0%A6%AF%E0%A6%AC%E0%A6%B9%E0%A6%BE%E0%A6%B0%E0%A6%95%E0%A6%BE%E0%A6%B0%E0%A7%80%E0%A6%B0_%E0%A6%A4%E0%A6%BE%E0%A6%B2%E0%A6%BF%E0%A6%95%E0%A6%BE&group=flood).
We don't believe we are intentionally misusing the flag, although before I was a sysop I did notice User:Jayantanth forgetting to remove it from himself once he was done using it (https://bn.wikisource.org/s/1vg#বট_ফ্ল্যাগ). As for those with the flag at present, all are bot accounts save for Titodutta, I can remove the flag from his account and ask him to create a bot account so his manual edits aren't also hidden from RecentChanges.
Well, by abusing a "pseudobot" flag I mean https://bn.wikisource.org/wiki/%E0%A6%AC%E0%A6%BF%E0%A6%B6%E0%A7%87%E0%A6%B7:%E0%A6%85%E0%A6%AC%E0%A6%A6%E0%A6%BE%E0%A6%A8/Bodhisattwa-bot and other bot accounts. Those accounts are full bots, not pseudobots. Pseudobot is a human making a lot of edits, maximally semiautomatically, not a fully autonomous script. It is my opinion, I'd like to hear your.
Also, general reminder that while we're operating in the secondary data center, per DBA request, no new features can be deployed to the wikis that creates tables/alter schemas during this period, without previous approval of DBA people (this is an extract of the request as posted on wikitech-l). Regards.