[Wikitech-l] Phabricator monthly statistics - 2017-05

[communitymetrics]

Hi Community Metrics team,

This is your automatic monthly Phabricator statistics mail.

Accounts created in (2017-05): 291
Active Maniphest users (any activity) in (2017-05): 901
Task authors in (2017-05): 512
Users who have closed tasks in (2017-05): 272

Projects which had at least one task moved from one column to another on
their workboard in (2017-05): 281

Tasks created in (2017-05): 2573
Tasks closed in (2017-05): 2095
Open and stalled tasks in total: 34515

Median age in days of open tasks by priority:

Unbreak now: 101
Needs Triage: 278
High: 490
Normal: 678
Low: 940
Lowest: 898

(How long tasks have been open, not how long they have had that priority)

Active Differential users (any activity) in (2017-05): 27

TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .

Yours sincerely,
Fab Rick Aytor

(via community_metrics.sh on iridium at Thu Jun  1 00:00:24 UTC 2017)

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

[Wikitech-l] Reading monthly update for May 2017

[Chris Koerner]

Hello,
Welcome to the first in a reoccurring monthly update from the Reading
department at the Wikimedia foundation. Here we'll provide a quick summary
of things that are currently being worked on. An archive of past activity
can be found on Mediawiki.org. Feedback and questions are welcome.


== Web ==

=== New print styles for the mobile web ===
Based on the findings of the New Readers team, we learned that users are
increasingly getting information online, and then sharing or consuming it
offline. In terms of mobile devices, this often means taking screenshots of
useful information, or saving the article as a PDF to read later on their
phones. Our older print styles did not account for reading on mobile
devices - they focused on paper printing. We will update our print styles
for mobile devices to account for offline consumption, making them easier
to read and navigate, as well as accounting for missing crucial information
such as article title and branding.[0]

=== Moving the lead section before the infobox on the mobile web ===
Over the past few quarters, we've been focusing on the top of the article
experience on the mobile website. One of the identified issues was that,
for articles which contained an infobox, users were exposed to the infobox
content prior to having an overview of the subject of the article itself.
To improve on this issue, we've moved the lead section of each article so
that it appears before the infobox on mobile, allowing readers to have
access to the main content of the page earlier. This change is now live on
all projects. Before, [0] After [1]

=== Completing related pages deployment ===
Since March 30, 2017, we have been running a test on enwiki on the related
pages feature. Over the past month, we collected data and analyzed the
performance of the feature.[2] Based on the results, we completed the
deployment of the feature on mobile English Wikipedia.

== New Readers ==

* The New Readers team is deep in beginning pilots to address the barriers
that were identified as highest priority through deep research in 2016.[3]
You can see deeper, cross-team updates at m:New Readers/Updates. [4]
* For Reading, we're supporting the Android and Web teams in developing
deeper support for readers who have internet sometimes, but want access to
some content when they're offline or don't want to spend the data to read.
To see a summary of that work, check out m:New Readers/Offline.[5]

== Multimedia ==
* In addition to bugfixes and maintenance, the team has been evaluating the
pre-release version of 3D model file support and collecting feedback via
the Commons Village Pump.[6] During the forthcoming month the team will be
prioritizing and working on 3D tasks in anticipation of a future launch.[7]

== Other Noteworthy Stuff ==
* Following April's Q3 quarterly check-in, we examined core readership
metrics for the same timespan in a followup presentation.[8] [9]


[0]
https://www.mediawiki.org/wiki/Reading/Web/Projects/Print_Styles#Mobile_Printing
[1]
https://www.mediawiki.org/wiki/File:Mobile_website,_older_version_of_infobox_and_first_paragraph.png
[2]
https://www.mediawiki.org/wiki/File:Lead_paragraph_before_infobox_example_-_Ada_Lovelace_article.png
[3]
https://www.mediawiki.org/wiki/Reading/Web/Projects/Related_pages#Metrics_analysis
[4] https://meta.wikimedia.org/wiki/New_Readers/Findings
[5] https://meta.wikimedia.org/wiki/New_Readers/Updates
[6] https://meta.wikimedia.org/wiki/New_Readers/Offline
[7]
https://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2017/05#Preparing_for_3D_models_on_Commons
[8] https://phabricator.wikimedia.org/tag/3d/
[9]
https://www.mediawiki.org/wiki/File:Reading,_Comm_Tech_%26_TPG_Quarterly_Check-in,_Apr_2017.pdf
[10]
https://commons.wikimedia.org/wiki/File:Wikimedia_Foundation_Reading_metrics_Q3_2016-17_(Jan-Mar_2017).pdf

---

The archive of all past updates can be found on MediaWiki.org:

https://www.mediawiki.org/wiki/Reading/Status_updates


Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] 2017-05-31 Scrum of Scrums meeting notes

[Grace Gellerman]

https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-05-31

*= 2017-05-31 =*
contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
== Call outs:==
* Security: status of TemplateStyles security review? (—from Reading eng.)
**its almost done. will be done end of this week at latest --bawolff
* Analytics: EventLogging purging script will be deployed before end of Q4.
  Reminder: Default purging strategy for new schemas since July 2016 is
full purge after 90 days.
  If you want new schemas sinc that date not to be fully purged after 90
days, please contact Analytics as soon as possible.
* RelEng: If you've committed something recently that may affect
performance, you maybe did affect performance: please check :) -
https://phabricator.wikimedia.org/T166345

=== Reading ===
 iOS 
* Last week
** 5.5 - https://phabricator.wikimedia.org/project/view/2602/
*** Places search updates: https://phabricator.wikimedia.org/T159733
*** Update `Top Read` feed design: https://phabricator.wikimedia.org/T165510
*** Places accessibility: https://phabricator.wikimedia.org/T159733
*** Other bug fixes & enhancements
* This week
** 5.5 - https://phabricator.wikimedia.org/project/view/2602/
*** Feature freeze, finish any remaining bug fixes & design tweaks
*** Regression testing

 Android 
* Bug identified last week causing stale content on the German WP main
page.  Thanks to Arlo and the Parsoid crew for the quick fix.
* Beta release planned for late this week (for real).  Finishing up final
tasks now.
* Next release will finalize the UI components for readling list syncing.
* New engineer hiring process is underway.  (The new eng will replace
Stephen who is moving to Reading Web.)
* Current release board:
https://phabricator.wikimedia.org/project/view/2352/
* Next release board: https://phabricator.wikimedia.org/project/view/2763/

 Multimedia 
* Ongoing: Media Viewer improvements, bringing it in line with standards
that didn't exist when it was written
* Soon: 3D extension prioritization and fixes
* Current work is largely stalled due to hiring process

 Web 
* Commencing work on Electron PDF. (cc Ops)
* Clearing out backlog - with a focus on #wikimedia-log-errors (cc RelEngs)

 Reading Infrastructure 
* compiling Page Content Service Data Inventory for HTML endpoint

 Wikidata 
* attended Wikicite (after the hackathon)
* Wikidata build is broken due to CI - it runs composer update. need
someone to review jenkins-config change to add the ability to do composer
install instead:
** https://gerrit.wikimedia.org/r/#/c/354522/
* discussed at hackathon to move away from having the Wikidata build
entirely and put our libraries into mediawiki-vendor

 Services 
* Blockers: none
* Updates:
** Getting ready to test automatic RESTBase blacklisting

 Security 
* Reviews:
** psy/psysh use on WMF servers
** Verification of whitelisted.yaml / graylisted.yaml

=== Editing ===
 Language 
* No blockers. Not blocking.
* CX new change in wmf3: User can now choose article publish destination in
a better manner.

 Parsing 
* Waiting on the wmf2 train to roll out fully for some followup work /
updates.
* Linter patch to cache linter counts is still in review, but close to
being merged. Once that gets in, and it rolls out, we will be able to
re-enable linter on large wikis
* https://gerrit.wikimedia.org/r/#/c/72053/ introduces a piglatin language
variant for easier testing of language variant code. Needs reviews. Bartosz
might already be on it.

 Collaboration 
* Continued work on namespace and tag filters for RCFilters
* Followup and bug fixes on the new notification blacklist feature (now in
Beta Cluster)
* Working on tag validation for AbuseFilter

 Analytics 
* We found the issue in global unique devices count per top domain (*.
wikipedia.org),
   fixed it and data looks good after vetting, will be productionized in
short.
* Ongoing: Webrequest Tagging (portal, pageviewAPI, etc.)
* Making progress on Wikistats2 front-end (stats.wikimedia.org replacement)
* CRing and testing EL purging script, we plan to deploy it before the end
of the quarter.
   Reminder: Default purging strategy for new schemas since July 2016 is
full purge after 90 days.

 UI Standardization 
* This week:
** Preparing urgent v0.23.0 with OOjs v2.1.0 dependency, bug fixes and
further improvements around Promise-methods feat WindowManager
** Continuos work on style guide build process, semi-automated SVG export
* Updates:
** OOjs UI:
*** v0.22.0 released with 2 accessibility and several other (UI)
improvements, among those
 Rename the 'MediaWiki' theme to 'WikimediaUI' for clarity on
development focus
 WindowManager: Add `WindowInstance` - a Promise-based lifecycle object
(Timo Tijhof) and follow
 Frameless button sizing equal framed ones is in
 Passing ARIA tests from 13 up to 18
 OOjs UI demos now with strengthened mobile experience, clearer

Re: [Wikitech-l] Question re what-links-here

[Aran]

What I meant by the code being changed programmatically is that some of
the content in the wiki is in the form of parser-functions, and the PHP
code that is responsible for rendering the parser-function was changed
which meant that the wiki's content has changed but without any edits
having been made. Thus I needed to refresh the links manually which the
maintenance script.


On 31/05/17 15:17, Aran wrote:
> No I just ran the refreshLink.php maintenance script from the shell.
>
>
> On 31/05/17 15:12, יגאל חיטרון wrote:
>> Did you use a bot? An API javascript? In any case, try the rest one.
>> Igal
>>
>> On May 31, 2017 21:04, "Aran"  wrote:
>>
>>> Hello,
>>>
>>> I have some wikis which have had some of their content changed
>>> programmatically due to the code in a parser-function being changed.
>>>
>>> In the wikis that are MediaWiki 1.27, the links in the what-links-here
>>> didn't update after I ran the refreshLinks maintenance script. The ones
>>> that are 1.28's in the same situation the links updated fine after
>>> running the script... is this a known issue? is there any way I can
>>> update the links in the 1.27's without upgrading the wiki?
>>>
>>> Thanks,
>>> Aran
>>>
>>>
>>> ___
>>> 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 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

Re: [Wikitech-l] Question re what-links-here

[Aran]

No I just ran the refreshLink.php maintenance script from the shell.


On 31/05/17 15:12, יגאל חיטרון wrote:
> Did you use a bot? An API javascript? In any case, try the rest one.
> Igal
>
> On May 31, 2017 21:04, "Aran"  wrote:
>
>> Hello,
>>
>> I have some wikis which have had some of their content changed
>> programmatically due to the code in a parser-function being changed.
>>
>> In the wikis that are MediaWiki 1.27, the links in the what-links-here
>> didn't update after I ran the refreshLinks maintenance script. The ones
>> that are 1.28's in the same situation the links updated fine after
>> running the script... is this a known issue? is there any way I can
>> update the links in the 1.27's without upgrading the wiki?
>>
>> Thanks,
>> Aran
>>
>>
>> ___
>> 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 mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Question re what-links-here

[יגאל חיטרון]

Did you use a bot? An API javascript? In any case, try the rest one.
Igal

On May 31, 2017 21:04, "Aran"  wrote:

> Hello,
>
> I have some wikis which have had some of their content changed
> programmatically due to the code in a parser-function being changed.
>
> In the wikis that are MediaWiki 1.27, the links in the what-links-here
> didn't update after I ran the refreshLinks maintenance script. The ones
> that are 1.28's in the same situation the links updated fine after
> running the script... is this a known issue? is there any way I can
> update the links in the 1.27's without upgrading the wiki?
>
> Thanks,
> Aran
>
>
> ___
> 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

Re: [Wikitech-l] Question re what-links-here

[Aran]

Strange, I've just noticed after coming back to it that the 1.27's are
looking fine now... does the refreshLinks script launch child processes
in the background or something?


On 31/05/17 15:03, Aran wrote:
> Hello,
>
> I have some wikis which have had some of their content changed
> programmatically due to the code in a parser-function being changed.
>
> In the wikis that are MediaWiki 1.27, the links in the what-links-here
> didn't update after I ran the refreshLinks maintenance script. The ones
> that are 1.28's in the same situation the links updated fine after
> running the script... is this a known issue? is there any way I can
> update the links in the 1.27's without upgrading the wiki?
>
> Thanks,
> Aran
>
>
> ___
> 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] Question re what-links-here

[Aran]

Hello,

I have some wikis which have had some of their content changed
programmatically due to the code in a parser-function being changed.

In the wikis that are MediaWiki 1.27, the links in the what-links-here
didn't update after I ran the refreshLinks maintenance script. The ones
that are 1.28's in the same situation the links updated fine after
running the script... is this a known issue? is there any way I can
update the links in the 1.27's without upgrading the wiki?

Thanks,
Aran


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

[Wikitech-l] [MediaWiki-announce] 1.29.0-rc.0 released, timeline on 1.29.0, EOL of 1.23.x

[Chad Horohoe]

Hi,

I'd like to announce the immediate availability of MediaWiki 1.29.0-rc.0,
the first release candidate for 1.29.x. Links at the end of the e-mail.

This is not a final release and should not be used for production websites.
Notably, there's a few major outstanding bugs related to the job queue. As
always please do try out the release candidate in a test environment. It's
how we find bugs that didn't surface in initial development :)

The timeline for 1.29.0 is a little fuzzy right now, and I apologize. The
outstanding bugs have been pretty hard to isolate and fix, but I see
progress so I hope those working on them will have it all resolved soon.

Finally, per the version lifecycle I'm announcing the End Of Life of
MediaWiki 1.23.x. The final release in this series was 1.23.17. Those
installations using the versions as LTS should upgrade to 1.27.3, as 1.27.x
is the supported LTS branch through June 2019.

Full release notes:
https://phabricator.wikimedia.org/diffusion/MW/browse/REL1_29/RELEASE-NOTES-1.29
https://www.mediawiki.org/wiki/Release_notes/1.29


**
Download:
https://releases.wikimedia.org/mediawiki/1.29/mediawiki-1.29.0-rc.0.tar.gz

Core only, no extensions:
https://releases.wikimedia.org/mediawiki/1.29/mediawiki-core-1.29.0-rc.0.tar.gz.sig

GPG signatures:
https://releases.wikimedia.org/mediawiki/1.29/mediawiki-core-1.29.0-rc.0.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.29/mediawiki-1.29.0-rc.0.tar.gz.sig

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

--
Chad Horohoe
___
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] SEMANTiCS 2017, Amsterdam, Sep 11-14, Extended Submission Deadline May 31, 2017

[Sebastian Hellmann]

 DEADLINE EXTENSION

Due to several requests the SEMANTiCS 2017 conference extends its 
submission deadlines.


3rd Call for Research & Innovation Papers
SEMANTiCS 2017 - The Linked Data Conference
13th International Conference on Semantic Systems

Amsterdam, Netherlands
September 11 -14, 2017
http://2017.semantics.cc

The Research & Innovation track at SEMANTiCS welcomes the submission of 
papers on novel scientific research and/or innovations relevant to the 
topics of the conference. Submissions must be original and must not have 
been submitted for publication elsewhere. Papers should follow the ACM 
ICPS guidelines for formatting 
(http://www.acm.org/sigs/publications/proceedings-templates) and must 
not exceed 8 pages in lenght for full papers and 4 pages for short 
papers, including references and optional appendices.


Research & Innovation Papers are published within ACM ICP Series.

Important Dates (Research & Innovation)
* Abstract Submission Deadline:   extended: May 31, 2017 (11:59 
pm, Hawaii time)
* Paper Submission Deadline:extended: June 7, 2017 
(11:59 pm, Hawaii time)
* Notification of Acceptance: July 3, 2017 (11:59 pm, 
Hawaii time)
* Camera-Ready Paper: August 14, 2017 (11:59 pm, 
Hawaii time)


For details please go to: https://2017.semantics.cc/calls
or contact the Research and Innovation Chairs:
Catherine Faron Zucker, faron [@] i3s.unice.fr, Université Nice Sophia 
Antipolis
Rinke Hoekstra, rinke.hoekstra [@] vu.nl, Vrije Universiteit 
Amsterdam/University of Amsterdam


As in the previous years, SEMANTiCS’17 proceedings will be published by 
ACM ICP (pending).


SEMANTiCS 2017 will especially welcome submissions for the following hot 
topics:

* Data Science (special track, see below)
* Web Semantics, Linked (Open) Data & schema.org
* Corporate Knowledge Graphs
* Knowledge Integration and Language Technologies
* Data Quality Management
* Economics of Data, Data Services and Data Ecosystems

Following the success of previous years, the ‘horizontals’ (research) 
and ‘verticals’ (industries) below are of interest for the conference:


Horizontals
* Enterprise Linked Data & Data Integration
* Knowledge Discovery & Intelligent Search
* Business Models, Governance & Data Strategies
* Semantics in Big Data
* Text Analytics
* Data Portals & Knowledge Visualization
* Semantic Information Management
* Document Management & Content Management
* Terminology, Thesaurus & Ontology Management
* Smart Connectivity, Networking & Interlinking
* Smart Data & Semantics in IoT
* Semantics for IT Safety & Security
* Semantic Rules, Policies & Licensing
* Community, Social & Societal Aspects

Data Science Special Track Horizontals
* Large-Scale Data Processing (stream processing, handling large-scale 
graphs)

* Data Analytics (Machine Learning, Predictive Analytics, Network Analytics)
* Communicating Data (Data Visualization, UX & Interaction Design, 
Crowdsourcing)

* Cross-cutting Issues (Ethics, Privacy, Security, Provenance)

Verticals
* Industry & Engineering
* Life Sciences & Health Care
* Public Administration
* e-Science
* Digital Humanities
* Galleries, Libraries, Archives & Museums (GLAM)
* Education & eLearning
* Media & Data Journalism
* Publishing, Marketing & Advertising
* Tourism & Recreation
* Financial & Insurance Industry
* Telecommunication & Mobile Services
* Sustainable Development: Climate, Water, Air, Ecology
* Energy, Smart Homes & Smart Grids
* Food, Agriculture & Farming
* Safety, Security & Privacy
* Transport, Environment & Geospatial

For details please go to: https://2017.semantics.cc/calls


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

[Wikitech-l] CREDIT showcase, Wednesday 7-June-2017

[Lani Goto]

Hi!

I'd like to welcome you to join us at the CREDIT showcase next week,
Wednesday, 7-June-2017 at 1800 UTC / 1100 Pacific Time. We'd like to see
your demos, whether they're rough works in progress or polished production
material, or even just a telling of something you've been studying
recently. For more information on the upcoming event, as well as recordings
of previous events, please visit the following page:


https://www.mediawiki.org/wiki/CREDIT_showcase

And if you'd like to share the news about the upcoming CREDIT showcase,
here's some suggested verbiage. Thanks!


*Hi *

*I hope all is well with you! I wanted to let you know about CREDIT, a
monthly demo series that we’re running to showcaseopen source tech projects
from Wikimedia’s Community, Reading, Editing, Discovery, Infrastructure and
Technology teams. *

*CREDIT is open to the public, and we welcome questions and discussion. The
next CREDIT will be held on June 7th at 11am PT / 2pm ET / 18:00 UTC. *

*There’s more info on MediaWiki, and on Etherpad, which is where we take
notes and ask questions. You can also ask questions on IRC in the Freenode
chatroom #wikimedia-office (web-based access here). Links to video will
become available at these locations shortly before the event.*

*Please feel free to pass this information along to any interested folks.
Our projects tend to focus on areas that might be of interest to folks
working across the open source tech community: language detection,
numerical sort, large data visualizations, maps, and all sorts of other
things.*

*If you have any questions, please let me know! Thanks, and I hope to see
you at CREDIT.*

*YOURNAME*

-- 
Lani Goto
Project Assistant, Engineering Admin
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] RFC discussion today: change PostgreSQL schema to be consistent with MySQL schema

[Daniel Kinzler]

This is a reminder of today's RFC discussion about MediaWiki's database schema
for PostgreSQL. Tim proposes to make it more similar to our MySQL schema, to
reduce maintenance overhead and breakage
.

Rationale: The inconsistencies between the MySQL and PostgreSQL schemas cause a
constant maintenance burden. PostgreSQL support is frequently broken in master.
The PostgreSQL schema is certainly better than the MySQL one, if analyzed in
isolation, but the advantages to PostgreSQL users of having an improved schema
are more than outweighed by the disadvantages of inconsistency with the
remainder of the installed MediaWiki user base.


The discussion will take place on the #wikimedia-office channel on Freenode, at
21:00 UTC (2pm PDT, 23:00 CEST).

-- 
Daniel Kinzler
Principal Platform Engineer

Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.

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

Re: [Wikitech-l] Does Mathoid require RESTBase?

[James Montalvo]

For now I've decided to fork Extension:SimpleMathJax and fix some issues I
had with it, but ultimately I'd prefer to use Extension:Math with Mathoid
since that seems to be the direction Wikipedia is going. But while moving
in the same direction as WMF wikis is good for stability, bug fixes,
feature additions, etc, I'm concerned about the complexity and lack of
documentation for setting this up. Furthermore, I'm concerned how
introducing RESTBase would negatively impact the rest of my setup,
particularly Parsoid. I also don't understand (and this is probably just my
ignorance) why RESTBase is required as an intermediary. Shouldn't it be
possible to configure Extension:Math to talk directly to Mathoid like
VisualEditor can talk directly to Parsoid?

Is RESTBase likely to give me any performance improvement, or is the
overhead likely to hurt my performance? Approximately 5-10k hits per day
with a pretty high edit:view ratio.

Thanks,
James

On Thu, Apr 27, 2017 at 12:32 PM, Moritz Schubotz 
wrote:

> Hi James,
>
> unfortunately it's currently a hard requirement. While it improved the
> performance significantly for large content providers like Wikipedia
> it made setting up mathoid on small privately hosted instances more
> difficult. Setting up a simpler way to enable math on private wikis is
> on my todo list.
> However, this guide is the best pointer I can give at the moment:
>
> https://www.mediawiki.org/wiki/Extension:Math/Restbase
>
> Please let me know if you encouter difficulties following the
> instructions provided at this page.
>
> Best
>
> physikerwelt
>
> On Thu, Apr 27, 2017 at 6:48 PM, James Montalvo
>  wrote:
> > Extension:Math removed client side MathJax support after MW 1.25. This
> > makes setup of the Math extension considerably more difficult. Mathoid
> was
> > fairly straightforward, but RESTBase seems like it is much more
> > complicated. Is RESTBase a hard requirement? Is there any way to connect
> to
> > Mathoid directly, the way VE can connect to Parsoid directly?
> >
> > Thank you,
> > James
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
> --
> Mit freundlichen Grüßen
> Moritz Schubotz
>
>   Telefon (Büro):  +49 30 314 22784
>   Telefon (Privat):+49 30 488 27330
>   E-Mail: schub...@itp.physik.tu-berlin.de
>   Web: http://www.physikerwelt.de
>   Skype: Schubi87
>   ICQ: 200302764
>   Msn: mor...@schubotz.de
>
> ___
> 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