Wikitech-l April 2019

wikitech-l@lists.wikimedia.org

69 participants
76 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

MediaWiki Language Extension Bundle 2019.04 release
by Kartik Mistry 07 May '19

07 May '19

Hello all, I would like to announce the release of MediaWiki Language Extension Bundle 2019.04. This bundle is The bundle is compatible with MediaWiki 1.31 and 1.32 or above and requires PHP 5.5.9 or above. Next MLEB is expected to be released in 3 months. If there are major changes or important bug fixes, we will do intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.04.tar… * sha256sum: 5fbbd39acd1cc0e1edbd542a390daf1992d1526134ceb69248cdb4dced58f3a9 * Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2019.04.tar… Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n * Report bugs to: https://phabricator.wikimedia.org/ * Talk with us at: #mediawiki-i18n @ Freenode Release notes for each extension are below. -- Kartik Mistry == Highlights and upgrade notes == == Babel == * Maintenance and localization updates only. == CleanChanges and cldr == * PHP entry point has been removed. Warning will be displayed for deprecated PHP entry point. (T140007) * Maintenance and localization updates. == LocalisationUpdate == * Maintenance updates only. == Translate == === Noteworthy changes === * Fixed fatal error on PageContentLanguage hook subscriber (T214358) * Replaced usage of mw.translateHooks with mw.hook. Deprecation warning will be shown while using functions under mw.translateHooks (T72031) * Added support for newer versions of the Elastica extension while maintaining backward compatibility for older version REL 1.31 (T218100) * Fixed page suggestion control on Special:PageMigration (T217726) * Fixed broken Special:PageMigration (T217727) * Add link to Special:PageMigration when page is marked for translation (T178642) * Removed display of the message group state for the source language (T160511) * Fixed invalid display of priority language notice (T217046) * Added better error handling in Special:SearchTranslations (T159221) *Display proper notice when translations to non-priority languages are blocked (T218777) *Fixed "proofreading" status appearing for source language on the MessageGroup and Language stats page (T160511) == UniversalLanguageSelector == * Various performance fixes. * Maintenance and localization updates. ==== Input Methods ==== * New tilde-based layouts for several languages of Africa: Kabyle, Kabiye, Kikuyu, Luganda, Lingala, Malagasy, Northern Sotho, Koyraboro Senni, Sango, Sotho, Venda. * Added Latin Pinyin transliteration keyboard ==== Fonts ==== * Added fonts for Church Slavonic. (T156843) -- Kartik Mistry | કાર્તિક મિસ્ત્રી kartikm.wordpress.com

1 1

Re: [Wikitech-l] [Wikidata-tech] wb_terms redesign
by Alaa Sarhan 04 May '19

04 May '19

> This is really a defective redesign. It reintroduced numeric IDs to be removed by T114902. See also T179928. We should reconsider reintroduce a new table to link unperfixed and perfixed entity ID. The new schema has been optimized as much as possible to allow maximum scalability as it will contain a massive amount of data that we hope it doubles or even triple in size as soon as we can. The ids changed here to integer as we have seperate tables at the top level and prefixes in those tables are redundant and only take up redundant space that accumulate to big amount very quickly. The old `wb_terms`, as well as the new schema, are not actually design for public use unless really necessary for your needs. If your needs can be addressed via Wikidata available APIs, you are very much encourage to switch to using those instead. In that case, you need not to worry about migrations and schema changes ever. > Also oppose any "partial migration for first XXX items" process in T221765: this makes queries much more complicated. Please first fill all data in the new schema, then discontinue the old table. Full migration is not possible unfortunately due to the current capacity of database master node. We tried to find a trade-off between the overhead we introduce to both disk usage and application logic complexity that will access those schemas. This will make our life at Wikidata also a little less pleasant for the migration period. We understand this is unusual migration and isn't a very easy one for a little while, that's why we want to help out with those queries and other inquiries as much as we can. If you have some queries you are running on `wb_terms`, it would of great help if you add them to a new Phab task on the Tool Builders migration board, in the Backlog column. https://phabricator.wikimedia.org/project/view/4014/ If you have any concrete suggestions regarding making this migration easier, we would also love to hear them. Please go ahead and add them on the same board in their own Phabricator tasks so that we can keep track of things more easily and follow up on them as soon as possible. On Thu, 25 Apr 2019 at 15:25, data_querier <data_querier(a)protonmail.com> wrote: > This is really a defective redesign. It reintroduced numeric IDs to be > removed by T114902. See also T179928. We should reconsider reintroduce a > new table to link unperfixed and perfixed entity ID. > > Also oppose any "partial migration for first XXX items" process in > T221765: this makes queries much more complicated. Please first fill all > data in the new schema, then discontinue the old table. > _______________________________________________ > Wikidata-tech mailing list > Wikidata-tech(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikidata-tech > -- Alaa Sarhan Full Stack Developer Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0https://wikimedia.de Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision!https://spenden.wikimedia.de Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

2 1

Gerrit: Please use /r/ over /r/p/ when cloning
by Paladox 02 May '19

02 May '19

Hello, In Gerrit 2.16 PolyGerrit takes over the /p/ url so cloning no longer works over that URL. Please convert to using /r/. /p/ is completely optional in Gerrit anyways so it's a matter of changing /r/p/ to just /r/ (you can update your config with the updated url by doing "sed -i -e 's/\/r\/p\//\/r\//' .git/config") We have this task https://phabricator.wikimedia.org/T222093 We also have this task to update prod and WMCS. See https://phabricator.wikimedia.org/T222093

1 1

Pending (false positive?) translations on Gerrit to Toolforge tools
by Derick Alangi 01 May '19

01 May '19

Hi, Looking at https://gerrit.wikimedia.org/r/dashboard/l10n-bot@translatewiki.net, there are pending translations to Toolforge tools which are failing due to false positives? AFAIK, Raimond usually cleans such up for MW extensions but I'm not sure for tools. So please if anyone knows the maintainers of these tools, he/she can just add them so they can review these translations and merge them? For a while now, they've been stacking on each other. Thanks! *--* *</Derick <https://www.mediawiki.org/wiki/User:X-Savitar>>*

6 9

Announcing MediaWiki 1.32.1
by Mukunda Modell 30 Apr '19

30 Apr '19

Although the archives have been available for quite some time, this minor patch release was never properly announced. So without further ado, I'd like to announce the availability of MediaWiki 1.32.1, you will find the requisite links below: ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.1.tar.gz Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.32/mediawiki-core-1.32.1.tar.gz Patch to previous version (1.32.0): https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.1.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.32/mediawiki-core-1.32.1.tar.gz.… https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.1.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.1.patch.gz.sig Public keys: https://www.mediawiki.org/keys/keys.html

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 April 2019