Wikitech-l July 2023

23 participants
28 discussions

EBNF grammar project status?
by Steve Bennett 01 Apr '25

01 Apr '25

What's the status of the project to create a grammar for Wikitext in EBNF? There are two pages: http://meta.wikimedia.org/wiki/Wikitext_Metasyntax http://www.mediawiki.org/wiki/Markup_spec Nothing seems to have happened since January this year. Also the comments on the latter page seem to indicate a lack of clear goal: is this just a fun project, is it to improve the existing parser, or is it to facilititate a new parser? It's obviously a lot of work, so it needs to be of clear benefit. Brion requested the grammar IIRC (and there's a comment to that effect at http://bugzilla.wikimedia.org/show_bug.cgi?id=7 ), so I'm wondering what became of it. Is there still a goal of replacing the parser? Or is there some alternative plan? Steve

26 217

Phabricator upstream shutdown
by Brian Wolff 21 Mar '25

21 Mar '25

It sounds like phabricator upstream is going away: https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_op… Just curious, are we planning to continue using it long term or move to something else? -- Brian

10 12

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 nitens.org • @readermeter <http://twitter.com/readermeter>

2 1

[action requested] Technical Decision-Making Retrospective Survey
by Moriel Schottlender 23 Apr '24

23 Apr '24

Hello all, The Technical Decision-Making Forum Retrospective team <https://www.mediawiki.org/wiki/Technical_decision_making> invites you to complete a survey about Wikimedia's technical decision-making processes. While there will be more ways to participate, this is the first and most important step in our data collection. It aims to gather information about your experience, thoughts, and needs regarding the process of making technical decisions across the Wikimedia technical spaces. This survey will be used for gathering information about the process and the needs around technical decision-making that touches our production systems. You can find the survey link here: https://wikimediafoundation.limesurvey.net/885471?lang=en Who should take this survey? People who do technical work that relies on software maintained by the Wikimedia Foundation (WMF) or affiliates. If you contribute code to MediaWiki or extensions used by Wikimedia, or you maintain gadgets or tools that rely on WMF infrastructure, this survey is for you. What is the deadline? *August 7th, 2023 * What will the Retrospective team do with the information? The retrospective team will synthesize the collected data and publish an anonymized analysis that will help leadership make decisions about the future of the process. We will collect anonymized information that we will analyze in two main ways: - Sentiments based on demographic information: these will tell us whether there are different needs and desires from different groups of people. - General needs and perceptions about decision-making in our technical spaces: This will help us understand what kind of decisions happen in the spaces, who is involved, and how to adjust our processes accordingly. Is the survey the only way to participate? The survey is the most important way for us to gather information because it helps us gather input in a structured manner. But it will not be the only way you can share your thoughts with us - we will have more information soon about upcoming listening sessions where you can talk with us live. In the meantime, you are always welcome to leave feedback on the talk page: https://www.mediawiki.org/wiki/Talk:Technical_decision_making/Technical_Dec… Where can I see more information? There are several places where you can find more information about the Technical Decision-Making Process Retrospective: - The original announcement about the retrospective from Tajh Taylor: https://lists.wikimedia.org/hyperkitty/list/[email protected]/… - The Technical Decision-Making Process general information page: https://www.mediawiki.org/wiki/Technical_decision_making - The Technical Decision-Making Process Retrospective on MediaWiki: https://www.mediawiki.org/wiki/Technical_decision_making/Technical_Decision… - Phabricator ticket: https://phabricator.wikimedia.org/T333235 How to contact the retrospective core team: - Write to the core team mailing list: tdf-retro-2023(a)lists.wikimedia.org - The Technical Decision-Making Process Retrospective on MediaWiki talk page: https://www.mediawiki.org/wiki/Talk:Technical_decision_making/Technical_Dec… Thank you, Moriel, on behalf of the TDMP Retro Core Group Core group: - Moriel Schottlender (chair) - Daniel Kinzler - Chris Danis - Kosta Harlan - Temilola Adeleye -- Moriel Schottlender (she/her <https://pronoun.is/she>) Principal Software Engineer Wikimedia Foundation https://wikimediafoundation.org/

3 6

Announcing: Path review board
by Brian Wolff 04 Oct '23

04 Oct '23

Yesterday there was a conversation about code review on irc and among other things, how sometimes patches can get "stuck". I had an idea for a way to improve things. I'm not sure if it is a good idea, but there's only one way to find out. So without further ado, announcing the Code Review Patch Board: https://www.mediawiki.org/wiki/Code_review/patch_board In short - each person is allowed to list one of their patches on the board that they would really like to see reviewed. You can only list one patch at a time, and it should be a patch that you have been unable to get review for for at least a week through normal means. See the page for the full list of guidelines. I encourage people to give it a try. Add a patch you wrote that you cannot get a review for. Or if you have +2 rights, try giving some love to these underloved patches. I would also love to hear feedback on the general idea as well as the current guidelines. To repeat, the url is: https://www.mediawiki.org/wiki/Code_review/patch_board Thanks, bawolff

4 5

Global Lua modules and templates
by Felipe Schenone 29 Aug '23

29 Aug '23

Hi! As many of you know, a central global repository for Lua modules and templates has been a frequent request since the early days of the movement. This year, I programmed a JavaScript tool called Synchronizer https://www.mediawiki.org/wiki/Synchronizer (inspired on a previous tool called DiBabel by User:Yurik) The tool allows to synchronize (that is, automatically copy) Lua modules across Wikimedia wikis, and provides other features to help developers update and maintain global modules. I also re-wrote the documentation at https://www.mediawiki.org/wiki/Multilingual_Templates_and_Modules to account for the new tool. It basically describes how to develop a Lua module that can be copied unchanged to any wiki, by abstracting things like user-readable strings and config. Admittedly, this is a "poor man's version" of a proper solution to the problem, but one I find invaluable while developing and maintaining modules. Hopefully some of you may find it useful too!

3 4

Announcing MediaWiki 1.40.0
by Sam Reed 08 Aug '23

08 Aug '23

I am happy to announce the availability of the general release of MediaWiki 1.40! This includes the security fixes announced in 1.35.11/1.38.7/1.39.4. Tarballs have already been uploaded, and the git tag has been pushed. Thanks to everyone who helped out with this release, especially thanks to those who tested out the release candidate and provided feedback, as well as the developers who worked hard to get several important fixes merged in time for the 1.40 final release. To see what's changed in 1.40, see the release notes below. MediaWiki 1.40 is the second release of MediaWiki 'born' with PHP 8.0 and PHP 8.1 support included. We anticipate there may be some as-yet undiscovered bugs with PHP 8.x support, of which we'd love to hear reports so they can be fixed. We plan to back-port fixes to 1.39, 1.38 and 1.35 to the extent possible. MediaWiki 1.40 is due to be supported until the end of June 2024. As a reminder, 1.35 LTS is due to become end-of-life in November 2023, and 1.38 became end-of-life today, 30 June 2023. === Changes since MediaWiki 1.40.0-rc.0 === * Localisation updates. * (T330464) Work around argument corruption bug in XMLReader::open. * build: Updating mediawiki/mediawiki-phan-config to 0.12.1. * Fix frame and frameless rdfa depending on file existing. * (T329214) Pass whether current rev of file exists to Linker::makeBrokenImageLinkObj. * (T334659) Handle thumb errors when !$enableLegacyMediaDOM. * A manualthumb that doesn't exist should be considered a thumb error. * (T313157) IndexPager: Also protect against $offset being 0. * (T335612, CVE-2023-36674) SECURITY: Move badFile lookup to Linker. Open Bugs: [1] https://phabricator.wikimedia.org/project/board/6139/ Bug report form: [2] https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tags=MW-1.40-… ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.40/mediawiki-1.40.0.tar.gz https://releases.wikimedia.org/mediawiki/1.40/mediawiki-1.40.0.zip Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.40/mediawiki-core-1.40.0.tar.gz https://releases.wikimedia.org/mediawiki/1.40/mediawiki-core-1.40.0.zip Patch to previous version (1.40.0-rc.0): https://releases.wikimedia.org/mediawiki/1.40/mediawiki-1.40.0.patch.gz https://releases.wikimedia.org/mediawiki/1.40/mediawiki-1.40.0.patch.zip GPG signatures: https://releases.wikimedia.org/mediawiki/1.40/mediawiki-core-1.40.0.tar.gz.… https://releases.wikimedia.org/mediawiki/1.40/mediawiki-core-1.40.0.zip.sig https://releases.wikimedia.org/mediawiki/1.40/mediawiki-1.40.0.tar.gz.sig https://releases.wikimedia.org/mediawiki/1.40/mediawiki-1.40.0.zip.sig https://releases.wikimedia.org/mediawiki/1.40/mediawiki-1.40.0.patch.gz.sig https://releases.wikimedia.org/mediawiki/1.40/mediawiki-1.40.0.patch.zip.sig Public keys: https://www.mediawiki.org/keys/keys.html

3 2

Save the date: SMWCon 2023 December 11-13 in Paderborn, Germany
by Bernhard Krabina, KM-A 31 Jul '23

31 Jul '23

Dear all, Please save the date: #SMWCon 2023, December 11-13, Paderborn, Germany https://www.semantic-mediawiki.org/wiki/SMWCon_Fall_2023 Tickets will be available beginning of September, but you can already announce your participation on the above page and think about possible contributions (talks, tutorials, workshops, etc.). Hope to see you in Paderborn, Bernhard and Tobias

1 0

2025

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 July 2023