Co to automaticky generovat, a umožnit správcům změnit?

Thanks @Addshore. Guessing getWatchlist() is the bottleneck here?

In T167375#5548708, @Dzahn wrote:

@Jseddon Is this currently stalled on your end?

No reply to my message despite being active, closing.

I feel there has to be something simpler to accomplish this, but...I was unable to find it. Advices welcomed!

Thanks @Tgr and others!

Simply processed archives as well, see https://docs.google.com/spreadsheets/d/1JLWiyRgmgRpvCpiZoBMd_Iv3X3AatEaojofEUPurhj0/edit#gid=1472119880.

Hello, since I'm too lazy to do the auditing manually, I wrote a small script for that (https://github.com/urbanecm/growth-mentorActivityAudit). If used at non-Czech wikis, it would need some tweaks (detection for questions at line 26 and signatures at line 11), but that shouldn't be too hard.

Not sure if we should add "like changing the mentor" to that message. @Catrope @kostajh @Tgr What do you think?

On it

Here you are.

There's not really a maintenance script we can use on this one, but tagging with Wikimedia-maintenance-script-run anyway for lack of better tag.

maybe @CommunityTechBot can do this for us?

Why do we need that, if I may ask?

Per https://wikitech.wikimedia.org/wiki/Password_reset, one of ways you can prove your identity is to put a file at a bastion. Could you put a file at the bastion host, referencing this ticket, please?

In T213287#5815704, @Xqt wrote:

In T213287#5815653, @Dvorapa wrote:

First phase announced in mailing lists and tech news

Did you? Didn’t received sth
Found it but why I didn’t received that mail from mailing list?

I spent few hours playing with the interface, and I'm now satisfied with its average performance. @Tgr explained in ambassadors' chat why the results are worse - the API link we were playing with was giving top ten matches, randomized in order, while homepage has top 250 matches, randomized in order. That's always going to be worse. Checked "Czech", please let me know if I should do anything else.

In T183549#5776463, @Zoranzoki21 wrote:

Arbcom wikis should be in own arbcom dblist and problem resovled :).

+1 to Amire80.

No, I believe @Tchanders answered everything.

@MarcoAurelio asked me to look into the logs, and I found TranslationNotificationSubmitJob does its work, but can't find anything
for TranslationNotificationJob. I grepped JobExecutor.log, and only TranslationNotificationSubmitJo found as well.

I get it, but how can it be relevant to the fact I can't type in that editor?

The work is done - will be fully working later today when wmf.15 is everywhere.

I'll have a look into this.

Testing few random topics from T242400#5796914 to compare and it looks to work fairly well, except for Geography (articles are related to the universe rather than to geography) and few other topics. Seems it's due to my seed articles being poor there, I'll play a bit and change them.

This isn't a security vuln, but intended.

But they're not - if you want to push for doing that, start an on-wiki discussion. I beliee it is better to have it done in an standard way. Also, I can't recall a page in MediaWiki namespace with global effects.

I created it in same way as https://meta.wikimedia.org/wiki/Spam_blacklist and https://meta.wikimedia.org/wiki/Title_blacklist.

There's https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Move_files_to_Commons#How_it_works - maybe that can be considered too?

In T237253#5782374, @Ah3kal wrote:

Hello, thank you for proceeding to the rename. It seems though that the old name "Βιβλίο" is not kept as an alias. Could you please do this? Thank you.

Thanks @abi_!

Okay, closing to hide it from my dashboard. Feel free to re-open once you need a followup analytics!

Is there anything else I can help you with, or can we close this task?

Hi, since I discovered that it might be caused by simply wrongly picked articles. To test that theory, I played with Special:Search and changed the list of articles for arts in https://cs.wikipedia.org/w/index.php?title=MediaWiki:NewcomerTopics.json&diff=prev&oldid=18036160. Looks much better, out of first 10 articles, 9 are okay.

Per @MMiller_WMF's request, I'm adding some other topics:

I'd like to hear @Jdforrester-WMF's comment at this one.

Selected arts and got the following:

In T242400#5794412, @Tgr wrote:

I'm thinking we should have some kind of debug mode that returns more details about why those tasks got selected (for the morelike backend, that would probably be in the form of links to the CirrusSearch debug dumps for the component queries - those dumps show what words were used for the morelike match, with what weight), plus the English Wikidata title/description of the article if available, to make it easier for non-speakers of the language to debug results.

Hi, you can mock the methods with https://docs.python.org/3/library/unittest.mock.html, and assert the methods are called as expected.

In T242157#5790000, @Lokal_Profil wrote:

In T242157#5785171, @Urbanecm wrote:

Maybe we can add the deprecation to the tech news, or even massmessage technical village pumps with a special message, warning all bot maintainers that Python 2 is to be depracated soon? I can do either thing for you. I can do a second analytics after a month (?) and email bot maintainers who still show at the list.

I think this could be useful, especially if combined with a link to some general info about how to migrate (both as a script user and as a script writer) and a link to a partilly filled out new task template for requesting support (for migrating specific bots). Maybe set up a temporary subproject to Pywikibot for the migration tasks?
Same e-mail should also go out on the pywikibot list.

In T242157#5785695, @Xqt wrote:

• surprising: Didn't expect that highly usage of Python 2 after 8 months of FutureWarning

Also surprised but I would expect a bunch of them to be regularly run cron jobs where nobody looks at the logs unless it crashes. As the co-maintainer of one such bot I know we don't (and when I do look at the logs I filter out FutureWarning 🙄).
@Urbanecm If not too much work it would be interesting to see what the percentage distribution looks like for number of users (alternativet named scripts) rather than requests (just to get a feel for if 2.7 is dominated by a few large users or if it's simple scripts run by many small volume users.