Wikitech-l June 2020

wikitech-l@lists.wikimedia.org

66 participants
72 discussions

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

List related to repositories which haven't mediawiki/mediawiki-codesniffer
by Zoran Dori 11 Jan '23

11 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

"Library" for sharing useful resources for learning technical topics
by Amir Sarabadani 21 Sep '20

21 Sep '20

Hello, Recently, I stumbled upon a technical writing course which I found very useful and I wanted to share it and thought of sending an email to wikitech-l recommending it. Also, I've been looking for a resource about VueJS with not much luck and wanted to send an email asking if anyone knows any. Instead, I have this idea to have a virtual library for developers so they can share useful resources with each other. You go to a wiki page and see list of courses, books, conference videos, on each topic and different people recommanding them. You can also request a resource for a topic and people respond to you. If the wiki page grows too big, we can split them to sub pages based on topics, and so on. I started the page in https://www.mediawiki.org/wiki/User:Ladsgroup/Library but I'm planning to move it to the main namespace if no one objects. Please take a look, add more recommandations, co-sign, request for a resource, respond to a request for a resource, etc. What do you think? Please let me know if you think it's a horrible idea or you have feedback on details (mediawiki.org? maybe we should move it to wikitech.wikimedia.org?) Hope that'd be useful. Best -- Amir (he/him)

7 7

(Low prio) Do we still need AtEase?
by Krinkle 09 Sep '20

09 Sep '20

It does the same as the @ operator, except that it takes care to prevent a very bad bug that existed before PHP 7. Details at https://phabricator.wikimedia.org/T253461 If there are other issues or benefits, please write them on the task. The overhead of AtEase is prerty minor, so really any benefit at all is likely to tip the balance toward keeping it. But, in the event that there isn't any, then perhaps we should slowly phase it out. Best, -- Timo

1 1

Logo of mediawiki
by Amir Sarabadani 04 Sep '20

04 Sep '20

Hello, The current logo of MediaWiki was adapted slightly more than fifteen years ago and hasn’t changed since. This logo despite having the nice concept of sunflower, is old. The sunflower represents the diversity, the constant growth and also the wildness. Among its biggest issues I can point out that it’s a bitmap picture so it’s unusable in large sizes (like large posters) and it’s too realistic making it unusable in small sizes. Most, virtually all, software products use a simpler and more abstract form. For example, docker, kubernetes, Ubuntu, VueJs, React, Apache Kafka, and many more. It’s a good time for MediaWiki to follow suit. My request is for changing the logo of MediaWiki and I have no plans or interest in changing logo of any other project. Please show your support, oppose or your comments in the discussion page. You can also add more suggestions. The discussion page: https://www.mediawiki.org/wiki/Project:Proposal_for_changing_logo_of_mediaw… Best -- Amir (he/him)

1 3

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

MediaWiki 1.35 Branch Cut and Release
by Cindy Cicalese 08 Jul '20

08 Jul '20

On March 30, we announced that we were temporarily pushing back the release of MediaWiki 1.35 due to uncertainty resulting from the COVID-19 pandemic. We are now ready to begin the process of moving forward with the release. The first step is cutting the release branch, REL1_35, which will occur on Monday, July 13. We will then be in "pencils down" mode: developers will stop targeting MediaWiki 1.35 for new features. Instead, any new features would continue to be applied to master and would target MediaWiki 1.36 or later. The only work that would continue towards MediaWIki 1.35 would be blockers - critical bug fixes or features close to completion that need to make it into the release. This would happen by merging those patches into master and then backporting them to the REL1_35 branch. We anticipate that MediaWiki 1.35 will be released at the beginning of August. We appreciate your patience in these difficult times. Wishing you safety and health, Cindy

3 2

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

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 2020