Wed, Nov 25
Diffusion needs some time to sync its mirrors so the skin is shown as archived here as well.
Mon, Nov 23
Oct 27 2020
This is just stale…
Oct 23 2020
Oct 17 2020
Oct 9 2020
You did not specify any extension/skin here. After doing so, feel free to repoen.
Sep 10 2020
Jul 20 2020
Jul 19 2020
Jul 13 2020
I think the way forward proposed by the patch is confusing. Either we should remove the setting altogether, or keep it functional for another version of MediaWiki. Removing its functionality without removing the setting seems unhelpful at best.
Jul 6 2020
Jun 24 2020
Requested public project User-Demian has been created: https://phabricator.wikimedia.org/project/view/4852/
Jun 14 2020
Are you sure you are pushing to the correct URI? (http://phabricator.wikimedia.org/source/tool-commons-android-app.git) and using the correct credentials?
Jun 13 2020
Jun 5 2020
Jun 3 2020
May 27 2020
Considering the discussion in T236809, I am against doing anything here. There is no suitable alternative, as InternalParseBeforeLinks will probably recieve the same treatment, and the deprecation should be removed soon.
The problem of deprecations is that they can not just be ignored by extension developers, as they make unit tests fail. Such, jenkins awards -1 Verified to every changeset uploaded for an extension that does use them.
By the way, what I really do not like here is that there is no reasonable path forward for extension developers. If I replace hooks by other hooks that are not deprecated yet, there is a high probablity that those other hooks will be deprecated a few months later, for example the InternalParserBeforeLinks hook.
May 26 2020
Can we do the same for the InternalParseBeforeSanitize hook?
May 25 2020
Can you try again with the master version of the Arrays extension? This is probably broken because the global default value has been broken for some time in v2.2: https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/Arrays/+/6a47eac735e7cd9c16b445453f960e6b057845ae
May 23 2020
May 14 2020
May 12 2020
Adding documentation in a way like this is recommened in the extension registraion documentaton, which is why I added it.
Currently, it says that this is not supported for config anymore, but when I added the key, it stated otherwise.
May 10 2020
To clarify something: I think I translated my thoughts into English in a misleading way: When I was talking about "objecting", I meant that I would like to raise the question why the request was refused, considering other decisions concerning membership in acl*repository-admins have been handled much more lenient in the past. In particular, I had no intent to overrule this decision (which would be totally presumptuous) or anything like that, but just to ask to reconsider.
May 7 2020
If T249730 is resolved, can it be made public?
May 6 2020
Considering the European GDPR, we might even be legally mandated to provide this information to users, as users have the right to access any information a given website is storing about him.
Apr 27 2020
Apr 25 2020
I think blocking MessMessages would create more problems than it would solve. Massmessages which are not delivered to single persons because of partial blocks seem to be quite problematic to me.
Apr 24 2020
This task would be done when every extension has its own project and MediaWiki-extensions-Other is archived.
Please be aware that in the current parser implementation, some extensions use the onClearState hook provided by MediaWiki. Are you planning on removing that too?
Apr 23 2020
This can not be fixed by the extension without dropping features. See T236809 for further information.
Apr 15 2020
I would like to object this refusal. This is about phabrricator repository adminship, not about gerrit permisions. In practice, these are used for repository management stuff and nothing else.
Apr 14 2020
Apr 13 2020
Apr 3 2020
Rejecting worked for me now.
Apr 2 2020
Mar 17 2020
Mar 12 2020
Mar 8 2020
Feb 18 2020
This puzzled me – is there any reason why this is open about 50 times longer than these tasks usually are? Is there something blocking this?