Wikitech-l February 2022

wikitech-l@lists.wikimedia.org

43 participants
38 discussions

Missing Section Headings
by Marc Riddell 12 Sep '24

12 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

Repository ownership of the Lingo extension
by Zoran Dori 10 Jan '23

10 Jan '23

Hi everyone, I want to notify you that I have, on behalf of the WikiTeq company, made a task https://phabricator.wikimedia.org/T298277 for requesting repository ownership for the Lingo extension. In case that you have any kind of questions, please let me know. :) Best regards, Zoran

3 3

Make working with templates easier: Several improvements coming to all wikis soon.
by Johanna Strodt 29 Apr '22

29 Apr '22

Hi everyone, In 2019, the German-speaking wikis selected “Make working with templates easier” as the focus area of Wikimedia Deutschland’s Technical Wishes project. Since then, our team has made improvements in different areas, to help template creators as well as users of the wikitext editor and VisualEditor. Our work on this focus area is coming to an end, so I’d like to summarize what happened and lay out the next steps: Two changes from our Templates project have been available on all* wikis for a while already: - A new attribute “suggested values” was introduced to help you clarify what values a parameter may expect. [1] - Line numbers are shown in the “Template” namespace when syntax highlighting (CodeMirror extension) is turned on. [2] A few wikis have these line numbers in _all_ namespaces. If you want this for your wiki as well, please reach out to us. Several other changes were deployed to a small group in the past months. A big thanks to Catalan, Turkish, Greek, Malay, Twi, French, Hungarian, Hebrew, Finnish, Dagbani and German Wikipedia, to English Wikivoyage and Nauruan Wiktionary as well as Wikitech wiki for testing these changes and giving feedback to help us improve these projects. These changes are now coming to more wikis: - Finding and inserting templates will become easier with an improved search (in the TemplateWizard & in the template dialog of VisualEditor and New Wikitext mode). [3] - In VisualEditor, you’ll be able to remove a template from a page via the context menu, just like removing a table or an image. [4] - In VisualEditor, the template dialog will become bigger and descriptions will be more visible. [5] - When using syntax highlighting (CodeMirror extension)*, matching brackets will be highlighted [6] and the color scheme will be updated for better readability [7]. The planned deployment date for all of these changes is March 9 (and March 16 on English Wikipedia). A few weeks later, we’ll be deploying the last improvements from our Templates project: - For syntax highlighting (CodeMirror extension), a colorblind-friendly color scheme will be added. You’ll be able to activate it via a user setting. - A range of fundamental changes to the VisualEditor template dialog will be deployed. They will make it easier to understand what is expected from a template, to navigate the template dialog, and to add parameters to a template. Feedback on all the projects is much appreciated on their respective talk pages. Thanks a lot on behalf of the Technical Wishes team, Johanna, Community Communications Technical Wishes --- * All improvements in the CodeMirror extension, which provides syntax highlighting, only apply to wikis that have the extension installed. This is generally true for left-to-right language wikis, because unfortunately the extension doesn’t work sufficiently for right-to-left languages yet [1] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Suggested_values_for_… [2] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Line_Numbering [3] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Finding_and_inserting… [4] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Removing_a_template_f… [5] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/VisualEditor_template… [6] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Bracket_Matching [7] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Improved_Color_Scheme…

1 1

Best practices for extensions
by Krinkle 14 Mar '22

14 Mar '22

TLDR: Tech leads please review Best practices for extensions <https://www.mediawiki.org/wiki/Best_practices_for_extensions> on mediawiki.org. Hi all, You may be familiar with the Best practices for extensions <https://www.mediawiki.org/wiki/Best_practices_for_extensions> page on mediawiki.org. It has been marked as a draft since 2017. I'd like to polish this page and get it to a state where it would be uncontroversial to label it as "Development guideline <https://www.mediawiki.org/wiki/Development_guidelines>". This would not make it a hard policy. Neither does it imply that it covers all practices in all situations. Rather, it would mean that the items that are there now are indeed a part of our current best practices. We would keep it alive through bold <https://en.wikipedia.org/wiki/Wikipedia:Be_bold> edits and talk page conversations, similar to our Coding conventions <https://www.mediawiki.org/wiki/Manual:Coding_conventions/PHP> and other such guidelines that we maintain peer to peer and through consensus. The reason I've not simply labelled it as such already is because before today I found the document to be out of sync with our actual practices. I have made a number of changes with descriptive edit summaries to bring it in sync with what I percieve to be our best practices; based on how myself and other maintainers perform code review at large, and how we review new extensions prior to deployment. All are welcome to fix mistakes, raise questions/concerns on the talk page, on this thread. You're also welcome to message me directly anytime if you prefer. If you consider yourself familiar with our practices and/or lead and mentor other engineers, please take a minute to review the page and consider whether the items reflect your current understanding and judgement. -- Timo Tijhof, Principal Engineer, Wikimedia Performance Team.

5 7

Talk to the Search Platform / Query Service Team—March 2nd, 2022
by Trey Jones 02 Mar '22

02 Mar '22

The Search Platform Team <https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds an open meeting on the first Wednesday of each month. Come talk to us about anything related to Wikimedia search, Wikidata Query Service (WDQS), Wikimedia Commons Query Service (WCQS), etc.! Feel free to add your items to the Etherpad Agenda for the next meeting. Details for our next meeting: Date: Wednesday, March 2nd, 2022 Time: 16:00-17:00 GMT / 08:00-09:00 PST / 11:00-12:00 EST / 17:00-18:00 CET & WAT Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours Google Meet link: https://meet.google.com/vgj-bbeb-uyi Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927 Hope to talk to you next week! —Trey Trey Jones Staff Computational Linguist, Search Platform Wikimedia Foundation UTC–5 / EST

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 February 2022