In T9195#209617, @OrangeStar wrote:

I'm going to make a subtask for the "using heavy JavaScript to modify groups and namespaces" part, I have an idea on how to do that without adding any new APIs (at least the namespaces part).

I'm going to make a subtask for the "using heavy JavaScript to modify groups and namespaces" part, I have an idea on how to do that without adding any new APIs (at least the namespaces part).

Everything is now done for this.

Reopening per Universal_Omega

Backups are done.

To provide an update on backups, public wikibackups are currently underway. Private backups will be done after but take little time. I can say almost certainly that all this will be done by the 21st, given that there's still 3 days left.

The RfF has now been closed and we will therefore be proceeding by adding the option of having five pre-defined tags in addition to the current categories system.

While not wanting to pre-empt the discussion at https://meta.miraheze.org/wiki/Community_noticeboard#Request_for_Feedback:_Categories_and_the_tagging_system it seems quite clear that there is wide support so far from the community to both keep the current category system but also to add a new 'tag' system. While obviously work shouldn't start before the RfF is completed, after a discussion with @Universal_Omega I think it would be best to do this in three stages (originally I thought of two but @Agent_Isai suggested #3). The rationale is that between Stage 1 and 2 wikis can start getting used to the new system and tagging their wikis and Stage 2 wouldn't be very useful at the beginning of the process in any case.

This extension has been moved to Wikimedia Phabricator, is marked as maintained (now maintained by Wikimedia folks, as was kindly offered here once it was posted about), and is now marked compatible with 1.39+ on its extension page.

@Agent_Isai Status?

Assigning to Agent for community consultation. I would recommend having two main options for implementation: either we keep one main category and then tags or we just have tags

Btw, https://phabricator.wikimedia.org/T295830 indicates that GrowthExperiments shows errors if Suggested edits feature is enabled without CirrusSearch installed, so I guess it should also be disabled.

I fixed the sitenotice, it was a simple fix, but php error messages aren't very helpful at identifying the cause.

Sitenotice fixed and deployed thanks to @Void.

We could also just revert the problematic change, but I would first want to give UO a chance.

Discord, status page, and Twitter notification done. I see you tried to do a sitenotice but there was some change in the code used for sitenotices which caused a deploy failure so I'll see if @Universal_Omega has any idea on how to fix this though I'll note that he's currently away so if this cannot be resolved within a few hours, I'll deploy a CentralNotice instead.

@Agent_Isai Can this be announced for tomorrow 2000-2030 please?

In T9195#195130, @John wrote:

This feels like am infinitely defined task - where does the scope end? What's the end goal? I think this should be split up into tasks for each part so they can be tracked, fleshed out and opinions can be sought in a more defined manner.

This feels like am infinitely defined task - where does the scope end? What's the end goal? I think this should be split up into tasks for each part so they can be tracked, fleshed out and opinions can be sought in a more defined manner.

I think I fixed this now. Please re-open if not.

Sorry for necro this task but seems to happened on custom domain: https://houkai2.cyou/
Tested clearing cache and cookie, used Edge and Chrome.