Re: [Wikitech-l] Parsoid/PHP replaces Parsoid/JS on the Wikimedia cluster

[Subramanya Sastry]

We haven't updated the setup instructions yet because we are going to be 
making some more changes to how Parsoid/PHP integrates with MediaWiki. 
We hope to be able to get it all squared away in time for the next MW 
release. That will make the installation as simple as upgrading to the 
latest MediaWiki install and adding some config options to 
LocalSettings.php.


But, if you are really impatient to try, ask again and we will provide 
some instructions. You will need MW 1.35.wmf.10+, Parsoid master, and 
PHP 7.2. It is likely going to work with 7.2+ since CI passes with 
7.4.but we haven't thoroughly tested against those versions. If you 
aren't ready to play with this bleeding edge and update again in a 
couple months, maybe best wait it out for the next release.


We will shortly be releasing a new Parsoid deb file that will be a final 
release for Parsoid/JS. Once better integrated with MediaWiki, we won't 
need to release Parsoid debs going forward.


Subbu.

On 12/20/19 3:12 AM, Hogan (US), Michael C wrote:

The Extension:VisualEditor page on Mediawiki.org still guides people to use 
Parsoid/JS. Where is the best place to find instructions for migrating a wiki 
installation from Parsoid/JS to Parsoid/PHP? If documentation doesn't exist, I 
can help create it once I understand the steps. I've also opened a topic on the 
Extension_talk:VisualEditor page if that's a more convenient place to discuss: 
https://www.mediawiki.org/wiki/Topic:Vd9tmhoaax7re3it

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


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

[Wikitech-l] TechCom Radar 2019-12-18

[Kate Chapman]

Hi All,

Here are the minutes from this week's TechCom meeting:

* Approved: MediaWiki database policy and/or guidelines (2019):


* Approved: RFC: Where to implement Desktop Improvements project


* Began discussing: Support PHP 7.4 preload


You can also find our meeting minutes at


See also the TechCom RFC board
.

If you prefer you can subscribe to our newsletter here


Thanks,
Kate

--
Kate Chapman
Senior Program Manager, Core Platform
Wikimedia Foundation
kchap...@wikimedia.org

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

Re: [Wikitech-l] Parsoid/PHP replaces Parsoid/JS on the Wikimedia cluster

[Hogan (US), Michael C]

The Extension:VisualEditor page on Mediawiki.org still guides people to use 
Parsoid/JS. Where is the best place to find instructions for migrating a wiki 
installation from Parsoid/JS to Parsoid/PHP? If documentation doesn't exist, I 
can help create it once I understand the steps. I've also opened a topic on the 
Extension_talk:VisualEditor page if that's a more convenient place to discuss: 
https://www.mediawiki.org/wiki/Topic:Vd9tmhoaax7re3it

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

Re: [Wikitech-l] Parsoid/PHP replaces Parsoid/JS on the Wikimedia cluster

[Amir Sarabadani]

Great job!
It's such a big improvement while users might not notice, I greatly
appreciate this improvement as it helps with the development and running
third party installations of mediawiki.

Best and thanks again!

On Thu, Dec 19, 2019, 18:26 Subramanya Sastry  wrote:

> Summary
> ---
> Parsoid/PHP, the PHP port of Parsoid is now live everywhere for all
> products on all wikis. Parsoid/JS is still deployed on the Wikimedia
> cluster but doesn't receive any traffic and will be decommissioned
> in the new year.
>
> Context: Making Parsoid the default MediaWiki wikitext engine
> -
> In 2018, we completed the replacement of HTML4 Tidy from MediaWiki
> with RemexHTML, a HTML5 parser.
>
> The port of Parsoid to PHP is the next step along the way to integrate
> Parsoid and the MediaWiki wikitext parser into a single wikitext engine.
> That final product will let us bring the benefits of Parsoid's approach
> to a wider set of products and let us start work on improving templates
> and wikitext or other features without having to implement that in two
> wikitext engines with different processing models.
>
> See a Feb 27 tech talk for a full context [1]. A future blog post will
> provide more details about the porting project and process.
>
> Performance
> ---
> Parsoid/PHP on the wikimedia cluster seems to be about 2x faster than
> Parsoid/JS for the wikitext -> HTML and HTML -> wikitext endpoints.
> This performance bump is a pleasant surprise given that going in, we
> anticipated to incur some performance penalty. While we have various
> theories about the factors contributing to this, we haven't had the
> opportunity yet to investigate fully. The load on the MediaWiki Action API
> endpoint was also significantly reduced on Dec 13 when we stopped
> processing mirrored traffic on Parsoid/JS (Parsoid/PHP accesses the
> database directly instead).
>
> Timeline
> 
> We started porting in earnest in Feb with some preparatory work over
> the previous few months. We deployed Parsoid/PHP as a passive mirror
> of the full volume of wikitext -> HTML requests in October & November
> to discover and fix problems early. By Dec 2, we’d enabled Parsoid/PHP
> for the majority of Parsoid clients on all wikis. On Dec 18, we switched
> everything over to Parsoid/PHP.
>
> Compared to an earlier estimate of 9 months, we took about 2 months longer
> to get to this milestone.
>
> Thanks to all the testing in place, in the end, this Parsoid/JS to
> Parsoid/PHP switch went fairly smoothly with some minor glitches.
>
> Credits
> ---
> This project to port Parsoid from Javascript (Node.js) to PHP was a
> multi-team collaboration. The Parsing, Core Platform, Product
> Infrastructure,
> Service Ops, Security teams from the Wikimedia Foundation were the relevant
> teams. We also benefited with some contractorhelp from Wikiteq. Thanks to
> everyone involved!
>
> [1]
>
> https://www.mediawiki.org/wiki/Wikimedia_Technical_Talks#Episode_1:_The_long_and_winding_road_to_making_Parsoid_the_default_mediaWiki_parser
>
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] New features for all mobile editors

[Olga Vasileva]

Hello everyone,

As of this week, the Readers Web team has expanded the deployment of a
small set of features from the mobile "advanced mode" users to all
logged-in users.  All logged-in users will now have access to article and
talk tabs, as well as direct access to history pages.

We hope that these changes will allow new contributors to access these
parts of the interface with more ease.  For more advanced contributors, we
do recommend using the "advanced mode", which includes the above features
and more!

Thank you!

Olga


-- 
*Olga Vasileva* // Reading Product Manager // Web
https://wikimediafoundation.org/


*Imagine a world in which every single human being can freely share in
the sum of all knowledge. That's our commitment. Donate
. *
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Early heads-up! Call for projects and mentors for Google Summer of Code 2020 and Outreachy Round 20 begins

[Srishti Sethi]

Hello everyone,

Wikimedia will be participating in the Google Summer of Code
 2020 and Outreachy
 Round 20!

This is an early heads-up to potential mentors interested in participating
in these programs – if you would like to mentor a coding or non-coding
(documentation, design, research, outreach, translation, etc.) project,
share your ideas in a comment on this Phabricator task:
https://phabricator.wikimedia.org/T241019 or refine it more secretly during
the year-end holidays :)

We will reach out to you with more formal steps in January! In the
meanwhile, here are some relevant links for you:
* A recent blog post highlighting one of our intern's and mentor's
experience participating in Outreachy program with Wikimedia:
https://wikimediafoundation.org/news/2019/06/25/wikimedia-and-outreachy-technical-internships-are-bridging-the-free-and-open-source-inclusion-gap/
* Roles and responsibilities of Google Summer of Code and Outreachy
mentors: https://www.mediawiki.org/wiki/Outreachy/Mentors,
https://www.mediawiki.org/wiki/Google_Summer_of_Code/Mentors
* Ongoing projects work via Outreachy Round 19
https://www.mediawiki.org/wiki/Outreachy/Round_19

Looking forward to your participation!

Cheers,
Srishti  & Pavithra
 (Wikimedia org admins)

*Srishti Sethi*
Developer Advocate
Wikimedia Foundation 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] MediaWiki Extensions and Skins Security Release Supplement

[Scott Bassett]

Greetings-

With the security/maintenance release of MediaWiki 1.31.6/1.32.6/1.33.2
[0], we would also like to provide this supplementary announcement of
MediaWiki extensions and skins with now-public Phabricator tasks, security
patches and backports [1]:

== CheckUser ==
+ (T234862, CVE-2019-18611) - Do not show oversighted edit summaries in
CheckUser API


== AbuseFilter ==
+ (T104807, CVE-2019-18612) - Older hidden versions of a currently-public
AbuseFilter are exposed via diffs


+ (T237887, CVE-2019-18987) - Old public versions of private filters are
publicly viewable


== VisualEditor ==
+ (T239209, CVE-2019-19708) - XSS in Visual Editor via Copy


== MinervaNeue skin ==
+ (T240487, CVE requested) - XSS in MinervaNeue skin


== LDAPAuthentication2 ==
+ (T240338, No CVE requested) - LDAPAuthentication2 allows login with
invalid password


The Wikimedia Security Team recommends updating these extensions and skins
to the current master branch or relevant, supported release branch [2] as
soon as possible. Some of the referenced Phabricator tasks above _may_
still be private. Unfortunately, when security issues are reported,
sometimes sensitive information is exposed and since Phabricator is
historical, we cannot make these tasks public without exposing this
sensitive information. If you have any additional questions or concerns
regarding this update, please feel free to contact secur...@wikimedia.org
or file a security task within Phabricator [3].

[0]
https://lists.wikimedia.org/pipermail/wikitech-l/2019-December/092886.html
[1] https://phabricator.wikimedia.org/T234983
[2] https://www.mediawiki.org/wiki/Version_lifecycle
[3] https://www.mediawiki.org/wiki/Reporting_security_bugs

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

[Wikitech-l] Parsoid/PHP replaces Parsoid/JS on the Wikimedia cluster

[Subramanya Sastry]

Summary
---
Parsoid/PHP, the PHP port of Parsoid is now live everywhere for all
products on all wikis. Parsoid/JS is still deployed on the Wikimedia
cluster but doesn't receive any traffic and will be decommissioned
in the new year.

Context: Making Parsoid the default MediaWiki wikitext engine
-
In 2018, we completed the replacement of HTML4 Tidy from MediaWiki
with RemexHTML, a HTML5 parser.

The port of Parsoid to PHP is the next step along the way to integrate
Parsoid and the MediaWiki wikitext parser into a single wikitext engine.
That final product will let us bring the benefits of Parsoid's approach
to a wider set of products and let us start work on improving templates
and wikitext or other features without having to implement that in two
wikitext engines with different processing models.

See a Feb 27 tech talk for a full context [1]. A future blog post will
provide more details about the porting project and process.

Performance
---
Parsoid/PHP on the wikimedia cluster seems to be about 2x faster than
Parsoid/JS for the wikitext -> HTML and HTML -> wikitext endpoints.
This performance bump is a pleasant surprise given that going in, we
anticipated to incur some performance penalty. While we have various
theories about the factors contributing to this, we haven't had the
opportunity yet to investigate fully. The load on the MediaWiki Action API
endpoint was also significantly reduced on Dec 13 when we stopped
processing mirrored traffic on Parsoid/JS (Parsoid/PHP accesses the
database directly instead).

Timeline

We started porting in earnest in Feb with some preparatory work over
the previous few months. We deployed Parsoid/PHP as a passive mirror
of the full volume of wikitext -> HTML requests in October & November
to discover and fix problems early. By Dec 2, we’d enabled Parsoid/PHP
for the majority of Parsoid clients on all wikis. On Dec 18, we switched
everything over to Parsoid/PHP.

Compared to an earlier estimate of 9 months, we took about 2 months longer
to get to this milestone.

Thanks to all the testing in place, in the end, this Parsoid/JS to
Parsoid/PHP switch went fairly smoothly with some minor glitches.

Credits
---
This project to port Parsoid from Javascript (Node.js) to PHP was a
multi-team collaboration. The Parsing, Core Platform, Product 
Infrastructure,

Service Ops, Security teams from the Wikimedia Foundation were the relevant
teams. We also benefited with some contractorhelp from Wikiteq. Thanks to
everyone involved!

[1] 
https://www.mediawiki.org/wiki/Wikimedia_Technical_Talks#Episode_1:_The_long_and_winding_road_to_making_Parsoid_the_default_mediaWiki_parser




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

Re: [Wikitech-l] Wikimedia Café online meeting for December 2019

[Pine W]

Hello colleagues,

This is a reminder that the December 2019 Wikimedia Café meeting will start
approximately one hour from now.

Pine
( https://meta.wikimedia.org/wiki/User:Pine )


On Fri, Nov 29, 2019 at 10:50 PM Pine W  wrote:

> Hello colleagues,
>
> For the next Wikimedia Café online video meeting, agenda items include:
> * Documentation for Wikitext 
> * The NavWiki  project
>
> Last month's Wikimedia Café had a problem with an inaccurate time
> conversion from USA Eastern time to UTC. People attempted to join the
> meeting at different times based on whether they referred to UTC or to US
> Eastern time. I apologize for the error, and I think that it has been
> corrected for December.
>
> The meeting style for the Café will emphasize discussion rather than
> presentation. People are welcome to participate as listeners only if they
> prefer.
>
> Please see the page on Meta
>  for more
> information about the Café. Please watch the page for any updates,
> particularly to the schedule or the agenda. Signing up for the meeting is
> optional, but is helpful to the organizers so that we can estimate how many
> people will attend. Signing up for the meeting also informs us who we
> should notify individually if there are significant changes, such as to the
> schedule.
>
> If there are any problems with connecting to the meeting or if you have
> any questions or comments then please write on the Meta talk page.
>
> Regards,
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Announcing MediaWiki 1.34.0

[Sam Reed]

I am happy to announce the availability of the general release of MediaWiki
1.34!

While tarballs have already been uploaded, git tags will follow later on
today.

Thanks to everyone who helped out with this release, especially thanks to
those who tested out the release candidates and provided feedback, as well
as the developers who worked hard to get several important fixes merged in
time for the 1.34 final release. To see what's changed in 1.34, see the
release notes below.

Please note that MediaWiki 1.34 no longer supports HHVM, and also the PHP
version requirement has been raised from 7.0.13 in MediaWiki 1.33, to 7.2.9.

As per the pre-release announcement, 1.34.0 includes some security fixes
that weren't in 1.34.0-rc.0 or 1.34.0-rc.1.

== Security fixes ==
* (T192134) Personal and site-wide CSS and JavaScript is loaded on
Special:PasswordReset.
* (T239466) Possible to circumvent title-blacklist (CVE-2019-19709).

== Links to all mentioned tasks ==
* https://phabricator.wikimedia.org/T192134
* https://phabricator.wikimedia.org/T239466

MediaWiki 1.34 is due to be supported until the end of November 2020.

**
Download:
https://releases.wikimedia.org/mediawiki/1.34/mediawiki-1.34.0.tar.gz

Download without bundled extensions:
https://releases.wikimedia.org/mediawiki/1.34/mediawiki-core-1.34.0.tar.gz

Patch to previous version (1.34.0-rc.1):
https://releases.wikimedia.org/mediawiki/1.34/mediawiki-1.34.0.patch.gz

GPG signatures:
https://releases.wikimedia.org/mediawiki/1.34/mediawiki-core-1.34.0.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.34/mediawiki-1.34.0.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.34/mediawiki-1.34.0.patch.gz.sig

Public keys:
https://www.mediawiki.org/keys/keys.html

Release Notes
https://www.mediawiki.org/wiki/Release_notes/1.34
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Security and maintenance release: 1.31.6 / 1.32.6 / 1.33.12

[Sam Reed]

I would like to announce the release of MediaWiki 1.33.2, 1.32.6 and 1.31.6!

These releases also serve as a maintenance release for these branches.

While tarballs have already been uploaded, git tags will follow later on
today.

As a reminder, 1.32.6 will also be the final release for 1.32 (barring any
unforeseen issues), which is scheduled to become end of life in January
2020 [1]. If you're using 1.32, it is recommended that you upgrade to the
latest point release of the 1.33 branch (1.33.2, to be released tomorrow)
or 1.34.0 to carry on using a maintained and supported release.

An "MediaWiki Extensions Security Release Supplement" email will follow
this one.

== Security fixes ==
* (T192134) Personal and site-wide CSS and JavaScript is loaded on
Special:PasswordReset.
* (T212067) wfParseUrl() incorrectly parses hostnames in older PHP and HHVM
versions due to bug in parse_url(). This is only potentially an issue on MW
< 1.34 where it supports PHP version (see PHP bug 73192) 7.0.0–7.0.12, or
HHVM less than 3.18.6.
* (T239466) Possible to circumvent title-blacklist (CVE-2019-19709).

== Links to all mentioned tasks ==
* https://phabricator.wikimedia.org/T212067
* https://phabricator.wikimedia.org/T239466
* https://phabricator.wikimedia.org/T192134
* https://bugs.php.net/bug.php?id=73192

== Release notes ==

Full release notes for 1.31.6:
https://phabricator.wikimedia.org/diffusion/MW/browse/REL1_31/RELEASE-NOTES-1.31
https://www.mediawiki.org/wiki/Release_notes/1.31

Full release notes for 1.32.6:
https://phabricator.wikimedia.org/diffusion/MW/browse/REL1_32/RELEASE-NOTES-1.32
https://www.mediawiki.org/wiki/Release_notes/1.32

Full release notes for 1.33.2:
https://phabricator.wikimedia.org/diffusion/MW/browse/REL1_33/RELEASE-NOTES-1.33
https://www.mediawiki.org/wiki/Release_notes/1.33

For information about how to upgrade, see


**
Download:
https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.6.tar.gz

Download without bundled extensions:
https://releases.wikimedia.org/mediawiki/1.31/mediawiki-core-1.31.6.tar.gz

Patch to previous version (1.31.5):
https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.6.patch.gz

GPG signatures:
https://releases.wikimedia.org/mediawiki/1.31/mediawiki-core-1.31.6.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.6.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.31/mediawiki-1.31.6.patch.gz.sig

Public keys:
https://www.mediawiki.org/keys/keys.html

**
Download:
https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.6.tar.gz

Download without bundled extensions:
https://releases.wikimedia.org/mediawiki/1.32/mediawiki-core-1.32.6.tar.gz

Patch to previous version (1.32.5):
https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.6.patch.gz

GPG signatures:
https://releases.wikimedia.org/mediawiki/1.32/mediawiki-core-1.32.6.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.6.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.6.patch.gz.sig

Public keys:
https://www.mediawiki.org/keys/keys.html

**
Download:
https://releases.wikimedia.org/mediawiki/1.33/mediawiki-1.33.2.tar.gz

Download without bundled extensions:
https://releases.wikimedia.org/mediawiki/1.33/mediawiki-core-1.33.2.tar.gz

Patch to previous version (1.33.1):
https://releases.wikimedia.org/mediawiki/1.33/mediawiki-1.33.2.patch.gz

GPG signatures:
https://releases.wikimedia.org/mediawiki/1.33/mediawiki-core-1.33.2.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.33/mediawiki-1.33.2.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.33/mediawiki-1.33.2.patch.gz.sig

Public keys:
https://www.mediawiki.org/keys/keys.html
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Ops] [Train] 1.35.0-wmf.11 status update

[James Forrester]

The 1.35.0-wmf.11 version of MediaWiki is fully deployed to Wikimedia
production.[0][1]

Thank you to everyone for their help resolving issues, both this week and
over the past year.

The train will be next deployed from Tuesday, 7 January 2020 onwards with
1.35.0-wmf.14.

[0]. 
[1]. 

Yours,
-- 
*James D. Forrester* (he/him  or they/themself
)
Wikimedia Foundation 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Adding a Citation on VE surface using SurfaceModel

[Egbe Eugene]

Hi All,

What is the best way to add a citation text on the VE surface?

I have wikitext of the form

{{sample mediawiki
|Path=
http://localhost/myweb/otherprojects/mw/core/index.php/Main_Page#Getting
|Title= Medaiwiki|Publisher = [[Wikimedia]]
|Date= 17 June 2019|Arrival date= 12 May 2017
| Archive Path = mediawiki.org| Archive date = 4 September 2019 }}


which when I paste, VE renders automatically. But when I write it as a
string, it does not render on the surface.

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