Wikitech-l September 2021

32 participants
37 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

Unsubscribe from mail list
by Arpit Maheshwari 11 Jan '23

11 Jan '23

This is a request to please kindly unsubscribe me from your mailing list

4 4

List related to repositories which haven't mediawiki/mediawiki-codesniffer
by Zoran Dori 10 Jan '23

10 Jan '23

Hello, can someone to update list https://phabricator.wikimedia.org/P10500 which contains repositories which haven't mediawiki/mediawiki-codesniffer. I found in list that much repositories are empty, and repositories which aren't available on Gerrit. So, can someone please update this list of repositories (in mediawiki/extensions) which haven't mediawiki/mediawiki-codesniffer, but at least, contains one PHP file. or to provide me command with which I can update list when I want, so I don't need to request it every time. Best regards, Zoran. P. S.: Happy weekend! :)

4 6

How we deploy code
by Tyler Cipriani 12 Oct '21

12 Oct '21

Last week, I spoke to a few of my Wikimedia Foundation colleagues about how we deploy code—I completely botched it. At the end of the conversation, I was pretty sure I'd only succeeded in making a complex process more opaque. I decided to write a blog to redeem myself: How We Deploy Code <https://phabricator.wikimedia.org/phame/post/view/253/how_we_deploy_code/> My goal was to write a very high-level overview of the process we use to deploy code to Wikimedia production. Hopefully, this is helpful. <3 – Tyler Cipriani (he/him) Engineering Manager, Release Engineering Wikimedia Foundation

6 6

What does "ltsrel" mean?
by Ike Hecht 06 Oct '21

06 Oct '21

I'm confused about what the term "ltsrel" means. The way I understand it, it *should* mean that the extension supports only Long Term Support versions of MediaWiki. It would have a branch for every LTS version of MediaWiki like REL1_31 and REL1_35, but not for REL1_32, REL1_33 or REL1_34. However, on the Compatibility <https://www.mediawiki.org/wiki/Compatibility#MediaWiki_extensions> page, the rel and ltsrel policies are described as: * release branches (key: rel): For every MediaWiki release, there is a corresponding branch in the extension. So e.g. if you use MediaWiki 1.36, you should use the REL1_36 branch of the extension. * long-term support release branches (key: ltsrel): For every MediaWiki release, there is a corresponding branch in the extension, following the Version lifecycle release policy. These sound exactly alike to me.

2 4

Parsoid/JS is EOL
by Subramanya Sastry 30 Sep '21

30 Sep '21

Hello everyone, MediaWiki 1.31 has reached EOL. Consequently, Parsoid/JS (the javascript version of Parsoid) is also EOL starting today. Parsoid was originally implemented in Javascript. It was ported to PHP in 2019 and the PHP port is now part of all MediaWiki releases. With the EOL of the MediaWiki 1.31 LTS, LTS support transfers to Parsoid/PHP 0.12, which was included as part of the MediaWiki 1.35 LTS distribution. Parsoid/JS has only been receiving security releases since 2020 and will no longer get any security updates. We recommend all Parsoid users switch over to Parsoid/PHP. Subbu. on behalf of the Content Transform Team (formerly the “Parsing Team”)

1 0

Security and maintenance release: 1.31.16 / 1.35.4 / 1.36.2
by Sam Reed 30 Sep '21

30 Sep '21

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 September 2021