There is talk in some communities about the wg-globals going away later this year, but I can't find anything in the tech updates or mw.org
Is there any definite time-line for the removal?
Sent from my Android device with K-9 Mail. Please excuse my brevity.
= 2016-06-08 =
== Product ==
=== Editing ===
==== Collaboration ====
* Blocked - None
* Blocking - Working on External Store on Beta
** Expanding our API to fetch notifications by specific pages.
** Working on expandable Echo bundles
** Split Flow Vagrant role to mitigate some issues with Flow having a lot
of MediaWiki-Vagrant dependencies.
==== Language ====
* Blocked: None
* Blocking: None
** Work on ContentTranslation, Compact Language Links continue.
==== Parsing ====
* Parsoid use of service-runner: working with Marko to deal with final
steps (puppet updates, testing in beta cluster).
* Followup RFC for Tidy replacement scheduled today (Wed, Jun 8).
* Released Parsoid 0.5.1 debian package last week.
==== Multimedia ====
* Not blocked, not blocking
* New repository set up for experimental new extension for file annotations
* UploadWizard fixes moving along apace
* Gallery slideshow patch looking nicer, proceeding
=== Reading ===
==== Reading Infrastructure ====
* AuthManager goes live this week!
==== Reading Web ====
* Fixing issues with lazy loading images and refs
* AB test of Popups extension ("Hovercards") on hu.wiki in progress (50%
==== Android ====
* Beta release this past Monday (6/6).
* Working hard on the feed. No dependencies on other teams for this for
* On the horizon (Q3): UI updates for cohesiveness and ease of use.
==== Mobile Content Service ====
* Deployed first three feed-related endpoints. Not publicly available yet.
Use labs instance if needed. Still adjusting response format.
==== Community Tech ====
* Testing PageAssessments on Beta Labs (
* Working on CopyPatrol tool on Tool Labs (
* No blockers
==== iOS ====
* No update
== Technology ==
=== Analytics ===
* We're blocking the Release team on its goal to move deployment to scap3,
we're trying to prioritize and get it done but it might not fit until early
* Pageview API is still throwing 500 errors despite the throttling down to
10 requests per second, we've had an update to the AQS compaction (and an
update to SSDs from spinning slowpokes) under testing for a while, so far
the numbers look about an order of magnitude better.
* Ongoing: normalizing and loading all history from all mediawiki dbs into
* The team will be at its offsite next week, and Madhu and Dan will be at
Wikimania, Andrew taking vacation after the offsite. Our offsite is in
Berlin and we're working out of WMDE's offices, so if they need us for any
in-person hacking, we're there :)
=== Technical Operations ===
** Language Engineering on Parallel corpora dumps
** ORES is deployed in production. Try it out in http://ores.wikimedia.org
** Got a few problems with services on SCB today
** A jessie appserver passed smoke tests, we are moving towards upgrading
the mw* fleet to jessie now.
** GTID 100% deployed on core dbs. Labs/analytics/dbstore needs work.
** Insecure POST block still coming up June 12 (this weekend)
=== Services ===
* service cluster services outage today
** approx 15 mins
** stil under investigation
* Cassandra partial outage last week during move to 2.2.6
* MathML by default
** hit some initial bumps, should be good now
=== Security ===
* Two usability bugs for Ex::OATHAuth in progress (T136988, T136989)
* Two-factor usability survey on hold until after AuthManager is enabled
* Fix for T129738 will be deployed this week
* Reviews: Use of wheels for deployment by Analytics
=== Research ===
* Wikilabels downtime --
=== Discovery ===
* '''Blocking''': none
* '''Blocked''': none
* ElasticSearch 2.3 upgrade is finished
* TextCat demo: https://tools.wmflabs.org/textcatdemo/
* Portal now has language detection and sorting
* Investigation of how long the typical portal session is:
=== Wikidata ===
* Working on MediaInfo and support for structured data on commons
* Deploying ArticlePlaceholder to 3 more wikis tomorrow (June 9)
https://phabricator.wikimedia.org/T135624 (guwiki, lvwiki, nnwiki)
=== RelEng ===
* '''Blocking''': None as far as we know
* '''Blocked''': Reading Infra - AuthManager (blocks 1.27 release)
** REMINDER! Migrate your things to scap3:
*** What have you touched? Please migrate! :)
** Phabricator update going out this week (was postponed):
=== Fundraising tech ===
* Trying to get payments onto 1.26 before 1.25 EOLs
** pondering what to do for the future, including even divorcing
DonationInterface from MW entirely
* Testing new processor in Israel, Japan and Ukraine
* Ready to test new PayPal integration method
* Enhancing fraud & dos mitigation measures
* more work to get off ActiveMQ
** potential translation bug rendering banners:
** listing old cookies to unset or migrate to LocalStorage:
There is a possible disk failure of our main CI host, 'gallium'. It is
being investigated at:
We are very sorry for the inconvenience.
Major updates will be sent to the lists with minor updates/investigation
on the task linked above.
Thanks to Kunal and Yuvi for responding so far.
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
the Reading Infrastructure team will try to enable AuthManager  in WMF
production this week, with the following schedule:
- group0 Tuesday 22:00 UTC (yes, that's pretty much now)
- group1 Wednesday 22:00 UTC
- group2 Thursday 22:00 UTC
I apologize for the very late notice. I realize that such a change should
ideally be fixed long before, advertised via the Tech news etc, but
omitting that seemed like the lesser of two evils. We believe we need to
get AuthManager into the 1.27 release as having to support two completely
different authentication systems in the LTS release would be an
unreasonable burden and risk; to do that, we need to test it in production
in very short order, otherwise the release will be delayed a lot due to
vacations and Wikimania; and we weren't sure until very recently whether we
are able to keep to this schedule.
If all goes well, switching AuthManager on should have very little visible
effect (see earlier announcements ), but with a change of this
complexity all rarely goes well. If you see authentication-related
problems, please ping or cc Brad Jorsch (IRC: anomie) and me (IRC: tgr). If
we are not around and things break badly, you can revert by setting
wgDisableAuthManager to true in wmf-config.
We're glad you like the new page functionality! I've opened up a ticket
<https://phabricator.wikimedia.org/T137215> to fix the Dutch phrase
translation typo, thanks for letting us know. :)
For your comment about adding in an option to change the language, I'm
curious about something, as this has come up before. Would you prefer to
use the portal page in the language that is detected (as we do now) or in a
different language but not actually searching on that language's wiki?
For instance, if your preferred language is Dutch: would it make sense for
you to click on that language link on the portal page to go to
nl.wikipedia.org and then do a search? Or, even if the browser's language
is detected as Dutch (nl) would you rather use the portal page to search in
a different language, like English?
Yes, thanks for asking, the sister project links will be translated and we
have a ticket <https://phabricator.wikimedia.org/T136441> open to get that
started. We wanted the descriptive text to be visible on the page to give
more insight into the sister projects, even though we don't have the text
Product Manager, Discovery
On Tue, Jun 7, 2016 at 5:13 AM, Romaine Wiki <romaine.wiki(a)gmail.com> wrote:
> Hi Deb,
> Great improvement!
> Looking at the page, I only notice one major error. My language is Dutch
> (nl), and so my browser/computer system is set that way. However the phrase
> is spelled wrong: it says: "De vrieje encyclopedie" while it should say "De
> vrije encyclopedie". So: vrieje -> vrije. "vrieje" is not a Dutch word. Can
> this be fixed?
> Further I would recommend one thing to be added to the page. Because large
> parts of the word visit Wikipedia through internet cafés and computers
> elsewhere, I would suggest in the top right/left corner an option to change
> the language.
> And one final question: will the bottom section of the page also be
> 2016-06-07 0:05 GMT+02:00 Deborah Tankersley <dtankersley(a)wikimedia.org>:
>> The Discovery team recently updated the wikipedia.org portal page to
>> detect what the visitor's browser's preferred language(s) are and then
>> arrange the language links around the globe to match those language
>> Earlier this year, we ran a successful A/B test
>> that proved promoting our visitor's preferred languages resulted in
>> increased visibility and interest into these projects. Also, the display of
>> '*The Free Encyclopedia*' phrase is now localized to the visitor's first
>> preferred browser language. If there isn't a translation available, the
>> phrase will be displayed in English (view a screenshot
>> as it currently is today.
>> Additionally, a new A/B test
>> <https://www.mediawiki.org/wiki/Wikipedia.org_Portal_A/B_testing#A.2FB_test:…> will kick
>> off this week to determine if the listing of languages by article count can
>> be displayed in a more modern and streamlined way without decreasing usage
>> of the links. Our goal is to promote easy scrolling through the long list
>> of languages by article count, but in a dropdown format while also
>> providing greater discovery of the sister wiki project links.
>> More information on past and future work can be found on the wiki page
>> <https://www.mediawiki.org/wiki/Wikipedia.org_Portal> as well as the
>> sprint <https://phabricator.wikimedia.org/tag/discovery-portal-sprint/>
>> and backlog
>> boards. We're always interested in receiving constructive feedback from
>> the community: if you have a question or comment, please start a discussion
>> on the talk page
>> Deb Tankersley
>> Product Manager, Discovery
>> Wikimedia Foundation
>> Wikitech-ambassadors mailing list
> Wikitech-ambassadors mailing list
Dear users, developers and all people interested in semantic wikis,
We are happy to announce SMWCon Fall 2016 - the 13th Semantic MediaWiki
* Dates * September 28th to September 30th 2016 (Wednesday to Friday)
* Location * German Institute for International Educational Research
(DIPF), Schloßstraße 29, Frankfurt am Main, Germany.
* Conference page *
* Participants * Everybody interested in semantic wikis, especially
in Semantic MediaWiki, e.g. users, developers, consultants, business
SMWCon Fall 2016 will be supported by The German Institute for
International Educational Research (DIPF)  and Open Semantic Data
Association e. V. .
Following the success of this format the SMWCon will have one tutorial
and workshop day preceding two conference days.
Participating in the conference: To help us planning, you can already
informally register on the conference page, although a firm registration
will later be needed.
Contributing to the conference: If you want to present your work in the
conference please go to the conference page and add your talk there. To
create an attractive program for the conference, we will later ask you
to give further information about your proposals. Tutorials and
presentations will be video and audio recorded and will be made
available for others after the conference.
Among others, we encourage contributions on the following topics:
Applications of semantic wikis:
* Semantic wikis for enterprise workflows and business intelligence
* Semantic wikis for corporate or personal knowledge management
* Exchange on business models with semantic wikis
* Lessons learned (best/worst practices) from using semantic wikis or
* Semantic wikis in e-science, e-humanities, e-learning, e-health,
* Semantic wikis for finding a common vocabulary among a group of people
* Semantic wikis for teaching students about the Semantic Web
* Offering incentives for users of semantic wikis
* Challenges and obstacles for semantic wikis in business environments
Development of semantic wikis:
* Semantic wikis as knowledge base backends / data integration platforms
* Comparisons of semantic wiki concepts and technologies
* Community building, feature wishlists, roadmapping of Semantic MediaWiki
* Improving user experience in a semantic wiki
* Speeding up semantic wikis
* Integrations and interoperability of semantic wikis with other
applications and mashups
* Modeling of complex domains in semantic wikis, using rules, formulas etc.
* Access control and security aspects in semantic wikis
* Multilingual semantic wikis
For any other question and sponsorship opportunities, please do not
hesitate to contact Karsten Hoffmeyer <karsten at hoffmeyer.info>.
Hope to see you in Frankfurt am Main!
Lia Veja, Karsten Hoffmeyer
(Members of the Organizing Committee)
This week's ArchCom-RFC meeting is about T89331 ("Replace Tidy in MW
parser with HTML 5 parse/reserialize"). Information about the
goings-on of ArchCom continues to exist on the ArchCom Status page:
...and also copied below for your convenience.
My understanding is that the authors feel pretty good about the
implementation, and are looking for help figuring out how to implement
a successful migration.
Other handy links and information:
This week's meeting: <https://phabricator.wikimedia.org/E203>
RFC for this week's meeting: <https://phabricator.wikimedia.org/T89331>
Subject of the RFC: Replace Tidy in MW parser with HTML 5 parse/reserialize
Location: #wikimedia-office IRC channel
Time: 2016-06-08 Wednesday 21:00 UTC (2pm PDT, 23:00 CEST)
I'm looking forward to chatting with you there!
Source of [[mw:Architecture_committee/Status]], where "phab:" links
are pointers to https://phabricator.wikimedia.org
This page provides status update for [[Requests for
comment|ArchCom-RFCs]], with an emphasis on ArchCom team member. As
of this writing on 2016-04-29, this update is an experiment discussed
[[Topic:T2zctt083izvx07l|weekly ArchCom update discussion on the
"ArchCom/Team practices" talk page]].
===== Recent RFC meetings =====
* ArchCom Planning meeting 2016W22: 2016-06-01: [[Phab:E197]] (E156/9)
** Notes: [[Architecture committee/2016-06-01]]
* ArchCom-RFC office hour 2016W22: 2016-06-01: [[Phab:E198]] (E66/37)
** Security discussion, including:
*** CSP - [[Phab:T135963|T135963]]
===== Upcoming RFC meetings =====
*ArchCom Planning meeting 2016W23: 2016-06-08: [[Phab:E202]] (E156/10)
**Notes: [[Architecture committee/2016-06-08]]
*ArchCom-RFC office hour 2016W23: 2016-06-08: [[Phab:E203]] (E66/38)
** [[Phab:T89331|T89331 Replace Tidy in MW parser with HTML 5
===== Entering Final Comment Period =====
===== Recently Approved =====
==== RFC inbox ====
* [[phab:tag/archcom-rfc/|ArchCom RFC board]]:
** Inbox zero on 2016-06-11.
===== Shepherd status =====
** Multi-content revisions (T107595) is interesting
** Software Quality working group?
** Working on Multi Content Rev Spec with Brion
** T113034 [[phab:T113034|RFC: Overhaul Interwiki map, unify with
Sites and WikiMap]]: checking in with Adam
** T89733 (approved, with Stas driving implementation)
** Working with [[User:BSitzmann (WMF)|BSitzmann]] on
[[Phab:T132597|T132597]] (no longer an RFC)
need to start the second part, but the recent comments have me
confused. I'll need to talk to Timo and figure out what the subject of
part two should be.
** Starting to use [[Phab:Z425]] as asynchronous ArchCom-RFC channel,
testing Conpherence use for means of piloting ArchCom working groups.
We may still have more separate triage discussions, but I'm waiting to
get feedback on [[phab:T135674|T135674]].
** Working with [[User:DPatrick (WMF)|DPatrick]] on [[Wikimedia
Security Team]] issues in an attempt to be useful there.
** [[Phab:T89331|T89331 (Replace Tidy in MW parser with HTML 5
parse/reserialize)]] - should meet to discuss migration rather than
** T114444 [[phab:T114444|RFC: Introduce notion of DOM scopes in
** Section anchors - will update T18691
** CSP - [[Phab:T135963|T135963]] - Will shepherd
** Local storage abstraction [[Phab:T121646|T121646]] working with
Fundraising on this to move cookies into local storage; not an RFC
yet, but may become one.
===== No activity in the last two weeks =====
* T122942 [[phab:T122942|RFC: Support language variants in the
* T39902 [[phab:T39902|RFC: Implement rendering of redlinks in
Parsoid]] (no shepherd)
* T18691 [[phab:T18691|RFC: Section headings should have a clickable
* T111588 [[phab:T111588|RFC: API-driven web front-end]] (Timo)
* T123753 [[phab:T123753|Establish retrospective reports for Security
and Performance incidents]] (RobLa)
* T122825 [[phab:T122825|Service ownership and minimum maintenance
* T105766 [[phab:T105766|RFC: Dependency graph storage]] (Gabriel)
* T124504 [[phab:T124504|Transition WikiDev '16 working areas into
working groups]] (RobLa)
* T66214 [[phab:T66214|Use content hash based image / thumb URLs &
define an official thumb API]] (Brion)
* T91162 [[phab:T91162|RFC: Shadow namespaces]] (Brion)
* T128351 [[phab:T128351|RFC: Notifications in core]] (Brion)
* T122825 [[phab:T122825|Service ownership and minimum maintenance
* T54807 [[phab:T54807|Identify and remove legacy preferences from
MediaWiki core]] (no shepherd)
* T88596 [[phab:T88596|Improving extension management]] (Daniel)
===== Useful Phab links =====
* [[phab:maniphest/query/xc.j4DEYcjwu/#R|Query for shepherd assignments]]
* [[phab:search/query/lgPo47yENoTl/#R|Query for all ArchCom RFCs]]
* [[phab:project/board/52/|ArchCom-RfCs board]]
On Tuesday, May 31 we have deployed a change to the production cluster that
sets MathML with SVG fall-back as the default rendering mode for
mathematical formulae for all Wikimedia projects~. This change brings
scaleable and selectable formulae to the whole Wikimedia community, not
just logged-in users, thus opening new perspectives for better rendering,
accessibility, search, equation sharing, font and unicode support, styling,
We are very excited about this feature seeing the light of day, not only
because of the visible improved experience for our reader and editors, but
also because this project has been carried out in collaboration with the
community. In particular, this achievement would not have been possible
without Moritz Schubotz (aka User:Physikerwelt), who has been the lead
developer of Mathoid, the rendering service responsible for producing the
MathML and SVG code that the end-users see on the web-site.
You can read more about this awesome feature on the MathML Association’s
The WMF Services Team
Marko Obrovac, PhD
Senior Services Engineer