Wikitech-l January 2020

wikitech-l@lists.wikimedia.org

68 participants
60 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 28 Jun '24

28 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 23 Feb '23

23 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

realtime notifications disabled in Phabricator
by Daniel Zahn 17 Aug '20

17 Aug '20

Phabricator users, this is to let you know that the "aphlict" service has been disabled on Phabricator (for now) because it caused stability issues. This means you will not get realtime (pop-up) notifications on Phabricator. (If you had those enabled in the first place). Regular notifications (that do not pop-up) and emails are not affected by this. https://phabricator.wikimedia.org/T238593 -- Daniel Zahn <dzahn(a)wikimedia.org> Operations Engineer

8 15

New DB_REPLICA constant; DB_SLAVE deprecated
by Aaron Schulz 04 Jul '20

04 Jul '20

As of 950cf6016c, the mediawiki/core repo was updated to use DB_REPLICA instead of DB_SLAVE, with the old constant left as an alias. This is part of a string of commits that cleaned up the mixed use of "replica" and "slave" by sticking to the former. Extensions have not been mass converted. Please use the new constant in any new code. The word "replica" is a bit more indicative of a broader range of DB setups*, is used by a range of large companies**, and is more neutral in connotations. Drupal and Django made similar updates (even replacing the word "master"): * https://www.drupal.org/node/2275877 * https://github.com/django/django/pull/2692/files & https://github.com/django/django/commit/beec05686ccc3bee8461f9a5a02c607a023… I don't plan on doing anything to DB_MASTER, since it seems fine by itself, like "master copy", "master tape" or "master key". This is analogous to a master RDBMs database. Even multi-master RDBMs systems tend to have a stronger consistency than classic RDBMs slave servers, and present themselves as one logical "master" or "authoritative" copy. Even in it's personified form, a "master" database can readily be thought of as analogous to "controller", "governer", "ruler", lead "officer", or such.** * clusters using two-phase commit, galera using certification-based replication, multi-master circular replication, ect... ** https://en.wikipedia.org/wiki/Master/slave_(technology)#Appropriateness_of_… *** http://www.merriam-webster.com/dictionary/master?utm_campaign=sd&utm_medium… -- -Aaron

4 3

Google Code-in 2019: Read what students worked on
by Andre Klapper 07 Feb '20

07 Feb '20

A few days ago, Google Code-in 2019 ended. 194 students completed 715 Wikimedia tasks.[1] Big thanks and congratulations to everybody! Read about their GCI experience with Wikimedia in their blog posts: https://www.mediawiki.org/wiki/Google_Code-in/2019#Wrap-up_blog_posts Thanks to our 43 mentors for being available, also on weekends & holidays. Thanks to everyone on IRC, Gerrit, Phabricator, mailing lists, Github, etc. for your friendliness, patience, support and help. Thanks to Wikimedia org admins for making this run really smoothly. And thanks to Google for organizing this opportunity for young people to learn about and contribute to free software and free knowledge. Google will announce Grand Prize winners and finalists on February 10. We also welcome everybody's feedback what Wikimedia could improve: https://www.mediawiki.org/wiki/Google_Code-in/Lessons_learned#2019 Sharing some of the students' achievements, to give you an impression: * WMCZ's Tracker software received 40 fixes and improvements * 37 fixes and improvements to the WatchTranslations tool * 24 fixes and improvements to the VideoCutTool tool * 12 fixes and improvements to the WikiContrib tool * Tasks to learn programming in Lua were completed 218 times (such as: Introduction to Lua in Wikipedia, Working with modules, Calculations and tests, Loops and tables, Lua libraries, MediaWiki libraries, Wikibase client, Name formats, Date formats, Using Wikidata) * 13 extensions got extension.json converted to manifest_version 2 * 8 extensions got jshint and jscs replaced with eslint * 5 extensions got jsonlint replaced with eslint * Blockly, Huggle, Phabricator, video2commons, and Wiki Ed Dashboard got migrated to the new Translate validator framework * Flask-JSONLocale received three bug fixes * Watchlist notifications can be delivered as web notifications through Echo (but not enabled yet on Wikimedia sites) * Kiwix Android App has a button to search for a new article * Quarry has a button to toggle syntax highlighting * Wikilink tool has a namespace filter and can filter bot edits * Commons Android App has screenshots in 14 more languages, the username can be clicked in the navigation drawer, an improved share message, and videos for best media upload practices were created * Commons Mass Description tool: /users does not throw a fatal error * EasyTimeline has a system message to track category description * MediaWiki Core's UploadFromUrl::isAllowedHost has tests * Google Drive to Commons tool allows removing files after selection before uploading, and has a redesigned 'upload complete' screen * Hashtags tool allows charts to be downloaded as images * MobileFrontend extension allows turning on the lead paragraph in other namespaces and the nav menu drawer received a CSS shadow * DynamicPageList extension uses page images as the image in gallery mode for pages which are not in the File namespace * MassMailer tool has improved internationalization, its alerts are dismissable, and is integrated with Translatewiki.net * Map of Monuments tool can filter by country and language * Wiki Education Dashboard Android App has better screenshots and a placeholder for empty screens * WikiEduDashboard has a git pull hook to update gems and packages, and its ArticleViewer adds appropriate styling for Wikidata * Music on Wikimedia pages was transcribed to LilyPond 9 times * 4 templates on English Wikipedia received Documentation * A web app to showcase a variety of tools hosted on Wikimedia Toolforge was created * meta:Research_on_open_source_team_communication_tools was expanded * Hackathons of other FOSS orgs were researched, to improve ours * 14 text files in MediaWiki core's /doc got converted to Markdown * Logos designed for VideoCutTool tool, the MediaWiki FormWizard Extension, the Friends of the Docs working group, and the Google Drive to Wikimedia Commons Uploader tool * Designs for "Personal Space Needed" and "Wikimedia Friends of the Docs" stickers created * HD logos were added for several Wikimedia project websites Thanks for helping making free knowledge available to everybody. <3 On behalf of the org admins, andre [1] https://www.mediawiki.org/wiki/Google_Code-in/Statistics -- Andre Klapper (he/him) | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/

3 2

Wikimedia Hackathon 2020: Registration Open!
by Rachel Farrand 06 Feb '20

06 Feb '20

On behalf of Open Labs Albania <https://openlabs.cc/en/> and the Wikimedia Foundation Community Events Team we are pleased to announce that registration for the Wikimedia Hackathon 2020 <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2020/Register> is now open for both scholarships and regular attendees! The hackathon will be held at OFIÇINA <http://www.oficina.al/> in Tirana, Albania between 9-11 May 2020 (please note that this is a Saturday through Monday instead of the usual Friday - Sunday). Additionally, we encourage attendees to stay in Tirana and attend the 7th annual Open Source Conference Albania (OSCAL) <https://oscal.openlabs.cc/> which will be in the same venue on May 16th and 17th, and will have a Wikimedia Track and mission aligned organizations participating. We have identified two focus areas <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2020#Hackathon_Focus_Are…> for the event which we will continue to refine and clarify over the next months. As usual, we welcome participants who plan to work on or learn about any project that they like related to any area of Wikimedia Technology. If you have any questions or comments please contact: wiki-hackathon(a)openlabs.cc Otherwise, please continue to follow our program and organizational developments on Wikimedia Hackathon 2020 on Mediawiki <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2020>. Please help us by forwarding this email to relevant lists and looking forward to see you in Tirana! -- Rachel Farrand Senior Program Manager Events Team Wikimedia Foundation

2 3

"Chain verification error" when trying to log-in to Beta cluster
by Kaartic Sivaraam 01 Feb '20

01 Feb '20

Hi all, I'm writing this email about an issue we recently faced in the Wikimedia Commons Android app. The beta flavour[1] of the Commons app connects to the Wikimedia Commons beta cluster[2]. When trying to log-in to the beta cluster using valid credentials we get the following error[3]: javax.net.ssl.SSLHandshakeException: Chain validation failed We get this error when trying to do the following API call: https://commons.wikimedia.beta.wmflabs.org/w/api.php?format=json&formatvers… This seems to be a problem only when making the API call to get the login token from the app (IIUC, we use OkHttp to make the API call). The same API call succeeds without issues when done using the browser. We're not sure what's causing this issue. We've stopgapped the issue[4] for the mean time but we would like to identify the actual problem and fix it. It would be nice if someone could help us with identifying the problem. If there's a better place or person to contact about this issue please let us know. As the stopgap fix has been merged, the beta version built from the latest source in 'master'[5] would not have the issue described above. The source that has the issue can be found at [6]. Notes and references [1]: It's different from the beta version released in Play store. [2]: https://commons.wikimedia.beta.wmflabs.org [3]: Unable to login #3320 - https://github.com/commons-app/apps-android-commons/issues/3320 [4]: https://github.com/commons-app/apps-android-commons/pull/3349 and https://github.com/commons-app/apps-android-commons/pull/3350 [5]: https://github.com/commons-app/apps-android-commons/tree/master [6]: https://github.com/commons-app/apps-android-commons/tree/fe56cefdbca21125e9… Thanks, Sivaraam

2 2

Poll: What algorithms do you program into your wikis?
by Daren Welsh 01 Feb '20

01 Feb '20

As research for a potential presentation topic at EMWCon 2020 [0], I'm polling the community. What algorithms do you program into your wikis? I'm curious to learn about technical methods, policies, and criteria for measuring "success". I'm interested in this concept because of how algorithms are used in social media tools and many have been called out for being "bad". So I wonder if wikis are any better. And don't just limit the analogy to social media. There's things like Amazon's suggested purchases or the stack exchange voting system selecting a "correct" answer by election. For example, the extension Watch Analytics recommends which pages need review based on how many people have reviewed each changed page. I think there are voting/rating systems for wikis. I wonder how those influence decisions. At one time I was working on an extension that built on the idea of contribution score, but I feared it would incentivize the "wrong" behavior. I'm looking for how algorithms influence content presented to users, but also if algorithms are used to make decisions. Here are some other examples of what I would consider algorithms in wikis: - Human driven voting systems like stack overflow - Category and Property driven - Using Wikibase, Cargo, or SMW to determine a priority or to identify a missing value - Machine-learning - Antivandalism/spam tools - Suggestions for which wiki pages to watch based on links between wiki pages - Suggestions for which wiki pages to review based on watchlists and how many people have seen the page since it was last edited - Suggestions for which users to collaborate with based on pages each person has edited - Contribution scores drive users to make more edits and to edit more pages. Is this what we really want? - Other? Of the algorithms you use in your wikis, how do you measure success? What does it mean to say that your algorithm is "working" or "succeeding"? How do you know your algorithm is not inducing bias in a bad way? If you'd like to share any info on how you use algorithms and how you measure success in using them, please reply directly to me (unless you want to share with the list). I'd appreciate screenshots and other ways to help me understand how your algorithm works and is used, so I can properly represent it in my presentation. I hope to get enough responses to showcase the flexibility of MediaWiki in how it can be used to drive decisions based on knowledge. Daren [0] https://www.mediawiki.org/wiki/EMWCon_Spring_2020 __________________ https://www.mediawiki.org/wiki/User:Darenwelsh http://mixcloud.com/darenwelsh

2 1

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 January 2020