Wikitech-l August 2024

30 participants
28 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

Drop dedicated support for IE 11, Edge Legacy and Opera
by Volker E. 06 Sep '24

06 Sep '24

Hi everyone, the Design System Team (DST) is proposing the following changes to MediaWiki browser support [1]: - Drop support for Internet Explorer 11 (IE 11) - Drop support for all versions of Edge Legacy - Drop support for Opera - Increase Basic (Grade C) support for Chrome and Firefox to versions 49+, Safari and iOS to versions 10+. What this means: The browsers we’re phasing out won’t be tested for layout rendering anymore. While users on these browsers might and will still be able to read and basically interact with content, they might experience some quirks. This step helps us integrate modern web features more seamlessly. These changes will unlock the ability to use specific newer browser features that cannot be safely used today without requiring a fallback, notably CSS custom properties (used in upcoming reading customization features like Night Mode) and the <summary> and <details> HTML elements that can be used to replace the checkbox hack. This will reduce the amount of code sent to 99.9% of users and cut down on software development costs and maintenance burdens. See the full announcement for more details; PDF to download [2]. On behalf of the Wikimedia Foundation Design System Team, Volker [1] https://www.mediawiki.org/wiki/Compatibility#Browser_support_matrix [2] https://phabricator.wikimedia.org/F52025988

11 14

Call for Projects and Mentors for Outreachy Round 29 is open!
by Deb Tankersley 05 Sep '24

05 Sep '24

Hello, I'm happy to announce that Wikimedia is participating in Round 29 of the Outreachy program https://www.outreachy.org/ [1] that runs from December 2024 through March 2025! The deadline to submit projects on the Outreachy website is September 11, 2024 at 4pm UTC and the project list will be finalized by September 18, 2024. We are currently gathering a list of interesting project ideas. If you have some ideas for coding or non-coding (design, documentation, translation, outreach, research) projects, please share them on this task: https://phabricator.wikimedia.org/T372834 [2]. *About the Outreachy Program* Outreachy is a paid, remote three-month internship program. Outreachy's goal is to support people from groups underrepresented in tech. We help newcomers to free software and open source make their first contributions in Free and Open Source Software (FOSS), coding, and non-coding projects with experienced mentors. These internships run twice a year–from May to August and December to March. Interns are paid a stipend of USD 7000 for the three months of work. Outreachy internship projects may include programming, user experience, documentation, illustration, graphical design, or data science. 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 applicants around the world and the program is open to both students and non-students; complete eligibility rules <https://www.outreachy.org/docs/applicant/> [3]. Outreachy expressly invites the following people to apply: - Women (both cis and trans), trans men, non-binary people, and genderqueer people. - Anyone who faces under-representation, systematic bias, or discrimination in the technology industry in their country of residence. - Residents and nationals of the United States of America of any gender who are Black/African American, Hispanic/Latin@, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander. *Tips for mentors for proposing projects* As a mentor, you will engage with potential candidates in the application period during October and help them make small contributions to your project. You will work more closely with the accepted candidates during the internship period from December through March. Each mentor will need to submit an intern project proposal: https://www.outreachy.org/communities/cfp/wikimedia/ [4]. The project proposal will then be reviewed and approved by the FOSS community coordinators. Additional co-mentors for the intern project will be able to sign up for the project after it has been approved by the community coordinator. *Guidelines for Crafting Project Proposals* - Follow this task description template when you propose a project in Phabricator: https://phabricator.wikimedia.org/tag/outreach-programs-projects [5]. - Add *Outreachy (Round 29)* tag - Project should require an experienced developer ~15 days and a newcomer ~3 months to complete. - Each project should have at least two mentors, with one of them holding a technical background. - Ideally, the project has no tight deadlines, a moderate learning curve, and fewer dependencies on Wikimedia's core infrastructure. Projects addressing the needs of a language community are most welcome. - 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] - To learn more about the roles and responsibilities of mentors, visit our resources on MediaWiki.org: - https://www.mediawiki.org/wiki/Outreachy/Mentors [7] We look forward to your participation! Cheers, Deb [1] https://www.outreachy.org/ [2] https://phabricator.wikimedia.org/T372834 [3] https://www.outreachy.org/docs/applicant/ [4] https://www.outreachy.org/communities/cfp/wikimedia/ [5] https://phabricator.wikimedia.org/tag/outreach-programs-projects [6] https://phabricator.wikimedia.org/tag/outreach-programs-projects [7] https://www.mediawiki.org/wiki/Outreachy/Mentors -- deb tankersley (she/her) senior technical program manager Wikimedia Foundation

1 1

Parsoid Read Views roll out on English and Hebrew Wikivoyage this week
by C. Scott Ananian 04 Sep '24

04 Sep '24

Hello everyone, I am glad to inform you that as part of our continued rollout of Parsoid Read Views, Parsoid is expected to be turned on this week as the default read views renderer on English and Hebrew Wikivoyage. Here's the rationale <https://www.mediawiki.org/wiki/Parsoid/Parser_Unification/Confidence_Framew…> behind our confidence to roll-out this experimental feature and collect feedback. This is an opportunity for continued experimentation as we increase the number of wikis using Parsoid for read views. If this disrupts your workflow, don’t worry you can still opt out through a user preference or turn Parsoid off on the page you’re navigating in the Tools submenu, as described at the Extension:ParserMigration <https://www.mediawiki.org/wiki/Help:Extension:ParserMigration> page. To report bugs and issues, please look at our known issues <https://www.mediawiki.org/wiki/Special:MyLanguage/Parsoid/Parser_Unificatio…> documentation and if you found a new bug please create a phab ticket and tag the Content Transform Team in Phabricator <https://phabricator.wikimedia.org/project/view/5846>. There is more information about our roll-out strategy <https://www.mediawiki.org/wiki/Parsoid/Parser_Unification/Confidence_Framew…> available. Best regards, C. Scott Ananian <https://www.mediawiki.org/wiki/User:CAnanian_(WMF)>, for the Content Transform Team

1 3

Language and Internationalization Newsletter, Community Meeting, and Support Track at Wikimania
by Srishti Sethi 30 Aug '24

30 Aug '24

Hello everyone, Hope this message finds you well. I wanted to share some updates regarding the Language & Internationalization newsletter, the upcoming community meeting, and the Language Support track at Wikimania. *Language and Internationalization Newsletter* The fourth edition of the Language & Internationalization newsletter (August 2024) is available at this link: < https://www.mediawiki.org/wiki/Wikimedia_Language_and_Product_Localization/… >. This newsletter provides updates from the April–June 2024 quarter on new feature development, improvements in various language-related technical projects and support efforts, details about community meetings, and contribution ideas for getting involved in projects. To stay updated, you can subscribe to the newsletter on its wiki page: < https://www.mediawiki.org/wiki/Wikimedia_Language_and_Product_Localization/… >. *Language Community Meeting* The next language community meeting is scheduled in a few weeks—on August 30th at 15:00 UTC. If you're interested in joining, you can sign up on this wiki page: < https://www.mediawiki.org/wiki/Wikimedia_Language_and_Product_Localization/… >. This participant-driven meeting will focus on sharing language-specific updates related to various projects, discussing technical issues related to language wikis, and working together to find possible solutions. For example, in the last meeting, topics included the Language Converter, the state of language research, updates on the Incubator conversations, and technical challenges around external links not working with special characters on Bengali sites. Do you have any ideas for topics to share technical updates or discuss challenges? Please add agenda items to the document here: < https://etherpad.wikimedia.org/p/language-community-meeting-aug-2024>. *Language Support Track at Wikimania* Attending the Wikimania Hackathon in person next week? There will be a dedicated Language Support track focusing on addressing small, language-specific technical requests across various Wikimedia projects to support new and existing language communities. Join us to collaborate with interested volunteers on technical tasks, organize technical sessions, and run a support help desk. There will also be a session for remote attendees on using Translatewiki.net for translating Wikimedia interface messages! < https://wikimania.wikimedia.org/wiki/2024:Program/Hackathon#Language_Support> Cheers, Srishti *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

1 2

New draft text of WMF legal policy regarding use of APIs
by Luca Martinelli [Sannita＠WMF] 29 Aug '24

29 Aug '24

Hello all, We have published a new draft text of WMF legal policy discussing the use of its APIs. The full page is available on Meta.[1] We are currently looking for feedback on this draft text, and you're welcome to express your considerations on the text's talk page.[2] This new document would be published at "API usage guidelines" on the Foundation wiki, unless community comments suggest the text should be appended on an existing page (for example, the User-Agent policy page),[3] or a different wiki. This page is available for community comment for a period of at least two weeks or until new comments, questions, and suggestions have concluded. Thank you in advance for your consideration! [1] https://meta.wikimedia.org/wiki/API_Policy_Update_2024 [2] https://meta.wikimedia.org/wiki/Talk:API_Policy_Update_2024 [3] https://foundation.wikimedia.org/wiki/Special:MyLanguage/Policy:User-Agent_… -- Luca Martinelli [Sannita] (he/him) Movement Communications Specialist

1 0

New Code of Conduct Committee members
by Amir Sarabadani 28 Aug '24

28 Aug '24

Hello everyone, The Committee has finished selecting its new members. The new committee candidates are (in alphabetical order): - Amir Sarabadani - Egbe Eugene Agbor (Eugene233) - Greg Grossmeier - Jayprakash12345 - Kamila Součková Auxiliary members will be (alphabetically): - Effie Mouzeli - Joris Darlington Quarshie - Martin Urbanec - MusikAnimal - SD0001 You can read more information about the members at [1]. List of changes from the last term: - Greg and Kamila will be joining the main committee. - Nuria is leaving the main committee - MusikAnimal is moving to the aux committee - Tony is leaving the aux committee This is not the final structure. According to the CoC [2], the current committee publishes the new members and calls for public feedback for *six weeks* and after that, the current committee might apply changes to the structure based on public feedback. Please let the committee know (via techconduct(a)wikimedia.org) if you have any concern regarding the members and its structure until *08 October 2024* and after that, the new committee will be in effect and will serve for a year. [1] https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Members/Candidates [2] https://www.mediawiki.org/wiki/Code_of_Conduct/Committee#Selection_of_new_m… -- Amir (he/him)

2 1

Tech News 2024, week 35
by Nick Wilson (Quiddity) 26 Aug '24

26 Aug '24

Latest *tech news <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News>* from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2024/35> are available. *Feature news* - [image: Advanced item] Administrators can now test the temporary accounts <https://www.mediawiki.org/wiki/Special:MyLanguage/Trust_and_Safety_Product/…> feature on test2wiki. This was done to allow cross-wiki testing of temporary accounts, for when temporary accounts switch between projects. The feature was enabled on testwiki a few weeks ago. No further temporary account deployments are scheduled yet. Temporary Accounts is a project to create a new type of user account that replaces IP addresses of unregistered editors which are no longer made public. Please share your opinions and questions on the project talk page <https://www.mediawiki.org/wiki/Talk:Trust_and_Safety_Product/Temporary_Acco…> . - Later this week, editors at wikis that use FlaggedRevs <https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:FlaggedRevs> (also known as "Pending Changes") may notice that the indicators at the top of articles have changed. This change makes the system more consistent with the rest of the MediaWiki interface. [1] <https://phabricator.wikimedia.org/T191156> *Bugs status* - Editors who use the 2010 wikitext editor, and use the Character Insert buttons, will no longer <https://phabricator.wikimedia.org/T361465> experience problems with the buttons adding content into the edit-summary instead of the edit-window. You can read more about that, and 26 other community-submitted tasks that were resolved last week <https://meta.wikimedia.org/wiki/Tech/News/Recently_resolved_community_tasks> . *Project updates* - [image: Wishlist item] Please review and vote on Focus Areas <https://meta.wikimedia.org/wiki/Special:MyLanguage/Community_Wishlist/Focus…>, which are groups of wishes that share a problem. Focus Areas were created for the newly reopened Community Wishlist, which is now open year-round for submissions. The first batch of focus areas are specific to moderator workflows, around welcoming newcomers, minimizing repetitive tasks, and prioritizing tasks. Once volunteers have reviewed and voted on focus areas, the Foundation will then review and select focus areas for prioritization. - Do you have a project and are willing to provide a three (3) month mentorship for an intern? Outreachy <https://www.mediawiki.org/wiki/Special:MyLanguage/Outreachy> is a twice a year program for people to participate in a paid internship that will start in December 2024 and end in early March 2025, and they need mentors and projects to work on. Projects can be focused on coding or non-coding (design, documentation, translation, research). See the Outreachy page for more details, and a list of past projects since 2013. *Learn more* - If you're curious about the product and technology improvements made by the Wikimedia Foundation last year, read this recent highlights summary on Diff <https://diff.wikimedia.org/2024/08/21/wikimedia-foundation-product-technolo…> . - To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out: - Community Configuration - Shaping On-Wiki Functionality Together <https://commons.wikimedia.org/wiki/File:Wikimania_2024_-_Ohrid_-_Day_2_-_Co…> (55 mins) - about the Community Configuration <https://www.mediawiki.org/wiki/Special:MyLanguage/Community_Configuration> project. - Future of MediaWiki. A sustainable platform to support a collaborative user base and billions of page views <https://commons.wikimedia.org/wiki/File:Wikimania_2024_-_Belgrade_-_Day_1_-…> (30 mins) - an overview for both technical and non technical audiences, covering some of the challenges and open questions, related to the platform evolution, stewardship and developer experiences <https://www.mediawiki.org/wiki/MediaWiki_Product_Insights> research. *Tech news <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News> prepared by Tech News writers <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/Writers> and posted by bot <https://meta.wikimedia.org/wiki/Special:MyLanguage/User:MediaWiki_message_d…> • Contribute <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News#contribute> • Translate <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2024/35> • Get help <https://meta.wikimedia.org/wiki/Tech> • Give feedback <https://meta.wikimedia.org/wiki/Talk:Tech/News> • Subscribe or unsubscribe <https://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Tech_ambass…>.*

1 0

Coming soon: A new sub-referencing feature
by Johanna Strodt 23 Aug '24

23 Aug '24

*Apologies for cross-posting* Hello. I'd like to let you know that Wikimedia Deutschland’s Technical Wishes <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes> team is planning to deploy a new feature for sub-referencing. For many years, community members have requested <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Sub-referencing/Histo…> an easy way to re-use references with different details. Soon, there will be a MediaWiki solution for this, and it will work in wikitext and in Visual Editor. If you want to know more, take a look at this project page <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Sub-referencing>. Please note that the new feature will be *optional* – if you prefer other ways of referencing, you can keep using them. However, you will probably encounter sub-references in articles written by others. To make sure that sub-referencing works well for you, we are asking for your feedback: <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Sub-referencing#Test> <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Sub-referencing#Test> - <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Sub-referencing#Test>Please try <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Sub-referencing#Test> the current state of development on beta wiki and let us know what you think <https://meta.wikimedia.org/wiki/Talk:WMDE_Technical_Wishes/Sub-referencing> . - Sign up here <https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Sub-referencing/Sign-…> to get updates and/or invitations to participate in user research activities. We plan to deploy this feature to the Wikimedia wikis later this year. Before that, we will check in with creators/maintainers of reference-related tools and templates. And we will send more announcements when we get closer to the deployment date. If you can already help us spread the message on your wikis, that would be much appreciated! For Wikimedia Deutschland's Technical Wishes team, Johanna Strodt Community communications Technical Wishes

5 6

Wikimedia AIOps Experiment on Public Incident Reports
by Siddarth Jain 22 Aug '24

22 Aug '24

Hi Wikimedia team, I'm Siddarth, Founder of an Open Source runbook automation framework Doctor Droid PlayBooks <https://github.com/DrDroidLab/playbooks>. At Doctor Droid, we're currently working on a self-serve AIOps platform <https://docs.drdroid.io/docs/doctor-droid-aiops-platform>. As part of it, I attempted an experiment on Wikimedia's publicly available Incident Reports where I leveraged it to extract correlations that can be used in multiple ways -- Here's a video showing it's output <https://www.youtube.com/watch?v=vXNMGsy_72s> & how it could be used. If your team would be open to exploring an experiment where we support your team with the Doctor Droid AIOps platform (with 6 months free trial & no commitments), I'd love to discuss more. I appreciate your team making the data publicly accessible. -- Regards, Siddarth Founder, Doctor Droid

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 August 2024