Wikitech-l February 2021

wikitech-l@lists.wikimedia.org

42 participants
51 discussions

Re: [Wikitech-l] [Wikidata] [Wikimedia-l] Idea of a new project: Wikifacts ?
by Adam Sobieski 13 Feb '21

13 Feb '21

Thad, Thank you for the information about schema.org with respect to ClaimReview<https://schema.org/ClaimReview>. A point of disagreement with that schema.org model is the ratings system concept (x out of N). Instead, for discussion, I prefer a more annotational approach for fact checking with typed annotations produced and consumed by both humans and software tools. That is, I prefer the concept of an informational message, warning, error system for fact checking resembling software IDE’s. Such a model is intuitive, can be readily formalized, made machine-utilizable, and typed annotations – informational messages, warnings, and errors – can be merged from multiple sources or service providers. Best regards, Adam P.S.: As interesting, a new W3C Community Group is launching on the topic of document services. The group intends to discuss and make new architecture and API to facilitate: spellchecking, grammar checking, proofreading, fact checking, mathematical proof checking, reasoning checking, argumentation checking, and narrative checking. If the group interests you, please do feel free to support the creation of the group: https://www.w3.org/community/groups/proposed/#services . From: Thad Guidry<mailto:thadguidry@gmail.com> Sent: Friday, February 5, 2021 3:12 PM To: Discussion list for the Wikidata project<mailto:wikidata@lists.wikimedia.org> Cc: wikitech-l(a)lists.wikimedia.org<mailto:wikitech-l@lists.wikimedia.org>; Wikispore experimental project<mailto:wikispore@lists.wikimedia.org> Subject: Re: [Wikidata] [Wikimedia-l] Idea of a new project: Wikifacts ? Oops, the better link for the Schema.org work to support fact checking (some even still in progress after 3 years) probably should have been this: http://blog.schema.org/2017/08/schemaorg-33-news-fact-checking.html Thad https://www.linkedin.com/in/thadguidry/ https://calendly.com/thadguidry/

6 7

🌱 Fresh 21.01.1 released!
by Krinkle 13 Feb '21

13 Feb '21

We have published a new release of Fresh. This one improves support for ".env" files with MediaWiki-Docker (thanks Željko Filipin), and adds support Podman, a rootless Docker alternative (thanks Kunal Mehta). Get started by installing or updating, and learn more, at: https://gerrit.wikimedia.org/g/fresh#fresh-environment Changelog: https://gerrit.wikimedia.org/g/fresh/+/21.01.1/CHANGELOG.md <https://gerrit.wikimedia.org/g/fresh/+/20.08.1/CHANGELOG.md> Fresh is a fast way to launch isolated environments from your terminal. These can be used to more securely work with 'npm' developer tools such as for ESLint, QUnit, Grunt, and Selenium. Example guides: * https://www.mediawiki.org/wiki/Manual:JavaScript_unit_testing * https://www.mediawiki.org/wiki/Selenium/How-to/Run_tests_targeting_MediaWik… * https://www.mediawiki.org/wiki/Selenium/How-to/Run_tests_targeting_MediaWik… -- Timo

1 0

Starting the Wikimedia Rust developers user group
by Kunal Mehta 12 Feb '21

12 Feb '21

Hi everyone, We are starting a user group for people interested in spreading the adoption of the Rust programming language[1] in the Wikimedia movement. If you're not familiar with it, Rust is a systems programming language that aims to provide the trifecta of safety, concurrency and speed. It's very fun to use (rated #1 favorite language in Stack Overflow's survey 5 years and counting) and has fantastic tooling. https://meta.wikimedia.org/wiki/Wikimedia_Rust_developers_user_group If you're already using Rust or looking to get started - please sign up! The current proposed goals of the user group are: * Develop a rich toolkit of Rust libraries and applications for working with Wikimedia and MediaWiki projects and APIs * Make Rust a first-class language in Wikimedia infrastructure like Toolforge * Encourage the usage of Rust where appropriate to build safer and better tools * Assist others who end up encountering Rust and need help (e.g. when upstreams adopt Rust) * Mentor new developers who are interested in contributing technically to the Wikimedia movement, including through programs like GSoC and Outreachy Have other ideas of what we could do? Please suggest them on the talk page! [1] https://www.wikidata.org/wiki/Q575650 [2] https://meta.wikimedia.org/wiki/Talk:Wikimedia_Rust_developers_user_group -- Legoktm

2 1

[Train] 1.36.0-wmf.30 is in danger
by Tyler Cipriani 12 Feb '21

12 Feb '21

Hiya all tl;dr: help us fix (or convince us not to care about): * No atomic section is open (got LocalFile::lockingTransaction)[0] Longer: We've been on 1.36.0-wmf.27 for two weeks which is 1,038 changes behind 1.36.0-wmf.30 (the latest branch). The remaining issue is: "No atomic section is open (got LocalFile::lockingTransaction)"[0] We're not sure about the impact of this log message. Holding the train is our most effective tool to ensure that the log messages that we see don't hurt users. We need to solve this by Monday or we will remain on wmf.27 for another week. Any help you can provide is sincerely appreciated. Any feedback on how to communicate about log messages more clearly so they get the attention they need in a timely manner is also appreciated! <3 -- Tyler 0: <https://phabricator.wikimedia.org/T274589>

1 0

Upgrade of CI jobs to Quibble 0.0.46
by Antoine Musso 12 Feb '21

12 Feb '21

Hello, On Monday 02/15 I will start upgrading Quibble on the CI jobs to version 0.0.46. The notable changes for CI are: * Run phpunit-unit stage before MediaWiki installation. T266441 Kosta Harlan * Fix regression which made us run linters for repositories besides MediaWiki extensions or skins (eg: mediawiki/services/parsoid). T263500 Antoine Musso * Mute zuul.CloneMapper logging when running browser tests. Antoine Musso It opens the way to use Apache instead of the php built-in webserver. That would make the Selenium tests slightly faster, but we have to add Apache to the images, that will be done later. The full changelog is: https://doc.wikimedia.org/quibble/changelog.html The task tracking the upgrade is: https://phabricator.wikimedia.org/T274590 cheers, -- Antoine Musso

1 0

Invitation to apply to Outreachy and Google Summer of Code program with Wikimedia!
by Gopa Vasanth 11 Feb '21

11 Feb '21

(feel free to forward the message as is to your friends, family members & colleagues) Hello folks, We would like to invite you to apply to the Outreachy and Google Summer of Code program with the Wikimedia Foundation (a non-profit organization behind Wikipedia)! About the Outreachy program Wikimedia will be mentoring ~3 projects in the Outreachy program in the May to August 2021 round. The initial applications are due February 22nd at 4 pm UTC. Apply today: https://www.outreachy.org/apply/ [1] Outreachy offers three-month internships to work remotely in Free and Open Source Software (FOSS) projects with experienced mentors. The internships may include programming, user experience, documentation, illustration, and graphic design, or data science. Outreachy internships run twice a year – from May to August and December to March. Interns are paid a stipend of $5,500 USD for the three months of work. They also have a $500 USD stipend to travel to conferences and events. Interns often find employment after their internship with Outreachy sponsors or in jobs that use the skills they learned during their internship. Outreachy is open to both students and non-students. Outreachy expressly invites the following people to apply: - Women (both cis and trans), trans men, and genderqueer people. - Anyone who faces under-representation, systematic bias, or discrimination in the technology industry in their country of residence is invited to apply. - Residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin@, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander. About the Google Summer of Code program Wikimedia is planning to mentor 8-10 projects in 2021’s Google Summer of Code (GSoC) program. Beginning March 9th, pending Wikimedia’s acceptance as a mentoring organization, applicants can begin discussing ideas with the mentors! The student application will be due on April 13, 2021: https://summerofcode.withgoogle.com/ [2] Google Summer of Code, now in its 17th year, is Google's summer program for candidates participating in any academic programs who want to get involved in open-source software. Over 6,626 students from 121 countries have already participated in the last year’s round i.e 2020 < https://opensource.googleblog.com/2020/06/google-summer-of-code-2020-statis…> [3]. Google Summer of Code is a unique program that pairs students with mentors who introduce them to the open-source community and provide guidance while they work on real-world open-source projects during their summer break from university. This year there are some new breaking changes in the GSoC program, including: - Smaller project size ~175 hr project (previously 350 hr) - Shortened coding period ~10 weeks long (previously 3 months) - Eligibility criteria redefined; the program is now open to candidates participating in a variety of academic programs (previously accredited university programs only) Projects cover a wide range of fields including Cloud, Operating Systems, Graphics, Medicine, Programming Languages, Robotics, Science, Security and many more. It's a highly competitive program (and this year is expected to be even bigger than last year), so don't wait until the last minute to prepare! About the Wikimedia Foundation The Wikimedia Foundation is the nonprofit organization that hosts and operates Wikipedia and the other Wikimedia free knowledge projects. Our vision is a world in which every single human can freely share in the sum of all knowledge. We believe that everyone has the potential to contribute something to our shared knowledge and that everyone should be able to access that knowledge, free of interference. We host the Wikimedia projects, build software experiences for reading, contributing, and sharing Wikimedia content, support the volunteer communities and partners who make Wikimedia possible, and advocate for policies that enable Wikimedia and free knowledge to thrive. Resources * Browse through the participants’ guides, to learn more about the application process steps: <https://www.mediawiki.org/wiki/Outreachy/Participants> [4] <https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants> [5] * All the projects will be showcased here: <https://www.outreachy.org/communities/cfp/wikimedia/> [6] <https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021> [7] We hope you will help us spread the word about Wikimedia’s participation in these programs (by sharing this email) Looking forward to your participation! Cheers, Gopa, Srishti, Pavithra, Ankit & Mahveotm (Wikimedia organization administrators for GSoC & Outreachy) [1] https://www.outreachy.org/apply/ [2] https://summerofcode.withgoogle.com/ [3] https://opensource.googleblog.com/2020/06/google-summer-of-code-2020-statis… [4] https://www.mediawiki.org/wiki/Outreachy/Participants [5] https://www.mediawiki.org/wiki/Google_Summer_of_Code/Participants [6] https://www.outreachy.org/communities/cfp/wikimedia/ [7] https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021 -- Regards Gopa Vasanth <https://www.mediawiki.org/wiki/User:Gopavasanth> Amrita Vishwa Vidyapeetham <http://www.amrita.edu/> | Blog <https://gopavasanth.wordpress.com/> amFOSS <https://amfoss.in/@gopavasanth> | GitHub <https://github.com/gopavasanth> | Gerrit <https://gerrit.wikimedia.org/r/#/q/gopavasanth> “Yesterday is not ours to recover, but tomorrow is ours to win or lose.”

1 0

2021-02-10 scrum of scrums meeting notes
by Grace Gellerman 11 Feb '21

11 Feb '21

https://www.mediawiki.org/wiki/Scrum_of_scrums/2021-02-10 = 2021-02-10 = == Callouts == * RelEng: Trying to be a bit more strict about log messages, see Greg's email: https://lists.wikimedia.org/pipermail/wikitech-l/2021-February/094250.html * RelEng: Blocked on serviceops: [https://phabricator.wikimedia.org/T274306 docker-pkg: "certificate verify failed: unable to get local issuer certificate" for docker-registry.discovery.wmnet when publishing dev-images from contint2001] === No updates === Community Tech, Anti-Harassment, Parsing, Language, Library === '''No notes provided''' === Editing, Growth, iOS, Android, Product Infrastructure, Inuka, Analytics, Cloud Services, Platform, Quality & Test == SoS Meeting Bookkeeping == * Updates: ** from retro ideas to try: *** Bolding items to read allowed +JF +TC *** relaxing the start time *** Template **** Adding a section where teams can add Gerrit patches or GitHub Pull Requests to request reviews or feedback. +GG +TC **** Perhaps add a contact point (email, url, office hours, whatever) for easy reaching out to teams when a bullet point seems interesting. +GG +JF +TC **** Adding a "thanks" section +GG +JF +TC+AP == Product == === Web === * Blocked by: * Blocking: * Updates: ** Security review of WVUI component library is back with Security for discussion ** Logging Vue.js component errors to the error intake system (again): https://phabricator.wikimedia.org/T249826 ** Language button treatment and associated A/B test: *** https://phabricator.wikimedia.org/T260738 *** https://phabricator.wikimedia.org/T268241 *** https://phabricator.wikimedia.org/T268504 === Structured Data === * Blocked by: * Blocking: * Updates: ** MediaSearch: working on supporting complex queries, instrumenting events, improving the CSS-only grid ** Image recommendations: using machine learning to improve mediasearch ( https://phabricator.wikimedia.org/T271803), translating data analysis from Research team into an elastic search profile and query builder ( https://phabricator.wikimedia.org/T271799) ** Continuing SDAW architecture discussions === Abstract Wikipedia === * Blocked by: ** None * Blocking: ** None * Updates: ** Working on phase gamma of development plan: https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Phases *** Creation of Functions coming soon; will need a code editor Vue UX component. *** First route for back-end executor service is landing soon. *** Also making WikiLambda changes as recommended by Platform; thanks again. ** Special thanks to Dave Pifke from Performance for their support and advice this & last week. ** Community suggestions for the logo concept for Wikifunctions continues: https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Wikifunctions_logo_conce… === Vue.js === * Blocked by: * Blocking: * Updates: ** Nearly done with updates to MediaWiki's JS minifier == Technology == === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** Fixing truncated order IDs https://phabricator.wikimedia.org/T274301 ** Fixing another error handling case for nightly recurring charge job https://phabricator.wikimedia.org/T274361 ** Prepping for CIviCRM db encoding update https://phabricator.wikimedia.org/T273704 ** More refinements to docker images for fundraising development https://phabricator.wikimedia.org/T262975 https://phabricator.wikimedia.org/T273894 === Engineering Productivity === ==== Performance ==== * Blocked by: * Blocking: * Updates: ** FOSDEM hasn't published our devroom videos yet, but here they are: https://drive.google.com/drive/folders/1OIp-3XUdtgWykK7sOxw8-k3icv8BWDcY?us… ==== Release Engineering ==== * Blocked by: ** Serviceops: [https://phabricator.wikimedia.org/T274306 docker-pkg: "certificate verify failed: unable to get local issuer certificate" for docker-registry.discovery.wmnet when publishing dev-images from contint2001] *** Have checked the obvious stuff, but not really sure how to proceed. * Blocking: * Updates: ** Jessie-based node 6 / npm 3 CI jobs have been dropped (original deadline was April 2019). Specifically, this means that 3d2png and Maps no longer have CI; any relevant teams may wish to fix. ** Train: *** Last week: 1.36.0-wmf.29 [[phab:T271342]] was abandoned.  *** This week: 1.36.0-wmf.30 [[phab:T271343]] underway.  *** Next week: 1.36.0-wmf.31 [[phab:T271344]]  === Search Platform === * Blocked by: ** No one * Updates: ** Blazegraph journal for wcqs is too big - https://phabricator.wikimedia.org/T273636 ** Deleted item still gets shown in WDQS query results - https://phabricator.wikimedia.org/T272120 ** Programmatically categorize WDQS queries by potential alternative solution -https://phabricator.wikimedia.org/T266022 ** wikimedia-event-utilities should provide tools for JVM based apps producing directly to kafka -https://phabricator.wikimedia.org/T270371 ** Reboot wdqs hosts for kernel upgrade - https://phabricator.wikimedia.org/T274213 === Security === * Blocked by: ** none * Blocking: * Updates: ** Updated SOP for Security Reviews: https://www.mediawiki.org/wiki/Security/SOP/Security_Readiness_Reviews ** Current queue and reviews in progress: https://phabricator.wikimedia.org/tag/secscrum/ === Site Reliability Engineering === * Blocked by: ** None * Blocking: ** None * Updates: ** Working with PI to get linkrecommendation updated in a structured fashion ** maps architectural discussions ongoing == Cross-cutting == * Blocked by: ** None * Blocking: ** None * Updates: ** It's quiet. ** No major progress on PHP 8.0 work. ** CI tools' upgrade status is mostly stable: https://libraryupgrader2.wmcloud.org/status?branch=master [[Category:Scrum of scrums{{#translation:}}|*]]

1 0

Where are the logs?
by Arthur Smith 11 Feb '21

11 Feb '21

I've been using mediawiki in the docker containers for a while, and I just did a git pull to the latest, replaced the containers I was running etc, and now I can't figure out where errors are being logged to or how I'm supposed to see them. Help! This may be related to the new '.env' file that seems to be required, which sets a MW_DOCKER_UID and MW_DOCKER_GID value... If I run docker-compose logs I do see some "Permission denied" errors for files in /etc/php/7.2/cli and /etc/php/7.2/fpm but those don't seem to be log files exactly (20-xdebug.ini files ?) If I do docker-compose exec mediawiki bash I get a login shell on the container and I can look around, but there are no mediawiki log files in /var/log where I would expect them, and again I don't have permission to create a file there. Also if I docker exec into the web container I don't have permission to look at the apache logs (but those do exist). If I try to add a $wgDebugLogFile to LocalSettings.php the mediawiki instance completely collapses, I can't look at anything, and I see no errors explaining what's going on! Help! Arthur

3 4

Want to Contribute
by Puneet Dwivedi 10 Feb '21

10 Feb '21

2 1

Re: [Wikitech-l] [Wikimedia-l] [REMINDER] Call for projects and mentors for Google Summer of Code 2021 and Outreachy Round 22 is ongoing!
by Srishti Sethi 10 Feb '21

10 Feb '21

Hi all, We are still looking for more projects for GSoC/ Outreachy. We are currently working on putting together a list of projects to submit along with our mentoring organization application to Google for GSoC next week. If you are interested in mentoring and have a project idea in mind, drop a note here <https://phabricator.wikimedia.org/T270429> [1]. Best, Srishti [1] https://phabricator.wikimedia.org/T270429 *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/> On Tue, Jan 26, 2021 at 10:54 PM Pavithra Eswaramoorthy < pavithra.e(a)hotmail.com> wrote: > Hello everyone, > > TLDR; Wikimedia will soon be applying as a mentoring organization to > Google Summer of Code 2021 <https://summerofcode.withgoogle.com> [1] and > Outreachy Round 22 <https://www.outreachy.org/> [2]. The application > submission deadline for GSoC is February 20th, and Outreachy is March 7th. > We are currently working on a list of interesting project ideas to include > in the application. If you have some ideas for coding or non-coding > (design, documentation, translation, outreach, research) projects, share > them here: https://phabricator.wikimedia.org/T270429 [3]. > > > Timeline > > As a mentor, you will be engaging potential candidates in the application > period for GSoC between March 10th – April 13th, and for Outreachy between > March 15th – April 16th. During this time, you will help candidates make > small contributions to your project and answer any project related queries. > You will be working more closely with the accepted candidates during the > coding period between May-August. > > > Project ideas > > We have started compiling a list of projects that you can take a look at > here: > https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021 [4], > https://www.mediawiki.org/wiki/Outreachy/Round_22 [5] > > If you don’t have an idea in mind and would like to pick one from an > existing list, check out these projects: > https://phabricator.wikimedia.org/tag/outreach-programs-projects/ [6] > > Through GSoC, you can mentor only coding but with Outreachy also > non-coding projects (including design, documentation, translation, > outreach, etc.). > > Note that GSoC has some changes this year, including: > > - Smaller project size ~175 hr project (previously 350 hr) > - Shortened coding period ~10 weeks long (previously 3 months) > - Eligibility criteria redefined; the program is now open to > candidates participating in a variety of academic programs (previously > accredited university programs only) > > Please keep these changes in mind while sharing your project ideas. > > > Some tips for proposing projects > > - Follow this task description template when you propose a project in > Phabricator: > https://phabricator.wikimedia.org/tag/outreach-programs-projects [7]. > Add #Google- Summer-of-Code (2021) or #Outreachy (Round 22) tag to it. > - Remember, the project should require an experienced developer ~15 > days to complete and a newcomer ~3 months for Outreachy and ~10 weeks for > GSoC. > - Each project should have at least 2 mentors, and one of them should > hold a technical background. > - When it comes to picking a project, you could propose one that is: > - Relevant for your language community or brings impact to the > Wikimedia ecosystem in the future. > - Welcoming and newcomer-friendly and has a moderate learning curve. > - A new idea you are passionate about, there are no deadlines > attached to it; you always wanted to see it happen but couldn't due to lack > of resources! > - About developing a standalone tool (possibly hosted on Wikimedia > Toolforge), with fewer dependencies on Wikimedia's core infrastructure, and > doesn't necessarily require a specific programming language, etc. > > To learn more about the roles and responsibilities of a mentor, visit our > resources on MediaWiki.org: > https://www.mediawiki.org/wiki/Outreachy/Mentors [8], > https://www.mediawiki.org/wiki/Google_Summer_of_Code/Mentors [9]. > > Cheers, > GSoC 2021 and Outreachy Round 22 Administrators > > [1] https://summerofcode.withgoogle.com > [2] https://www.outreachy.org/ > [3] https://phabricator.wikimedia.org/T270429 > [4] https://www.mediawiki.org/wiki/Google_Summer_of_Code/2021 > [5] https://www.mediawiki.org/wiki/Outreachy/Round_22 > [6] https://phabricator.wikimedia.org/tag/outreach-programs-projects/ > [7] https://phabricator.wikimedia.org/tag/outreach-programs-projects/ > [8] https://www.mediawiki.org/wiki/Outreachy/Mentors > [9] https://www.mediawiki.org/wiki/Outreachy/Mentors > > _______________________________________________ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > https://meta.wikimedia.org/wiki/Wikimedia-l > New messages to: Wikimedia-l(a)lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> >

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