Wikitech-l August 2019

wikitech-l@lists.wikimedia.org

50 participants
57 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

Several primary database masters switchovers scheduled (read-only required)
by Manuel Arostegui 26 Sep '19

26 Sep '19

Hello, The following primary database masters will be switched over during the next few weeks (more details at https://phabricator.wikimedia.org/T230788): Impact: *Writes will be blocked* *Reads will remain unaffected* These are the concrete days, hours and affected wikis: * s8: 10th Sept from 05:00-05:30 UTC. The affected wiki is: wikidatawiki - tracking task: T230762 * s2: 17th Sept from 05:00-05:30 UTC. The list of affected wikis is at: https://raw.githubusercontent.com/wikimedia/operations-mediawiki-config/mas… - tracking task: T230785 * s3: 24th Sept from 05:00-05:30 UTC. The list of affected wikis is at: https://raw.githubusercontent.com/wikimedia/operations-mediawiki-config/mas… - tracking task: T230783 * s4: 26th Sept from 05:00-05:30 UTC. The affected wiki is: commonswiki - tracking task: T230784 If everything goes well, we do not expect to use those 30 minutes of read-only and rather just a few minutes. We will email send an email the day of each failover before and after it is done. Sorry for any inconvenience this might cause.

2 9

m1 (etherpad, bacula, librenms, rt, racktables) db primary master switchover: 10th Sept 16:00 UTC
by Manuel Arostegui 10 Sep '19

10 Sep '19

Hello, The current primary master for m1 (db1063), which is mostly for internal services + etherpad isn't in a great healthy status: it is an old host, which needs to be decommissioned and which is having disks failing pretty much every week (plus disks on predictive failure). We have decided to fail it over one of the newer hosts, db1135: https://phabricator.wikimedia.org/T231403 We have scheduled this switchover for: Tuesday 10th September at 16:00 UTC This failover should be rather quick and would only take a few seconds (while we re-load the haproxy) - during those few seconds, the following services will be on read-only: bacula etherpadlite librenms puppet racktables rt Communication will happen at #wikimedia-operations If you are around at that time and want to help with the monitoring, please join us! Thanks

2 7

[Tech Talks] Sept 4, 2019, 6 PM UTC, Documenting Wikimedia technical projects
by Sarah R 03 Sep '19

03 Sep '19

Hi Everyone, It's time for Wikimedia Tech Talks 2019 Episode 7! This talk will take place *Sept 4, 2019 at 6PM UTC*. *Topic:* Documenting Wikimedia technical projects *Speaker:* Sarah R. Rodlund, Technical Writer -- Developer Advocacy *Summary: * This talk will discuss what technical writers do and why they are critical members of the Wikimedia technical community. You will learn more about the skills needed to be a technical writer and how to build these skills by participating on Wikimedia and other open source projects. The talk will also cover some ongoing initiatives to improve technical documentation for Wikimedia projects. *YouTube stream for viewers:* https://www.youtube.com/watch?v=GKvyk4VAPb0 During the live talk, you are invited to join the discussion on IRC at #wikimedia-office You can watch past Tech Talks here: https://www.mediawiki.org/wiki/Tech_talks If you are interested in giving your own tech talk, you can learn more here: https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te… Many kindnesses, Sarah R. Rodlund Technical Writer, Developer Advocacy <https://meta.wikimedia.org/wiki/Developer_Advocacy> srodlund(a)wikimedia.org

1 1

Upcoming Search Platform Office Hours—September 4th
by Trey Jones 03 Sep '19

03 Sep '19

The Search Platform Team <https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds office hours the first Wednesday of each month. Come talk to us about anything related to Wikimedia search! Feel free to add your items to the Etherpad Agenda for the next meeting. Details for our next meeting: Date: Wednesday, Sep 4th, 2019 Time: 15:00-16:00 GMT / 08:00-9:00 PDT / 11:00-12:00 EDT / 17:00-18:00 CEST Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours Google Meet link: https://meet.google.com/vyc-jvgq-dww Hope to talk to you in a week! Trey Jones Sr. Software Engineer, Search Platform Wikimedia Foundation UTC-4 / EDT

1 1

m5 (Wikitech) primary database master switchover
by Manuel Arostegui 03 Sep '19

03 Sep '19

Hello, We are going to switchover m5 (wikitech) primary database master on *Tuesday 3rd September at 13:00 UTC *https://phabricator.wikimedia.org/T229657 This switchover will also affect some Cloud services that will be handled on a different announcement. The current master (db1073) is an old and out of warranty hosts with several disks on predictive failure, it needs to be decommissioned. We will be failing over db1073 to db1133, a newer and more powerful host. We expect this to take around 15 minutes (or just a few seconds if everything goes fine). *Impact: * *- Writes will be blocked during the switchover* *- Reads will remain unaffected.* Communication will happen on #wikimedia-operations IRC channel. Thanks Manuel.

1 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 August 2019