Wikitech-l August 2022

wikitech-l@lists.wikimedia.org

37 participants
44 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

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

TDF is looking for community representatives
by Erica Litrenta 05 Oct '22

05 Oct '22

*(This email may not be written in your native language, and/or may be a crosspost: our apologies.)* Greetings, everyone. The Technical Decision Forum, or TDF (1), is seeking community representatives. Please visit the TDF Community Representation (2) page for more information, and email TDFSupport(a)wikimedia.org by Aug 12, 2022 to be considered for selection. Don't worry about the requirements listed on wiki, they are not set in stone; just provide your name, name of the group you "represent" if any, and a short sentence or two explaining your interest. For any questions, please post at *MediaWiki.org (3)*, or on the related Movement Strategy Forum topic (4), or simply email TDFSupport(a)wikimedia.org. Thanks, The Technical Decision Forum. (1) https://www.mediawiki.org/wiki/Technical_decision_making/Forum (2) https://www.mediawiki.org/wiki/Technical_decision_making/Community_represen… (3) https://www.mediawiki.org/wiki/Talk:Technical_decision_making/Forum (4) https://forum.movement-strategy.org/t/technical-decision-forum-tdf-is-looki… -- ------------------------------ Erica Litrenta (she/her) Senior Manager, Community Relations Specialists (Product) Wikimedia Foundation <https://meta.wikimedia.org/wiki/User:Elitre_(WMF)>

2 2

Upgrade the Search clusters to Elasticsearch 7.10.2
by Guillaume Lederrey 22 Sep '22

22 Sep '22

Hello all! For the last 2 quarters, the Search Platform team has been working on upgrading our Elasticsearch clusters to version 7.10.2 [1]. Keeping our software up to date is part of the usual project hygiene, allowing us to benefit from bugs and security fixes, performance improvements, and new features. In our case, upgrading to Elasticsearch 7.10.2 is also a required step towards a potential move to OpenSearch [2]. After much testing, fixes and validations, we are now ready to start the final migration process. We are anticipating a 3-week migration process, starting on August 29 2022. You can follow along on Phabricator [3]. What does this mean for you? For users of Special:Search, Special:MediaSearch and other user-facing Search interfaces, the upgrade should be fully seamless, and should not cause any disruptions to normal usage. For users of Cloudelastic [4] who are accessing the Elasticsearch API directly, there might be minor API changes that could affect your queries. Please review the documented breaking changes [5]. Most of the breaking changes are not related to queries, so it is unlikely that any client code will break with this upgrade. If you have any questions about this process, you can find us in #wikimedia-search on IRC, or at discovery(a)lists.wikimedia.org. Have fun! The Search Platform team [1] https://phabricator.wikimedia.org/T263142 [2] https://phabricator.wikimedia.org/T280482 [3] https://phabricator.wikimedia.org/T308676 [4] https://wikitech.wikimedia.org/wiki/Help:CirrusSearch_elasticsearch_replicas [5] https://www.elastic.co/guide/en/elasticsearch/reference/7.17/breaking-chang… -- *Guillaume Lederrey* (he/him) Engineering Manager Wikimedia Foundation <https://wikimediafoundation.org/>

1 1

Outreachy Round 25–call for projects and mentors now open!
by Srishti Sethi 08 Sep '22

08 Sep '22

Hello everyone, Wikimedia is participating in the winter edition of this year's Outreachy < https://www.outreachy.org/> [1] (December 2022–March 2023)! The deadline to submit projects on the Outreachy website is September 30th, 2022. We are currently working on a list of interesting project ideas. If you have some ideas for coding or non-coding (design, documentation, translation, outreach, research) projects, share them here: < https://phabricator.wikimedia.org/T313361> [2]. *About the Outreachy program* Outreachy offers three-month internships to work remotely 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. Interns often find employment after their internship with Outreachy sponsors or jobs that use the skills they learned during their internship. This program 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. * Residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latinx, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander. See a blog post highlighting the experiences and outcomes of interns who participated in a previous round of Outreachy with Wikimedia < https://techblog.wikimedia.org/2021/06/02/outreachy-round-21-experiences-an…> [3] *Tips for mentors for proposing projects* * Follow this task description template when you propose a project in Phabricator: < https://phabricator.wikimedia.org/tag/outreach-programs-projects> [4]. Add #Outreachy-Round-25 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/> [4] * To learn more about the roles and responsibilities of mentors, visit our resources on MediaWiki.org: < https://www.mediawiki.org/wiki/Outreachy/Mentors> [5]. We look forward to your participation! Cheers, Srishti [1] https://www.outreachy.org/ [2] https://phabricator.wikimedia.org/T313361 [3] https://techblog.wikimedia.org/2021/06/02/outreachy-round-21-experiences-an… [4] https://phabricator.wikimedia.org/tag/outreach-programs-projects/ [5] https://www.mediawiki.org/wiki/Outreachy/Mentors *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

4 10

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 2022