I wonder if there is another organization (Linux Foundation?) that Wikimedia could partner with in order to continue maintaiance and development of Phabricator?

In T178137#6922433, @dbarratt wrote:

In T178137#6922407, @Reedy wrote:

Sure. But if we/composer just follow what the composer.lock says, that doesn't get towards any sort of "maintained automatically", does it?

What do you mean? This gets maintained automatically if we were to use composer to load the extensions themselves. This is basically what the Drupal project does.

In T178137#6922407, @Reedy wrote:

Sure. But if we/composer just follow what the composer.lock says, that doesn't get towards any sort of "maintained automatically", does it?

In T178137#6921190, @Reedy wrote:

Probably not gonna happen. If we allow post merge jobs to randomly update/install stuff, it defeats the point of the auditability of having the mediawiki-vendor repo etc.

In T254405#6758944, @AdamMillerchip wrote:

I also ran into this and the solution was the same: the hostname needs to be the name of the docker host when running with docker-compose. I'd submit a PR, but the error is on Docker Hub, and I don't see an obvious way to edit that.

Also, would highly recommend looking the the other CMS counterparts such as:
https://hub.docker.com/_/drupal
and
https://hub.docker.com/_/wordpress

I would highly recommend taking a look at https://hub.docker.com/_/php which is the image the MediaWiki image extends from.

In T268987#6721885, @abi_ wrote:

1. Could you give push access to https://github.com/translatewiki in order to push the translations?

In T36928#6712648, @DannyS712 wrote:

So, to clarify the status of this task: I marked it as stalled because the patch has a -2 from @Anomie saying "Giving this a -2 until the concerns raised on the task are addressed...The problem is concern over the impact when only some users are prevented and others are not."
I believe that, since my patch does not grant the right to any users by default, this is not really an issue - end users (sites) can decide if they want to grant the right to a specific user groups, and deal with the results accordingly

This task doesn't seem related to React-i18n, but I would highly recommend using it in your project. :)

The Docker-Hub-MediaWiki tag is for the image at https://hub.docker.com/_/mediawiki not the Wikibase (3rd party installations) images.

This should already be supported (at least in Apache) Have you tried setting $wgArticlePath ?

That's better. :)

Oops.. missed one more category. One moment.

This is done. All fields are nullable (in other words, any field could be missing)

I fixed the "Create Task" link in the sidebar. :)

@Lonaowna Docker-Hub-MediaWiki is for the image hosted at https://hub.docker.com/_/mediawiki for the images described at https://www.mediawiki.org/wiki/MediaWiki-Docker you'll want MediaWiki-Docker. The images serve different purposes.

In T265627#6549096, @dbarratt wrote:

Sorry it should have been a g in the url, not an r

In T265627#6549049, @Aklapper wrote:

This is the code base located at https://gerrit.wikimedia.org/g/react.i18n , correct?

In T261461#6544466, @Mholloway wrote:

Let me make sure I understand the issue: when a user mutes another user via the Special:Mute web UI, we would expect both a PrefUpdate and a SpecialMuteSubmit event to be created and sent to their respective eventlogging tables, and this indeed happens locally, but in production it appears that only the SpecialMuteSubmit event is created and persisted. Is that correct?

In T264837#6544039, @Tchanders wrote:

@dbarratt While I was working on T264905 I noticed that there are around 50 data fields. I'm wondering if it's really worth copying them all out here?

Just to clarify, this task is not to remove keyboard navigation, it is to remove the color change on table focus (i.e. the highlighting will only happen on hover)

In T212976#6541250, @DannyS712 wrote:

@dbarratt when would such a feature be needed / how would it be used? C.f. XY problem

In T264838#6534396, @CDanis wrote:

@dbarratt see also T263263#6534392 :)

FYI: I looked for it on mwmaint2001

Found it! It's in /usr/share/GeoIP

$ ls -lah /usr/share/GeoIP
total 276M
drwxr-xr-x   2 root root 4.0K Oct  4 03:52 .
drwxr-xr-x 170 root root 4.0K Aug  4 00:10 ..
-rw-r--r--   1 root root 127M Oct  4 03:52 GeoIP2-City.mmdb
-rw-r--r--   1 root root 3.8M Oct  4 03:52 GeoIP2-Connection-Type.mmdb
-rw-r--r--   1 root root 4.0M Oct  4 03:52 GeoIP2-Country.mmdb
-rw-r--r--   1 root root  11M Oct  4 03:52 GeoIP2-ISP.mmdb
-rw-r--r--   1 root root 3.8M Jul 12  2018 GeoIPASNum.dat
-rw-r--r--   1 root root 4.5M Jul 12  2018 GeoIPASNumv6.dat
-rw-r--r--   1 root root  49M Oct  4 03:52 GeoIPCity.dat
-rw-r--r--   1 root root 1.9M Oct  4 03:52 GeoIP.dat
-rw-r--r--   1 root root 1.1M Oct  4 03:52 GeoIPNetSpeedCell.dat
-rw-r--r--   1 root root 1.3M Oct  4 03:52 GeoIPNetSpeed.dat
-rw-r--r--   1 root root 6.7M Oct  4 03:52 GeoIPRegion.dat
-rw-r--r--   1 root root 1.4M Jul 12  2018 GeoIPv6.dat
-rw-r--r--   1 root root  31M Jul 12  2018 GeoLite2-City.mmdb
-rw-r--r--   1 root root  16M Jul 12  2018 GeoLiteCity.dat
-rw-r--r--   1 root root  16M Jul 12  2018 GeoLiteCityv6.dat
-rw-r--r--   1 root root 743K Jul 12  2018 GeoLite.dat

(oops, updated the condition in the example SQL in the previous comment)

In T261461#6534043, @jwang wrote:

@dbarratt I found only 2 events for the entire 2020 that the before and after are all false. The timestamps are show as below.

My sql code:

SELECT  *
FROM specialmutesubmit
WHERE
 year=2020 
 AND NOT event.emailsbefore 
 AND NOT event.emailsafter
 AND NOT event.notificationsbefore 
 AND NOT event.notificationsafter

In T265176#6534098, @Yurik wrote:

Not exactly, even though this is also possible. There are cases in my app when i could be using multiple Banana contexts in the same place, e.g. showing text/links in different languages

It took me a bit, but I was finally able to reproduce this problem.

There are cases when I would like to use the functionality of the Message but without any context, e.g. from inside the Redux state, but still be able to construct a React object tree and do all the current functionality like using React elements as placeholders.

In T264545#6530570, @Niharika wrote:

@dbarratt I think so! Should we stall this task until we have determined how anon identifiers will work post T262321: IP Masking?

In T264545#6525791, @Niharika wrote:

@dbarratt Does the title rename make sense? Trying to get a sense of what we'll achieve from implementing this API endpoint.

To do this we will need a new table in the IPInfo extension that stores the user name, the timestamp when they first gained access, and whether they have had their access revoked.

We could fix this problem by restoring the focus to the previous element that was focused before the click. Basically:

I'm not sure why a new table is necessary, see T263756#6501992

@eprodromou Thanks that is helpful. Let's say we have a stable (v1) endpoint that we decide to deprecate, would we include that in the response or what that be a part of the route metadata in extension.json ?