Wikitech-l January 2018

64 participants
70 discussions

Missing Section Headings
by Marc Riddell 13 Sep '24

13 Sep '24

Hello, I have been a WP editor since 2006. I hope you can help me. For some reason I no longer have Section Heading titles showing in the Articles. This is true of all Headings including the one that carries the Article subject's name. When there is a Table of Contents, it appears fine and, when I click on a particular Section, it goes to that Section, but all that is there is a straight line separating the Sections. There is also no button to edit a Section. If I edit the page and remove the "== ==" markers from the Section Titles, the Title then shows up, but not as a Section Heading. Also, I don't have any Date separators on my Want List. This started 2 days ago. Any thoughts? Thanks, Marc Riddell [[User:Michael David]]

10 11

How to make commits from mirrored Wikimedia repos show up on your GitHub profile
by Bartosz Dziewoński 27 Jun '24

27 Jun '24

I know it has been annoying a couple of people other than me, so now that I've learned how to make it work I'll share the knowledge here. tl;dr: Star the repositories. No, seriously. (And yes, you need to star each extension repo separately.) (Is there a place on mw.org to put this tidbit on?) ------- Forwarded message ------- From: "Brian Levine" <support(a)github.com> (GitHub Staff) To: matma.rex(a)gmail.com Cc: Subject: Re: Commits in mirrored repositories not showing up on my profile Date: Tue, 09 Jul 2013 06:47:19 +0200 Hi Bartosz In order to link your commits to your GitHub account, you need to have some association with the repository other than authoring the commit. Usually, having push access gives you that connection. In this case, you don't have push permission, so we don't link you to the commit. The easy solution here is for you to star the repository. If you star it - along with the other repositories that are giving you this problem - we'll see that you're connected to the repository and you'll get contribution credit for those commits. Cheers Brian -- Matma Rex

3 3

Research FAQ gets a facelift
by Dario Taraborelli 25 Jun '24

25 Jun '24

We just released a new version of Research:FAQ on Meta [1], significantly expanded and updated, to make our processes at WMF more transparent and to meet an explicit FDC request to clarify the role and responsibilities of individual teams involved in research across the organization. The previous version – written from the perspective of the (now inactive) Research:Committee, and mostly obsolete since the release of WMF's open access policy [2] – can still be found here [3]. Comments and bold edits to the new version of the document are welcome. For any question or concern, you can drop me a line or ping my username on-wiki. Thanks, Dario [1] https://meta.wikimedia.org/wiki/Research:FAQ [2] https://wikimediafoundation.org/wiki/Open_access_policy [3] https://meta.wikimedia.org/w/index.php?title=Research:FAQ&oldid=15176953 *Dario Taraborelli *Head of Research, Wikimedia Foundation wikimediafoundation.org • nitens.org • @readermeter <http://twitter.com/readermeter>

2 1

bluejeans
by Jeremy Baron 22 Feb '23

22 Feb '23

Hi, On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote: > We will be holding this brownbag in 25 minutes. The Bluejeans link has > changed: > > https://bluejeans.com/396234560 I'm not familiar with bluejeans and maybe have missed a transition because I wasn't paying enough attention. is this some kind of experiment? have all meetings transitioned to this service? anyway, my immediate question at the moment is how do you join without sharing your microphone and camera? am I correct thinking that this is an entirely proprietary stack that's neither gratis nor libre and has no on-premise (not cloud) hosting option? are we paying for this? -Jeremy

9 16

New DB_REPLICA constant; DB_SLAVE deprecated
by Aaron Schulz 04 Jul '20

04 Jul '20

As of 950cf6016c, the mediawiki/core repo was updated to use DB_REPLICA instead of DB_SLAVE, with the old constant left as an alias. This is part of a string of commits that cleaned up the mixed use of "replica" and "slave" by sticking to the former. Extensions have not been mass converted. Please use the new constant in any new code. The word "replica" is a bit more indicative of a broader range of DB setups*, is used by a range of large companies**, and is more neutral in connotations. Drupal and Django made similar updates (even replacing the word "master"): * https://www.drupal.org/node/2275877 * https://github.com/django/django/pull/2692/files & https://github.com/django/django/commit/beec05686ccc3bee8461f9a5a02c607a023… I don't plan on doing anything to DB_MASTER, since it seems fine by itself, like "master copy", "master tape" or "master key". This is analogous to a master RDBMs database. Even multi-master RDBMs systems tend to have a stronger consistency than classic RDBMs slave servers, and present themselves as one logical "master" or "authoritative" copy. Even in it's personified form, a "master" database can readily be thought of as analogous to "controller", "governer", "ruler", lead "officer", or such.** * clusters using two-phase commit, galera using certification-based replication, multi-master circular replication, ect... ** https://en.wikipedia.org/wiki/Master/slave_(technology)#Appropriateness_of_… *** http://www.merriam-webster.com/dictionary/master?utm_campaign=sd&utm_medium… -- -Aaron

4 3

Roadmap for CX?
by Strainu 06 Sep '18

06 Sep '18

Following the recent outage, we've had a new series of complaints about the lack of improvements in CX, especially related to server-side activities like saving/publishing pages. Now, I know the team is involved in a long-term effort to merge the editor with the VE, but is there an end in sight for that effort? Can I tell people who ask "look, 6 more months then we'll have a much better translation tool"? Is there a publicly available roadmap for this project and more generally, for CX? Thanks, Strainu

5 8

Reboot of irc.wikimedia.org
by Alexandros Kosiaris 22 Feb '18

22 Feb '18

Hello everyone, This is to inform you that on Monday Feb 22nd 2018 ~10:00 UTC, the infrastructure powering irc.wikimedia.org will be rebooted for security upgrades. This is expected to only impact bots that are using irc.wikimedia.org AND are not able to automatically reconnect on connection failure. From recent experience (the equipment was rebooted 210 ago last time, with no fallout) those are very limited in number these days. Regards, -- Alexandros Kosiaris <akosiaris(a)wikimedia.org>

2 3

RevisionInsertComplete vs. RevisionRecordInserted
by Stas Malyshev 01 Feb '18

01 Feb '18

Hi! I've noticed that RevisionInsertComplete hook is now deprecated in favor of RevisionRecordInserted. However, EventBus still uses RevisionInsertComplete. Is this going to change soon? If so, will the underlying event/topic change too? I couldn't find anything in Phabricator about this - is there plan to change it or still use old hook for now and foreseeable future? Thanks, -- Stas Malyshev smalyshev(a)wikimedia.org

2 2

+2 nomination for WMDE-leszek in mediawiki/*
by Addshore 01 Feb '18

01 Feb '18

Hi, I've filed <https://phabricator.wikimedia.org/T185593>, nominating WMDE-leszek for +2 in mediawiki/ repos. -- Addshore

2 1

2018-01-31 Scrum of Scrums meeting notes
by Grace Gellerman 31 Jan '18

31 Jan '18

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-01-31 *= 2018-01-31 =* == Callouts == * Parsing team had planned to replace Tidy on an additional 200+ wikis including 4 large/medium wikis today (Jan 31). ( https://phabricator.wikimedia.org/T185945, https://phabricator.wikimedia.org/T184656 ) But, this has been postponed to Feb 6 because this week is a no M/W train, no SWAT week as per https://wikitech.wikimedia.org/wiki/Deployments#Week_of_January_29th * https://phabricator.wikimedia.org/T186133 - login issues on expired beta commons sessions, product and QA are having trouble testing things == Audiences == === Readers === ==== iOS native app ==== * Blocked by: * Blocking: * Updates: ** Dev Summit / All Hands ** Continuing work on 5.8.0 - Synced Reading Lists ( https://phabricator.wikimedia.org/tag/ios-app-v5.8.0-manatee-on-a-skateboar… ) ==== Android native app ==== * Blocked by: continuous integration - https://phabricator.wikimedia.org/T185931 * Blocking: * Updates: ** Dev Summit / All Hands ** Ready to release current version (improved reading list performance) ==== Reading Web ==== * Blocked by: * Blocking: * Updates: ==== Reading Infrastructure ==== * Blocked by: * Blocking: * Updates: ** Dev Summit / All Hands, not much else happened ** Trying again to get the summary switched over this week, probably more gradually by not forcing rerenders at first. ===== Maps ===== * Blocked by: * Blocking: * Updates: ==== Multimedia ==== * Thanks to WMDE and Search (and others) for meatspace availability last week, it was very helpful * Beta commons login issues related to expired sessions seem persistent on beta cluster - specifically on UploadWizard, not sure what's happening there - https://phabricator.wikimedia.org/T186133 ==== Discovery ==== * Blocked by: * Blocking: * Updates: === Community Tech === * Blocked by: Waiting on security review for GlobalPreferences * Blocking: * Updates: Beginning to work on ping users from edit summary wish; Close to wrapping up work on Grant metrics tool; Investigating other wishes === Contributors === ==== Editing ==== * Blocked by: * Blocking: * Updates: ==== Parsing ==== * Blocked by: Parsoid clients (VE, CX, Flow) needing to review and approve https://gerrit.wikimedia.org/r/#/c/402455/ * Blocking: * Updates: ** Had originally planned to replace Tidy on an additional 200+ wikis including 4 large/medium wikis today (Jan 31). ( https://phabricator.wikimedia.org/T185945, https://phabricator.wikimedia.org/T184656 ) But, this has been postponed to Feb 6 because this week is a no M/W train, no SWAT week. ** Would appreciate DBA input on https://phabricator.wikimedia.org/T173943#3933570 .. Kunal has added the #DBA phab tag already and so this SoS notification is just an FYI. ** Question to everyone: Every once in a while, Parsoid makes changes that requires downstream clients to update / approve changes. Longer-term, once Parsoid HTML is used for everything, we have a formal content-negotiation process that includes content versioning and version headers, but for now, when our clients are all internal and the contention negotiation support is not yet in place in the Parsoid + RESTBase stack, something quicker and simpler for faster change deployment is what we need. We have followed a combo of gerrit / phab / irc / email / SoS for this so far, but suggestions welcome for of how best to get everyone's attention and action in a timely fashion. Or is our combo process the best way to make this happen? ==== Global Collaboration ==== ===== Collaboration ===== * Mostly, our team is getting up to speed on Maps, our new assignment. * Collaboration and Language are now two separate teams again. ===== Language ===== * Blocked by: * Blocking: * Updates: ==== UI Standardization ==== ** No OOUI release today * Ongoing: ** OOUI: Toolbar demo overhaul in preparation of the icon refinement ** Style Guide *** Preparation for goal v1 of the Style Guide, see https://phabricator.wikimedia.org/tag/wikimediaui_style_guide/ ** AnnualReport *** Fixing its accessibility issues == Technology == === Analytics === * Updates: **All-hands +I offsite this week - nothing to mention === Cloud Services === * Blocked by: * Blocking: * Updates: === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** Starting work on adding EventLogging to CentralNotice, initially along with existing impression tracking, but at a low sample rate ** Upgrading our Civi instance to latest version ** Continuing work on new API for main credit card processor ** Fixing various vagrant issues relating to OS update === MediaWiki Platform === * Blocked by: * Blocking: * Updates: ** Developer Summit and All Hands *** Audiences Technology Working Group meetings *** Evolving the MediaWiki Architecture *** Supporting Third-Party Use of MediaWiki ** Filed "DiscussThis" RFC T185607 ** Multi-Content Revisions/Actor Table/Comment Table work on-going ** TemplateStyles ready to deploy === Performance === * Blocked by: Review of mcrouter puppet code (SRE knows) * Blocking: * Updates: ** Offsite/DevSummit/All Hands ** Adding perf monitoring of svwiki in preparation for release of TemplateStyles ** Continued improvements to Thumbor based on new error logging === Release Engineering === * Blocked by: * Blocking: * Updates: === Research === * Blocked by: * Blocking: * Updates: === Scoring Platform === * Blocked by: * Blocking: * Updates: === Search Platform === * Blocked by: none * Blocking: none * Updates: ** DevSummit/All Hands/Offsite week ** Phonetic search writeup published: https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Overview_of_Phonetic… next testing prototype on RelForge ** Hewiki test analyzed: https://analytics.wikimedia.org/datasets/discovery/reports/Second_MLR_Test_… ** Working on refactoring for search profiles: https://phabricator.wikimedia.org/T183279 ** Working on query parsing refactoring: https://phabricator.wikimedia.org/T185108 ** Working on Serbian analyzer for ES: https://phabricator.wikimedia.org/T183015 ** Added more data to category RDF dumps: https://phabricator.wikimedia.org/T173980 and https://phabricator.wikimedia.org/T185127 ** Deep category search patches in review: https://phabricator.wikimedia.org/T185127 and https://phabricator.wikimedia.org/T184840 === Security === * Blocked by: * Blocking: * Updates: === Services === * Blocked by: global collaboration on flow * Blocking: none * Updates: ** slow === Technical Operations === * Blocked by: * Blocking: * Updates: == Wikidata == * Work on Lexeme extension continues with proper persistance and diff support * Constraint violations now checked on qualifiers and references: https://phabricator.wikimedia.org/T168532 * Tuning usage tracking to get full recent changes integration back: https://phabricator.wikimedia.org/T178079 * Started logging warnings on pages that use too many items: https://phabricator.wikimedia.org/T184319 * Wikibase motivated a (tiny) fix in CoreParserFunctions: https://phabricator.wikimedia.org/T182800

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l January 2018