@Legoktm Do you know when you will have time to take another look at this change? I implemented your feedback.

Requested public project User-crusnov has been created: https://phabricator.wikimedia.org/project/view/3884/

Marking this as Resolved for the time being.

@Krinkle I don't think it is supposed that change project scopes are changed without consultig with Project-Admins first, especially as the scope of this project has been the result of a discussion here.

Requested public project User-EBernhardson has been created: https://phabricator.wikimedia.org/project/view/3865/

While I'm not involved in deciding this, I would appreciate you doing actual code contributions first. The commits you linked here are still more on the trivial side of things.

Requested public project User-DannyS712 has been created: https://phabricator.wikimedia.org/project/view/3849/

In T213880#4883399, @mmodell wrote:

Maybe we should archive MediaWiki-extensions-Other first, then create projects for extensions on an as-needed basis.

In T213880#4883219, @Aklapper wrote:

Thanks for filing this.

Leaving a talk page message for the authors to watch the relevant projects.

This needs to happen before creating a project tag, and getting consent and agreement from the developer/maintainer that they want to use Wikimedia Phabricator for tracking tasks and especially that there is not already an issue tracker somewhere else. I do not want to create a place in Wikimedia Phabricator where people file tasks while the maintainer/developer of a codebase expects those tasks to be filed somewhere totally else.

I agree that it doesn't really matter if tasks are filed as long as there is not separate project for them, as noone will ever find them anyway. However, if noone is active at maintaining a project, I don't know if this will really solve the issue.

In T213875#4883103, @Nuria wrote:

Rather than focusing on the bad actor why not focus in the target giving them tools to protect interactions? For example: they can protect their talk pages such to post you need to know the "secret" word (similar to a captcha), this way interactions are "whitelisted"

I agree with @Mainframe98 here.

@Legoktm Do you know when you will have time to review this change?

Thank you very much!

While I read the code in a way that you shouldn't be able to set this permission with the userights permission (because of the way User->getAllGroups works), is this displayed on ListGroupRights correctly? It might be ignored there as well an could look weird with no permissions assigned.

@Bawolff Can you please take another look on the patch?

Maybe a script reading the PHP version parameter of MediaWiki.org infoboxes and code searches for extension keywords can do much of the work.

Created T212489 to add this to extensions.

So, this should resolve remaining release blockers.

Taking a look at the remaining release blockers, I'll make a Release notes patch asap, as this is the only thing that's left here.

To avoid confusion here, I'll split this in two tasks:

• This task is just about the things implemented already. These have to be added to the Release notes before the release. I don't want this to be forgotten.
• T212472 tracks the work about platform abilities that hasn't been merged yet.

In T197535#4827645, @daniel wrote:

What's still missing here? The ability for extensions to require a php version, as requested by this ticket, appears to have landed, plus the ability to require php extensions. The patch that is still open seems to be for specifying platform capabilities. That seems to go well beyond the scope of this ticket. Should that really block the release? Am I missing something?

I aimed to implement everything @Legoktm has proposed in T197535#4310069. This might be out of scope considering the current task title, but I considered it part of this feature and considering this, part of this task as well. Maybe it's a good idea to split this task into two.

I was confident that this patch is merged before MW 1.32 is released, but I seemingly misjusged that. I wanted to point out that there is no reference in the release notes about the changes already merged into MW 1.32 currently, as I planned to do this after all patches are merged. We should add this.

@Legoktm Do you have time to take a look at this?

I don't think I have knowledge and time to really contributed, I just subscribed this task because I'm interested in development and improvement of the Math extension.

Yep: https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/Variables/+/474227/

Yes.

Unaware of this, I just were annoyed because of the hugenedd of MediaWiki-Page-editing and moved all open tasks to a separate workboard column.