As the scopes are still undocumented yet (I checked the link now) I am going to remove myself from this task for the time.

@Legoktm those benchmark results are a bit old, while fluidsynth might got an update, I can update them if required :)

Here are some thoughts from my side as a GCI participant:

In T185447#3917132, @Aklapper wrote:

Is this about some local change specific to Wikimedia's instance of Phabricator, or does this apply to any Phabricator in general (which would make this an upstream issue)?

Looking at the current source of Phabricator on GitHub, the "required" scope for user.whoami is referring to self::SCOPE_ALWAYS, therefore the docs for https://github.com/ofbeaton/oauth2-phabricator should be updated to list that scope.

Added missing documentation to the extension wiki page:
https://www.mediawiki.org/w/index.php?title=Extension:Score&oldid=2697225

In T185317#3913844, @Dalba wrote:

In T185317#3913727, @divadsn wrote:

@Dalba ok, that's a point, but now why the revert?

That patch could be fixed with a follow-up, which would be simply adding a |Invalid ISBN found to the regex, why not instead?

IMO, https://gerrit.wikimedia.org/r/#/c/399348/ was more deserved to be merged. It was submitted before your patch and it did not have this issue.

But it had other issue and the author wasn't doing anything for a month since that day, that's why I took it up and made mine when working on the task with @jayvdb as mentor.

@Dalba ok, that's a point, but now why the revert?

Afaik it's usually supposed to install all needed requirements from the requirements.txt, but I may be wrong here.

Running on Windows, make sure you don't have python-stdnum installed.

In T168716#3913425, @ABorbaWMF wrote:

@Jdlrobson, do we have a target article for this test on Staging? I have been looking for an article using the template in question, but I have not found one.

I wrote my blog post in English, it lacks a bit at the end, but ready for the public :)
https://www.codebucket.de/blog/contest/2018/01/17/google-code-in-2017-and-the-future.html

I made my suggestion over at the discussion page, hope it will be fixed soon :)
https://www.mediawiki.org/wiki/MediaWiki_talk:Titleblacklist#Google_misspelling_pattern_matching_wrong_for_Talk:_pages

11:06:35 <RexxS> divadsn: the blacklisting of a title is via the Extension:TitleBlacklist - https://www.mediawiki.org/wiki/Extension:TitleBlacklist

This filter might be present here: https://www.wikidata.org/wiki/Special:AbuseFilter

I'm sorry that I've overlooked the basic styling of those elements, now I re-done the patch and kept those styles in tact, only changed the scaling behavior.

Closing as the original PR got merged a week ago.

@Stemby MP3 files are better for mobile users from my experience when it comes to loading time and file size.

Now it's possible to slowly migrate from TiMidity++ to Fluidsynth and then after a period of time drop support for TiMidity++ :)