Wikitech-l June 2021

wikitech-l@lists.wikimedia.org

46 participants
40 discussions

Mailman 3 - is there an API available?
by Martin Urbanec 21 Jun '21

21 Jun '21

Hello, does Mailman 3 (as-installed by Wikimedia) have an API I could use? I'm an administrator of WMCZ's internal maillist, and it would help me if I could sync the addresses with evidence of members with a script rather than having to do it manually each time a new member is admitted (or quits). Thanks, Martin

3 3

Code style poll: return typehint spacing
by Gergő Tisza 20 Jun '21

20 Jun '21

There's an ongoing discussion about how PHP return typehints should be formatted in MediaWiki code: function foo(): int { or function foo() : int { If you are interested, please vote here: https://phabricator.wikimedia.org/T220719 (The permission system for votes is somewhat inflexible. If you want to vote but can't, please leave a comment.)

1 0

Need Help for MediaWiki Skin Development
by Nasir Khan 20 Jun '21

20 Jun '21

Hi, I want to develop a skin for MediaWiki and need some help with a number of issues I have faced. I read How to guilde.[1]. There are references to Example skin and Skin Labs skin. I could not install the Skin Labs skin as it is tagged for MediaWiki 1.37+ and then I started to look into the Example Skin. As MediaWiki is moving to the Mustache all the previous skin related docs are marked as outdated. So can you please refer me to the doc pages where I can get the equivalent amount of guidelines of the old doc pages. I have a few queries related to migrating an old style skin to Mustache. If a straight migration is not possible, I am ok to start from scratch as well. I asked a few questions to the Support Desk [2] but did not get any response there. I tried to Discord [3] but only one person replied to me. But that was not the solution I asked for. Earlier I reported some bugs to Phabricator but did not get the answers there as well. So it would be really helpful if please help refer me to some doc, and mention where is the right place to get answers. Thanks Nasir Khan [1] - https://www.mediawiki.org/wiki/Manual:How_to_make_a_MediaWiki_skin [2] - https://www.mediawiki.org/wiki/Project:Support_desk [3] - https://discord.com/channels/178359708581625856/178361730986934273 -- *Nasir Khan Saikat* www.nasirkhn.com

2 2

How to get python 3.6+ at toolforge?
by Shrinivasan T 19 Jun '21

19 Jun '21

Hello all, I have a bot written in python3.8, which uses fstrings a lot. https://realpython.com/python-f-strings/ When deployed the bot on the toolforge, found that it has python3.5 Hence cant run the bot. It cant understand the fstrings. Is there any way we can get python version 3.6 or greater at toolforge servers? Thanks. -- Regards, T.Shrinivasan My Life with GNU/Linux : http://goinggnu.wordpress.com Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com Get Free Tamil Ebooks for Android, iOS, Kindle, Computer : http://FreeTamilEbooks.com

4 5

Need help to login with pwb.py with a bot account
by Shrinivasan T 19 Jun '21

19 Jun '21

Hello all, I am trying to run a pywikibot based bot on toolforge server. i logged into tool forge. Cloned the pywikibot. created the user-config.py and user-password.py with below content. cat user-config.py mylang = 'pa' family = 'wikisource' usernames['wikisource']['pa'] = 'WD-WS Integration Bot' usernames['wikidata']['wikidata'] = 'WD-WS Integration Bot' password_file = "user-password.py" cat user-password.py ('WD-WS Integration Bot', BotPassword('wd-ws-integration-bot', 'PASSWORD HERE')) Created bot account at pa.wikisource.org https://pa.wikisource.org/wiki/User:WD-WS_Integration_Bot Can login to the pa.wikisource.org with the same user name and credentials. But, cant login using the command line using pwb.py. Getting the below error. tools.wdwsbot@tools-sgebastion-07:~/pywikibot-core$ python3 /data/project/shared/pywikibot/stable/pwb.py login WARNING: No user is logged in on site wikisource:pa Logging in to wikisource:pa as WD-WS Integration Bot@wd-ws-integration-bot Traceback (most recent call last): File "/mnt/nfs/labstore-secondary-tools-project/pywikibot/public_html/core_stable/pywikibot/data/api.py", line 2931, in login_to_site response['messagecode'] == 'login-throttled' KeyError: 'messagecode' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/data/project/shared/pywikibot/stable/pwb.py", line 365, in <module> if not main(): File "/data/project/shared/pywikibot/stable/pwb.py", line 360, in main file_package) File "/data/project/shared/pywikibot/stable/pwb.py", line 74, in run_python_file main_mod.__dict__) File "/data/project/shared/pywikibot/stable/scripts/login.py", line 151, in <module> main() File "/data/project/shared/pywikibot/stable/scripts/login.py", line 139, in main site.login(autocreate=autocreate) File "/mnt/nfs/labstore-secondary-tools-project/pywikibot/public_html/core_stable/pywikibot/site/_apisite.py", line 388, in login if login_manager.login(retry=True, autocreate=autocreate): File "/mnt/nfs/labstore-secondary-tools-project/pywikibot/public_html/core_stable/pywikibot/login.py", line 307, in login self.login_to_site() File "/mnt/nfs/labstore-secondary-tools-project/pywikibot/public_html/core_stable/pywikibot/data/api.py", line 2939, in login_to_site 'handled:\n{}'.format(response)) pywikibot.exceptions.CaptchaError: Captcha encountered which cannot be handled: {'result': 'Failed', 'reason': 'Incorrect username or password entered. Please try again.'} CRITICAL: Exiting due to uncaught exception <class 'pywikibot.exceptions.CaptchaError'> Need help to solve this. Thanks. -- Regards, T.Shrinivasan My Life with GNU/Linux : http://goinggnu.wordpress.com Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com Get Free Tamil Ebooks for Android, iOS, Kindle, Computer : http://FreeTamilEbooks.com

3 3

2021 WMF Board of Trustees elections - Call for Candidates
by Krishna Chaitanya Velaga 14 Jun '21

14 Jun '21

Hello all, The 2021 Board of Trustees election[1] is coming soon. Candidates from the community are needed to fill the available seats. The Wikimedia Foundation Board of Trustees oversees the Wikimedia Foundation's operations. Community trustees and appointed trustees make up the Board of Trustees. Each trustee serves a three-year term. The Wikimedia community has the opportunity to vote for community trustees. Wikimedia contributors will vote to fill four seats on the Board in 2021. This is an opportunity to improve the Board's representation, diversity, and expertise as a team. For potential candidates: - *Traits:* Wikimedia is a global movement and seeks candidates from the broader community. Candidates should think about what experiences and perspectives they will bring to the Board. Ideal candidates align with the Wikimedia mission and are thoughtful, respectful, and community-oriented. The Board would like to find perspectives and voices that are under-represented and essential for our movement. They should bring what Wikimedia needs from a new Trustee. - *Commitment: *Trustees serve a three-year term and can serve up to three consecutive terms. The time commitment is about 150 hours per year, excluding travel. This time is not evenly spread throughout the year. The time is concentrated around meetings. The expectation is that Trustees serve on at least one of the Board’s committees. - *Requirements*[2]: English is the language of business for the Board. Candidates need a basic understanding of English, but support and training are part of onboarding. Candidate applications will be translated into several languages to reach a broad audience of voters. - *Apply*[3]: Candidates from all projects and communities who meet the needs of Wikimedia Trustee are welcome. If you know someone who could be a good trustee, encourage them to run for election. Candidates can find information and submit their nomination on the Apply to be a Candidate page. - *Resources*[4]: A toolkit has been developed for community members who are considering submitting their candidacy for the Wikimedia Foundation Board of Trustees, and who want to better understand what to expect and how to prepare for the role. Thank you for your support, The Wikimedia Foundation Board of Trustees [1] https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_ele… [2] https://meta.wikimedia.org/wiki/Special:MyLanguage/Wikimedia_Foundation_ele… [3] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2021/Apply_t… [4] https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/Candidate_Re… -- Krishna Chaitanya Velaga (he/him) Board Governance Facilitator, Wikimedia Foundation

1 0

the parts of a template
by Amir E. Aharoni 14 Jun '21

14 Jun '21

Hallo. What are the parts of a template? When templates started in 2003 or 04, they were just simple pages, whose content you could add ("transclude") to multiple other pages. Over time they acquired more features: noinclude, includeonly, onlyinclude, parser functions, documentation pages, TemplateData, Scribunto, TemplateStyles, and more. If we now take a look at the parts from which a template is built, what will we identify? I'm not talking just about the technical parts, i.e. how the parser sees it, but also about the functional parts—how the template maintainers and users perceive it. Here's what I can think of: * The body: The content that is actually inserted into other pages. This can be further divided into text, formatting, images, and logic using parser functions and invoked modules, but for the sake of parsing it's probably one blob of wikitext, but do correct me if I'm wrong. Sometimes, but not always, appears in <includeonly> or <onlyinclude>. * The documentation: As a separate page (Template:Name/doc), as some content in <noinclude>, or a mix of both. * The categories: Self-explanatory. Usually in <noinclude>. * TemplateData: Usually in a <templatedata> tag on the template page itself, or on the /doc page. * TemplateStyles: On a separate page with a different content model, and linked using <templatestyles> tag. One TemplateStyles page can serve several other pages, so it's autonomous and modular. * Testing pages: A few complex templates also have testing or sandbox pages. I'm familiar with some examples, such as https://en.wikipedia.org/wiki/Template:Infobox_philosopher/sandbox , but I'm not an expert on how consistent it is. It's probably not right to call it a "part" of a template _technically_, but it's closely related to it, so it can be considered a _functional_ part. A couple of comments: 1. I mostly deal with Wikimedia use cases. Comments from other wikis are welcome, too—SMW wikis, your enterprise wiki, Fandom, other farms, etc. 2. I intentionally don't include in this list other templates and Scribunto modules that a template transcludes or invokes. It's very common, but these are autonomous. (I do include TemplateStyles, which can also serve several pages, and maybe I should exclude them, too). So, two questions: 1.Does it make sense generally? 2. Am I missing anything? Thanks :) -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬

2 1

📊 2021 Developer satisfaction survey results
by Tyler Cipriani 14 Jun '21

14 Jun '21

👋 Results: https://www.mediawiki.org/wiki/Developer_Satisfaction_Survey/2021 Thanks to everyone who took the time to respond to the survey! 🥰 The developer satisfaction survey results show what's important to our developer community, and the parts of our developer experience that need more resources to improve. ➡️ Folks should read it, talk about it, and ask questions (please ;))! <3 - Tyler Cipriani (he/him) Engineering Manager, Release Engineering Wikimedia Foundation [0]: <https://lists.wikimedia.org/pipermail/wikitech-l/2021-March/094317.html> [1]: <https://www.mediawiki.org/wiki/User:Greg_(WMF)> [2]: <https://lists.wikimedia.org/pipermail/wikitech-l/2021-March/094373.html>

1 0

Removal of the Revision class
by DannyS712 Wiki 11 Jun '21

11 Jun '21

Hi everyone. My patch[1] to remove the legacy `Revision` class from core was just merged, and this may have broken some extensions. Extensions deployed on WMF wikis had already been updated, but others may no longer work on MediaWiki 1.37. All code using Revision objects had been emitting deprecation warnings since at least 1.35. I've also created a basic guide[2] to help migrate extensions that were not updated. This includes how to migrate code relying on hooks that passed Revision objects - all such hooks have been removed. You can check out the phabricator task[3] for more info on what specifically was removed. Special thanks to the Platform Engineering team, and specifically Petr Pchelko, for helping out and reviewing a whole bunch of patches. Thanks, -DannyS712 [1] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/684071 [2] https://www.mediawiki.org/wiki/Manual:Revision.php/Migration [3] https://phabricator.wikimedia.org/T247143

1 0

Summary of this week's deployment of 1.37.0-wmf.9: All good, no train next week.
by Brennen Bearnes 10 Jun '21

10 Jun '21

This is a summary of this week's deployment of the 1.37.0-wmf.9 branch of MediaWiki and its extensions (also known as "the train"). The primary person in charge this week is Jeena Huneidi, with Mukunda Modell as backup, both from the Wikimedia Foundation Release Engineering team. The summary/blocker task for this week is https://phabricator.wikimedia.org/T281150 The new version is running on all sites: https://versions.toolforge.org/ Please note that the next train will be 1.37.0-wmf.11, since the week of June 14th is taken up by the WMF's annual All Hands. == Blockers == There were a total of four blockers for this train: * Regression: Echo new talk page message banner has lost its orange background ** https://phabricator.wikimedia.org/T284496 * regression: Reply tool padding and height broken ** https://phabricator.wikimedia.org/T284567 * TypeError: Argument 1 passed to LanguageConverter::__construct() must be an instance of Language, instance of StubUserLang given, called in /srv/mediawiki/php-1.37.0-wmf.9/includes/language/LanguageConverterFactory.php on line 132 ** https://phabricator.wikimedia.org/T284685 * Code editor failing to load completely on English Wiktionary ** https://phabricator.wikimedia.org/T284716 == Deprecation notices == Release Engineering has recently adopted the practice of filing deprecation notices in production as blockers for the following train. For 1.37.0-wmf.11, we've filed: * PHP Deprecated: Passing extra fields (quality) to LocalFile::loadFromRow was deprecated in MediaWiki 1.37. Property assignment will be removed in a later version. [Called from OldLocalFile::loadFromRow] ** https://phabricator.wikimedia.org/T284777 == 🚂💗 == As usual, lots of people helped find, triage, and solve problems with this train. Thanks to all involved (listed by Phabricator username): * DannyS712 * matmarex * Zabe * Ladsgroup * ovasileva * Jdlrobson * Edtadros * Esanders * ppelberg * Erutuon * Xiplus * Urbanecm ...and anyone else we've missed. Without your help we wouldn't be able to deploy the train. Thanks! -- Your train conductor collective

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