[Wikitech-l] MediaWiki 1.31 branch (and PHP versions)

[Chad]

Hi,

I meant to send this Tuesday but I forgot.

MediaWiki 1.31 has been branched from master! You should now see a REL1_31
branch where appropriate items should be backported to.

Core was branched at 69257de17fc899c447c9f1229b6ed319bc05d316.
All extensions & skins were branched from their respective masters at about
the same time as core. I plan to cut rc.0 sometime next week.

PHP versions
The current plan of action is to leave master as compatible with 5.5 for
now. This is because Wikimedia production isn't ready quite yet. This is
being tracked at T172165[0]. We will be moving the REL1_31 branch to 7.0+
as the required minimum version. Once production is ready, we'll
forward-port this change to master. It should be a little inconvenient, but
not too terribly bad (and notably, makes life less stressful for our SREs).
In the meantime, please do NOT introduce changes to master that require
7.0+ for core, vendor, or WMF-deployed extensions & skins. Doing so will
make me sad :(

Otherwise, great job on 1.31.x everyone! I'm rather pleased with what I'm
seeing so far. Check out the workboard[1] for ways you can contribute to
getting it wrapped up (and as always, tag issues with that tag if they
should absolutely block release).

Have a fantastic weekend!

-Chad

[0] https://phabricator.wikimedia.org/T172165
[1] https://phabricator.wikimedia.org/project/view/3011/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] An update on map internationalization

[Joe Matazzoni]

This is to let you know that Collaboration Team is planning to release map 
internationalization next week for testing on testwiki [1]. When it’s ready, 
we’ll post a note to confirm. 

Meanwhile, you might like to check out the detailed post I added last night to 
the Map Improvements 2018 project board: Special Update on Map 
Internationalization[2]. It includes a lot of information on the feature's 
status, how the it will work, how we imagine it might be useful, what the known 
limitations are, etc.  I’m looking forward to getting your input on this 
challenging but important feature (the best place to leave your ideas and 
questions is on the project talk page [3]).

Yours,
Joe

[1] https://phabricator.wikimedia.org/T112948 

[2] 
https://www.mediawiki.org/wiki/Map_improvements_2018#April_18,_2018,_Special_Update_on_Map_Internationalization
 

[3] https://www.mediawiki.org/wiki/Talk:Map_improvements_2018 

_

Joe Matazzoni 
Product Manager, Collaboration
Wikimedia Foundation, San Francisco

"Imagine a world in which every single human being can freely share in the sum 
of all knowledge." 




___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Introducing Quibble, a test runner for MediaWiki

[Stas Malyshev]

Hi!

> A second advantage, is one can exactly reproduce the build on a local
> computer and even hack code for a fix up.

This is great! CI errors not reproducible locally has been a huge
annoyance and very hard to debug. Thanks for making it easier!

-- 
Stas Malyshev
smalys...@wikimedia.org

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: Replacing Tidy on large wikis (by end of June 2018)

[Subramanya Sastry]

[ Crossposting my wikitech-ambassadors post from y'day for those you 
active on different wikis. ]


Hello everyone,

TL:DR;
--
As you are aware from previous postings on this list [1] [2] [3] [4] [5] 
[6], we have been progressively replacing Tidy with RemexHtml on all 
wikis on the wikimedia cluster. As of today, about 650 wikis have made 
the switch that include a number of large wikis. We aim to complete this 
switch over on the remaining 250 wikis by end of June 2018. Another 40 
or so wikis will be switched on May 2nd.


There are a few large wikis (es, pt, uk, zh especially) that could use 
more attention addressing Linter issues so that when we make the switch 
end of June, some pages on these wiki don't render differently from how 
they do now.



Details:

I started investigating more closely where the remaining large wikis are 
with respect to the linter issues (high priority categories on the 
Special:LintErrors page) that are pertinent to these wikis. I am listing 
below results from running sql queries on quarry.wmflabs.org for these 
wikis. If you are a community member on any of these wikis, do try to 
address these on your wiki.

15 other large wikis:

See https://quarry.wmflabs.org/query/26474 for counts of linter issues 
for each of the 9 categories in the main namespace.
* es, pt, uk, zh wikis have total error counts over 10K and in some 
cases, it is usually one category which needs attention.
* vi, ro, sr, sh, ar, tr, id are not too bad but don't seem to have seen 
a lot of change which indicates that these wikis aren't looking at 
linter issues.
* fr, hu, ja, pl wikis seem to be in good shape overall. There has been 
a steady fixing of issues and I think all these will will be in fairly 
decent shape for replacing Tidy by end of June.


https://www.mediawiki.org/wiki/Parsing/Replacing_Tidy/FAQ#Simplified_instructions_for_fixing_pages 
has some summarized instructions for fixing issues in different categories


English Wikipedia:

See https://quarry.wmflabs.org/query/25665 for counts of linter issues 
for each of the 9 categories in the main namespace.


English wp has been making slow and gradual progress. I think overall, 
despite there still being ~8300 instances (not pages) that need fixing, 
enwp is in pretty good shape for replacing Tidy by end of June.


Commons:

See https://quarry.wmflabs.org/query/25693 for counts of linter issues 
for each of the 9 categories in the File (ns6), Gallery (ns0), and 
Template (ns10) namespaces.


The vast majority of html5-misnesting errors on commons seem to come 
from the use of the {{lang}} template which uses a  tag to wrap 
content. However, it seems to be extremely common to pass content with 
paragraphs into the {{lang}} template. Right now, this doesn't cause any 
visible rendering issues and could be ignored temporarily, but we 
strongly recommend fixing lang to use  or on pages which misuse 
{{lang}} this way, replace use of {{lang}} by creating a new template 
({{lang-block}} maybe?) that uses a  tag.



Some tips:
--
1. On some wikis, fixing templates usually fixes the problem. Over the 
last 6 months, I've personally spent many hours fixing 100s of templates 
on 10s of different wikis and can personally attest to the efficacy of 
that strategy.
2. A lot of the html5-misnesting errors seem to be from incorrectly 
using a  tag to wrap content that has paragraphs, lists, tables. 
In all these cases, changing them to  almost always fixes the problem.


If you need any assistance, please leave a message on 
https://www.mediawiki.org/wiki/Help_talk:Extension:Linter. Between 8 am 
- 4pm PST, you can also usually find us on IRC on #mediawiki-parsoid.


Thanks,

Subbu.
(on behalf of the Parsing team @ Wikimedia Foundation)

1. 
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2017-July/001625.html
2. 
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2017-August/001637.html
3. 
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-January/001783.html
4. 
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-February/001795.html
5. 
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-March/001808.html
6. 
https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-March/001821.html 



___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Your feedback matters: Final reminder for the Wikimedia survey

[Edward Galvez]

Hi everyone,

This is our last reminder for you to complete the Wikimedia Communities &
Contributors survey.
* To those of you who have taken the survey - thank you so much! We really
appreciate your responses.  *

*This survey is closing in less than three days on Sunday 22 April 2018.*

*If you are volunteer developer, and have contributed code to any pieces of
MediaWiki, gadgets, or tools, please complete the survey. The opinions you
share will affect the work of the Wikimedia Foundation. *






*Follow this link to take the
survey: https://wikimedia.qualtrics.com/jfe/form/SV_5ABs6WwrDHzAeLr?aud=DEV
If you
have already seen a similar message on Phabricator, Mediawiki.org,
Discourse, or other platforms for volunteer developers, please don't take
the survey twice.  It is available in various languages and will take about
20 minutes to complete.You can find more information about
this survey on the project page
 and
see how your feedback helps the Wikimedia Foundation support contributors
like you. This survey is hosted by a third-party service and governed
by this privacy statement
.
Please visit our frequently asked questions page

to
find more information about this survey. Feel free to email me directly
with any questions you may have.Thank you!Edward Galvez from the Community
Engagement departmentWikimedia Foundation*

-- 
Edward Galvez
Evaluation Strategist, Surveys
Learning & Evaluation
Community Engagement
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Introducing Quibble, a test runner for MediaWiki

[Antoine Musso]

On 20/04/2018 03:18, Pine W wrote:
> Cool. Pardon my novice level understanding of containers and devops. Am I
> correct in saying that the plan is to use Docker to improve the efficiency
> of testing for MediaWiki?

It is partly about efficiency.  We have jobs running on a pool of
virtual machine on top of the OpenStack cluster, the instances are
deleted after each build.  A software (Nodepool) takes care of the
deletion and replenish the pool by asking for new instances to be started.

The pool is fairly limited in size and rate limited since any time it
asks for too many request the OpenStack cluster gets in trouble. That
has been a source of pain and headhaches and is overall quite slow.


Docker addresses that part:
* we provide the frozen environments CI uses to run tests
* anyone can download them with a docker pull
* the Docker container is spawned at start of the build and typically
takes just a few miliseconds to start


It is also next to impossible to reproduce a CI build for MediaWiki.
There are too many requirements:
* the image used to spawn the virtual machine, which is not publicly
available
* Parameters being injected by the workflow system (Zuul)
* Jenkins jobs written in yaml (integration/config)
* Shell scripts in a git repo (integration/jenkins)

Quibble addresses that second part: it aggregates all the logic and flow
in a single script. That is arguably easier to run.

Bonus: the Docker containers contain Quibble. Hence the container has
everything one needs to properly reproduce a build.


As for the efficiency, there are a few optimizations that are left to be
done. Namely: clone the repositories in parallel and skipping some tests
when we know another job already ran it.  For example running the
JavaScript eslint check should only be done once.

But overall, yes the switch should make it faster to get feedback on
changes and to have them merged.

-- 
Antoine "hashar" Musso


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l