Wikitech-l June 2017

wikitech-l@lists.wikimedia.org

68 participants
72 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 28 Jun '24

28 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 23 Feb '23

23 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

"How can MW 1.27.1 be stable with a broken hook?"
by Stephan Gambke 03 Jul '17

03 Jul '17

See https://phabricator.wikimedia.org/T118683 https://gerrit.wikimedia.org/r/#/c/244044 introduced a change that causes warnings on extensions that implemented the TitleMoveComplete hook signature according to documentation at https://www.mediawiki.org/wiki/Manual:Hooks/TitleMoveComplete. https://gerrit.wikimedia.org/r/#/c/249189/ tried to fix it but did not. Since then several MW versions have been released without a fix. All that happened was that the hook description on mw.org got a warning banner. Any comments? Any suggestions as to a way forward? As 244044 is clearly breaking stuff, what about completely reverting it? Stephan

3 5

Readers monthly update for June 2017
by Chris Koerner 03 Jul '17

03 Jul '17

Hello, Here we are again. Another month, and another update from the Readers (previously Reading) department at the Wikimedia Foundation. One more month of these and we'll have a turkey. :) [0] ==Discussions== === Apps=== * Android released an update improving offline storage and Reading List experience. * Android began work on support the zim archive format in the app, based on Community Wishlist request. [1] * iOS released version 5.5.0 which includes the all new Places tab, which focuses on geolocation based discovery. This update also improves how "In the News" look and work, adds a more prominent search box and other improvements. * iOS began work on 5.6.0 which will support reading modes (specifically a dark mode for night reading) and "On this Day" content in the feed. * Survey results from both apps on reading lists usage was completed, with findings available at Reading lists survey results. [2] === Web === * Moving the intro above the infobox on mobile web lead a significant increase on performance metrics [3] === New Readers === * New Reader updates can be found at Meta [4] === Multimedia === * A UX design heuristic evaluation was conducted and results turned into Phabricator tasks for 3D file (STL) support. A number of design refinements are being turned into a specification. The team has been prioritizing and working on 3D tasks in anticipation of a future launch. In the forthcoming month, additional consultation will be done on the wikis about potential moderation considerations for the 3D file (STL) type. [5] === Discovery === The Discovery team provides weekly updates. Here are their updates for June. * 2017-06-05 [6] * 2017-06-12 [7] * 2017-06-19 [8] * 2017-06-26 [9] [0] https://wikipedia.org/wiki/Special:MyLanguage/Ten-pin_bowling [1] https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Categories/R… [2] https://www.mediawiki.org/wiki/Wikimedia_Apps/Synced_Reading_Lists/Reading_… [3] https://phabricator.wikimedia.org/phame/post/view/15/investigating_a_perfor… [4] https://meta.wikimedia.org/wiki/New_Readers/Updates [5] https://phabricator.wikimedia.org/project/board/48/query/GMIMsF0oKK9t/?filt… [6] https://www.mediawiki.org/wiki/Discovery/Status_updates/2017-06-05 [7] https://www.mediawiki.org/wiki/Discovery/Status_updates/2017-06-12 [8] https://www.mediawiki.org/wiki/Discovery/Status_updates/2017-06-19 [9] https://www.mediawiki.org/wiki/Discovery/Status_updates/2017-06-26 --- 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 Wikimedia Foundation

2 1

Discovery Weekly Update for the week starting 2017-06-26
by Chris Koerner 01 Jul '17

01 Jul '17

Hello everyone, Here's the weekly update for Discovery and the last update in June. Can you believe it‽ As always, feedback and questions are welcome. ==Discussions== === Search === * Evaluated several training set sizes for the learning-to-rank models [0] * Completed several successful load tests on the servers for learning-to-rank query plugin [1] * Fixed a bug with second try searching using language detection [2] * Updated CirrusSearch to not depend on spaces to activate proximity rescoring (phrase rescore) [3] * Explore similar pages, categories and languages A/B test was activated on June 29, 2017 [4] === Analysis === * Updated the dashboards polloi package that now allows country names and assigning of ASCII region names [5] === Portal === * Statistics and translations were updated on the Wikipedia.org portal page on June 27, 2017 [6] [7] === Interactive === * A bug where coordinates were being passed incorrectly to external map services was fixed in production [8] * Discussion and a patch uploaded to update Kartographer so that jQuery 3 doesn't break things [9] [0] https://phabricator.wikimedia.org/T168664 [1] https://phabricator.wikimedia.org/T169002 [2] https://phabricator.wikimedia.org/T168302 [3] https://phabricator.wikimedia.org/T152094 [4] https://phabricator.wikimedia.org/T149809 [5] https://phabricator.wikimedia.org/T167913 [6] https://phabricator.wikimedia.org/T128546 [7] https://phabricator.wikimedia.org/T142582 [8] https://phabricator.wikimedia.org/T160782 [9] https://phabricator.wikimedia.org/T168744 -- The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner Community Liaison Wikimedia Foundation

1 0

Upgrade to jQuery 3 is coming
by Krinkle 30 Jun '17

30 Jun '17

Hey all, TL;DR: In April 2017, the jQuery library in MediaWiki core was upgraded from 1.x to 3.x (the current stable version), with the jQuery Migrate plugin enabled to ease migration. We temporarily still load jQuery 1.x on Wikimedia wikis. Read about the API changes at https://jquery.com/upgrade-guide/3.0/ == Upgrade guide == An overview of the important changes is available at: https://jquery.com/upgrade-guide/3.0/ This page also contains advice on how to migrate your code. In most cases it involves fairly simple changes, such as using a different method name, or adding quotes in selectors. The vast majority of the added requirements and removed methods are restored through the jQuery Migrate plugin with a deprecation warning in the console. As such, it's unlikely your code will require any immediate changes. If you do find a deprecation warning in the console, you can use the warning documentation to find out more: https://github.com/jquery/jquery-migrate/blob/e967c3b98b/warnings.md Once jQuery 3 is in Wikimedia production (with jQuery Migrate) it will be easy to find uses of deprecated methods with the deprecation warnings. However, you don't need to wait for August to start migrating. The methods removed in jQuery 3 have been deprecated for a while already, and their replacements are already available in jQuery 1.x in production, today. == Timeline == * April 2017: jQuery 3 lands in MediaWiki core master with jQuery Migrate plugin. * April to July 2017: Testing and fixing of issues arising from the switch. * July 2017: jQuery 3 enabled in Wikimedia's Beta Cluster. [1] * August 2017: jQuery 3 enabled on Wikimedia wikis in production. jQuery 3 will also be released as part of MediaWiki 1.30.0 (expected in November 2017). [2] As part of MediaWiki 1.30, inclusion of jQuery Migrate will made configurable so that sites that have already migrated may disable the plugin for better run-time performance. Track progress at <https://phabricator.wikimedia.org/T124742>. -- Krinkle [1] https://www.mediawiki.org/wiki/Beta_Cluster [2] https://www.mediawiki.org/wiki/MediaWiki_1.30

3 2

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 June 2017