@zeljkofilipin , @FDMS: Could you please review this?

It works OK now, thank you for working on this in the weekend.

@leila, I've just seen the survey myself. The text is translated, but the buttons are not. I think something went wrong with exporting the latest translations.

@leila : I updated the translation for Visit survey to use the same terminology as the rest of the translations ("chestionar"). I would appreciate it if you could re-deploy the translations.

{{done}} https://ro.wikipedia.org/wiki/Wikipedia:Cafenea#Chestionar_pentru_cititori

Romanians my age don't normally speak Russian. I kind of find this assumption offensive, especially since I have a babel box on my user page.

In T165540#3337819, @TheDJ wrote:

Eh. Markdown is like the defacto standard throughout the development world atm. (pretty much because it IS still readable even as pure text). Not only in Github, but also in Gitlab, phabricator etc. And lets not forget that we already use it all over the place.

I am personally against using the markdown (and implicitly the .md extension). The code is not maintained in Github, gerrit does not implicitly display markdown and having some weird syntax (however well-known) decreases the readability of the file in command line. I would much rather have it in plain text. With extension or not, that's bikeshedding.

Wikitext, since I need the markup. You can see what I'm trying to achieve at https://ro.wikipedia.org/wiki/Pagina_principal%C4%83 , under the heading "Conținut recomandat". It's the introduction of featured articles, processed using Lua in a very similar way to this extension. The same code is used in several portals to display the article of the day. These are not "classical" extracts, but longer ones, up to several paragraphs, which makes it dull to display without any links to other articles.

I can confirm that uploading a corrected file solved the generation.

@Jdlrobson, we should apply the same algo as for HTML extracts (i.e. no templates, markings do not count towards the number of characters from what I can determine). The idea here, if I get it right, is to obtain a short overview of the article to display in search results and articles list.

Presentation held in the demo session

I haven't seen this in a while. I think it can be closed if @XXN Hasn't seen it either.

During the hackathon we were able to implement a normal bot, as well as a Telegram bot (@clco_tester_bot)

Haha, did a patch myself, but gerritbot did not catch it: https://gerrit.wikimedia.org/r/#/c/354714/

@LegoFan4000 , can you try setting max_retries in user_config? The default seems to be 25, but considering the increasing timeout, it will probably seem like forever (around 43 minutes)

In T153315#3112275, @Whatamidoing-WMF wrote:

In T153315#3004592, @dialmove wrote:

Nice hypothesis you have there. How are you going to test it? How will you test that it matches the expectations of users who enter the Wikitext editor directly? (Which I'd estimate is a majority of experienced Wikipedia editors, the same ones who currently use the classic editor)

That's the $64,000 question, isn't it? I'm not an expert, but it's obvious to even me that this kind of test could be heavily influenced by anchoring and similar effects. You and I have the old wikitext editors as our anchor (as did the editor who formatted the template syntax that you copied), but new editors don't.

It's finally working for me too (no 502, I still need to stop the server on the main account).

I had the same issues in RecentChanges. Do note that while disabling categorisation works, disabling advanced recent changes (aka grouping by page) also makes the problem go away.

Actually, I tagged them just like @Milimetric :)

I've done updates every 2 weeks so far, but there was no progress since 4/6. But I thought there were 5K changes to review? If there are less than 4K (3650?), perhaps that would encourage people to contribute. We've been trying to decode http://labels.wmflabs.org/campaigns/rowiki/48/?campaign=stats , but the docs are not really enough.

Since this bug was submitted, we also have wikidata to worry about, with still more js that can crash a phone. Is there any chance this could be prioritized? Since most people seem to belive the user should be redirected to the mobile version, perhaps it's a configuration issue instead of a software bug?

I was able to make it work after stopping the server on my main account, but now I'm getting a 502 error when accessing https://paws.wmflabs.org/paws/user/Strainubot. Apparently there is an issue with accounts with the same prefix.

@yuvipanda, I get the same error as @Info-farmer on starting the server for my bot account. This is quite annoying, as most wikis require a bot account for pywikibot. I tried logging out and in, different browser&computer etc. I even removed the app from the wiki settings and then re-authorised it, but no change. According to stackoverflow, the 404 on starting the server seems to indicate an issue starting the VM.

Does this proposal mean that the MediaWiki translations will also go away? There are cases when the software is translated at translatewiki in a generic way, which should make any 3rd pary user happy, while on Wikipedia we adapt it to Wikimedia tools and local customs. How will those be treated in the future?

Since this is such a disputed feature, perhaps an option would be the way out? As for the indication of the end, perhaps another image (such as a double arrow) would be enough?

So, I fixed @Kosson's commit to use block-level elements (e.g. imbricated divs). It might be just me, but I think the indentation looked nicer. Would it be enough to add a new class with margin-left: 1.6em for the outer element?

@Xqt , from a wiki point of view, the new behavior is correct: when the category redirects to a page from another namespace, an error is shown, but the category is still included in the "Redirected categories" tracking category. It is also in accordance with the behavior of page.isRedirect, where no check is made.

Verified, I think this can be closed now.

This came up twice in the last week, so I guess it will become more of a problem as more users start editing WD.

Yes, I agree, the error is not the object of the bug, only the fact that the error message is bilingual.

Thank you, that great news, it means that we'll be able to upgrade {{coord}} to maplink soon.

@JGirault , I mentioned above that this is linked to our version of Twinkle (you need to enable the gadget to reproduce) and that I would appreciate any suggestion on what is exactly going wrong - I just can't understand how can Twinkle affect that particular code - there is nothing called "externals" or "fetch" in either of the Twinkle scripts. I also tried looking at the up-to-date TW source to see if I could find something to fix this.

Further investigation showed that this is caused by our version of Twinkle. I am leaving this bug open in the hope that I can get some help on how they interact causing this. The backtrace does not seem to involve Twinkle at all, so I must be missing something. I am hoping that the Kartographer team can indicate what exactly goes wrong in their code so I can use that information to debug Twinkle. Thanks!

This seems specific to ro.wp. I took the example from [[:mw:Help:Extension:Kartographer]] and tested with it on both mw.org (worked) and ro.wp (did not work).

Now, there is one more available :)

@borisfba implemented this at https://www.mediawiki.org/wiki/Module:ImageUtils

Not only can such a measure be worked around, as Krinkle described, but I suspect it would encourage further "leaking" of sensitive JS into other namespaces, just to ensure the edits don't showup in RC. On smaller wikis with low manpower bot edits that appear in the RC are frowned upon (because they seem to "steal" the attention from vandals) and risk raising useless frictions.

@DannyH , what's the ticket umber for making this the default?

@Peter , are you interested in mentoring this task? This was a request from our (ro.wp) community and I would love to see this listed in GCI, but I don't have the know-how to mentor it.

Since backwards compatibility will be broken anyway, the question is if we should keep the extra code that handles older versions of Wikibase. Is there any data on the number of Wikibase installations out there?

@ssastry, I can reproduce it reliably on FF 49 on Windows, but I expect it to reproduce in any browser. I think the trick is to edit the page in Visual Editor, change something anywhere on the page, then move to wikitext editor. If no change occurred, the switch is almost instantaneous, which makes me suspect that the text is loaded from the database instead of being converted from the version in Visual Editor.

Not sure why the bot did not pick it, but here is the review: https://gerrit.wikimedia.org/r/#/c/321095/

Thanks for the feedback! I decided to publish the tasks here because it's easier for the community to follow. I'll move them in bulk to the platform in the next 10 days.