I would like to add that the consensus on it.wiki is to have all appointed admins of the ML to have an NDA signed. WMF ones will do.
The 3 elected admins all have signed an NDA (VRT members or CUs).

Hi, Italian Wikipedia CUs would like to test Client Hints as well, when it will be deployed on the first production wikis.

Community consensus can be checked at https://nap.wikisource.org/wiki/Wikisource:Bar#Edit-in-sequence
We're eager to start beta testing!

@dmaza Exporting the EPUB from that page on nap.source, I still have the same error message. Because of the encoding L'Eneide I suppose.

The dumping ground will be useful in fact, because it is a starting point to perform triage on the incoming tasks (that's the purpose of Triage Meetings).
Actually the new tasks are put in the Backlog without checking their priority, or feasibility. I agree that the label #all-and-every-wikisource is quite generic: every task with that label should have at least a second, more specific, one.

As a side note, I strongly doubt that "All feedback volunteers had to share was positive. [iv]".
Here it's kind of neutral.(NB: please update the links above: the pages on it.wiki have been moved)
A wider discussion is happening here on it.wiki, and all the comments are far from enthusiast.

Shall we change the name on Commons as well?
See https://commons.wikimedia.org/wiki/MediaWiki:Grouppage-OTRS-member
The idea would be to move the page to MediaWiki:Grouppage-VRT-member and to change the text to "Commons:Global VRT permission", right?

Hi @Samwilson, I cannot reproduce it either. Very probably, the usage of OpenSeadragon for the Page image viewer had some positive side effect wrt this task T288141.
Let's close it?

yes it is! the scripts examples in particular... Thanks

nothing has been solved yet

The text is set to its default message:

@Alex_brollo please check the last line of @Soda 's message above, where there's a hint about some API interface.
Btw, in order fix our Javascriptsto, I've used the following code to display a new image in the (openseadragon) canvas:

image.onload = function() {
	canvas = document.querySelector('.openseadragon-canvas canvas');
	var ct = canvas.getContext("2d");
	ct.drawImage(image, 0, 0, canvas.width, canvas.height)
}

@Xover Can you suggest a place (can be phabricator as well) where users can interact with more expert ones to discuss such technical issues? I reckon that this is a specific case where such help is needed and requires a longer discussion.

@Aklapper nope, but the deployment seemed stuck. I reverted it to Resolved. Sorry for the inconvenience :)
@Soda Thanks a lot for your comment; actually the issue is with the image inside the .prp-page-image that is hidden when editing the page. I've fixed this special case with display: inline;, not knowing what this will affect in OpensSeaDragon. But probably here it's not the right place to discuss about a specific gadget that was broken.

As this new feature has been rolled back (due to a memory leak), why not to delay de deployment until we are sure that there are no issues and that all the projects are notified of such a change? Clearly several local Gadgets will need to be corrected, and the communities need to be ready.
If there are memory issues (maybe OpenSeadragon is too greedy), Wikisources probably need a way to disable it locally. Have we thought about that?

For information, the example page provided above contains the following text:

@Cohaf @Mike_Peel Please go ahead. Mind that you'll need to

@whym : It has been mentioned in one of our meeting, if I remember correctly. The answer is no, this 'otrs' in the url doesn't need to be changed.

I am moving the talk pages by hand. Please helm in double checking it, as well as eventual double redirects. Thanks.

The issue depends on the special characters in the page name.

@Keegan @AntiCompositeNumber
Here's the new version:
https://commons.wikimedia.org/wiki/File:Wikimedia_VRT_RGB_logo.svg

@Keegan
Logo following the Wikimedia visual identity guidelines:

• https://commons.wikimedia.org/wiki/File:Wikimedia_VRT_logo_-_vertical.svg

If we need a colored version (which was the visual identity until 2018 I believe), like https://commons.wikimedia.org/wiki/File:Wikimedia_OTRS_logo.svg, it can be done.

Looks complete now.

English text updated. Translations are pending.

Waiting for the categories to update, e.g. https://meta.wikimedia.org/wiki/Category:OTRS_templates/Translations

@Urbanecm volunteered to rename the group (https://meta.wikimedia.org/wiki/Special:GlobalUsers/otrs-member) to vrts-permissions.
@Keegan: when the renaming can take place? Shall we fix it in our next meeting?

@Urbanecm It is possible to move the talk page as well, and the other subpages? Thanks
See https://meta.wikimedia.org/wiki/Special:PrefixIndex/Talk:OTRS/ and https://meta.wikimedia.org/wiki/Special:PrefixIndex?prefix=OTRS

There is an issue in moving > 500 translated pages.
Waiting for T284118 to be solved.

In T284116#7127994, @DannyS712 wrote:

@Quiddity I think the issue is that the target page exists, regardless of if it is in the page translation system - I've deleted it, can you try again?

Template:PermissionOTRS moved on Commons to Template:PermissionTicket (leaving a redirect).

• Translations should be revised
• Doc partially modified, waiting for categories to be changed

Just to complete the answer above. As said in https://meta.wikimedia.org/wiki/Talk:OTRS :
The VRT name is already adopted by the English speaking community (see [[Wikipedia:Volunteer_Response_Team]] on en.wiki), at least since October 2009. Of course we intend that other language communities continue to use their own names, if they wish. But not "OTRS" or "Znuny" because they are trademarks we do not own, and "would become obsolete if we ever started using a different ticket management system" (cf. https://en.wikipedia.org/w/index.php?title=Wikipedia:Volunteer_Response_Team&oldid=318124031).

First phase of replacing text has been completed (unless some pages were missed). I.E. the OTRS mentions have been replaced with VRTS (or VRT), and the pages have been marked for translation.

@Jarekt thanks

@bd808 Yes, there is wide consensus among the admins to activate the bridge. Thanks

Here we are:
https://nap.wikisource.org/wiki/Wikisource:Bar#SUBPAGES

Come on! All the Page namespace of all Wikisource projects have subpages: it's the very way they are ordered. If the magic word {{SUBPAGENAME}} does not work, a lot of links fail.
Probably they forgot to set the flag when they created the project... I should have logged it as a bug rather than a request.

@Mpaa transferbot.py doesn't check the ql of the pages. The error is arisen by the API when you try to write the text.

In T173385#5811262, @Mpaa wrote:

In T173385#5809505, @Ruthven wrote:

@Mpaa Well, the same happens without the option ql=4.

ql=4 is not the matter (it is just a filter on the pages the script should use), the 'Validated' code is inside the wikitext of the page.
Or you mean that there are other pages with lower quality level where you have the same issue?
If so, could you post it?

Hi all, sorry to reopen this, but I think that problem I encountered is related.
I am using delete.py under PAWS. I applied the patch above, but I obtain the same result: not being able to "undelete" files in a project where I am sysop.

@Mpaa Well, the same happens without the option ql=4.
@Tpt there is any workaround?

Actually I tested it with the bot account and the sysop account, both resulting in the You are not allowed to change the proofreading status of this page. error when creating a page in ns:Page.
Thus it seems that it is not possible to create or modify ns:Page using pywikibot?

Thanks a lot @Dcljr !

After several weeks of testing, I'm rather sure that it's an OS X issue. But I have no "autoreplace" option activated, or anything similar, apparently.

@Aklapper For instance, it happened on the following pages:

• it.wp Using Brave browser Version 0.66.101 Chromium: 75.0.3770.142 (64-bit) on OS X version 10.13.6, MediaWiki: 1.34.0-wmf.22 415c14d 13:21, 16 set 2019
• it.ws Using Safari browser Version 12.0.1, on OS X version 10.13.6, MediaWiki: same version as above, but happened with older versions as well.
• en.wp, not logged in, in order to rule out gadget interference, same Safari browser and MediWiki version as the former entry.
• NB: I tested under Windows 10 today (Firefox, IE), but wasn't able to replicate the issue. But, as long as it happens randomly, I cannot be sure that it's an OS issue.

@Dcljr Thanks, but never mind: I never liked too much the bureaucracy, and we're doing fine with the virtual namespace Wikisource:Prugetto ; see: https://nap.wikisource.org/wiki/Wikisource:Prugetto:Tecnicismi.

@Dcljr It is possible that I've misidentified the problem (@Alex_brollo Forse tu puoi aggiungere qualcosa in più), but, yes, to obtain this result it seems that we need a namespace alias.

There is a problem with the namespaces. Actually, some names were written in the local language (Neapolitan) instead that in English for the canonical field. This brings some importation errors, and some other general issue.

@Ladsgroup It's the task we talked about, remember? ;) Thanks

In T212883#5418407, @MarcoAurelio wrote:

@Dzahn Is Nnapulitano correct? {{#language:nap}} returns Napulitano.

The wiki is now online. T210752

In T212881#5341855, @Reedy wrote:

I note new wikis were never created in a timely fashion anyway...

Do you mean that it's impossible to create new projects?
In alternative, it's possible to create a project with a working version of Mediawiki? I mean: in the past projects were created (at least in 2003). Why it's not possible to create them in the same way as before, using the same version of the software? (sorry if the question sounds silly)

Just reporting some failing export, which occurs pretty often now. There are really no solution to this?

The error still appears (502 Bad Gateway) - and several users pointed at that.

It seems under control to me. There are spam emails from different sources in "Probably-spam", which is normal, and they have to be moved to "Junk" if they are really spam mails.

On the OTRS interface I set up the filter `00 spam-20190124 smtp-sortant2.phpnet.org`.
The remaining tickets have been moved to Junk.