Yeah, I also thought of namespaceDupes. Please do let me know if there's anything left to fix on-wiki.

@taavi Hii! Perhaps you can now review the patch again since the community consensus is established.

In T344306#9095601, @Bugreporter wrote:

Using an existing right as protection level is not recommended. Srwiki currently has patrol and rollback protection level, but they will be phased out: see T230103: Systematize wgRestrictionLevels.

Okie, I'll keep that in mind when modifying the patch! Thanks!

The Draft namespace seems obvious but we don't like to enable VE in the namespaces that are used for discussions, as VE does not provide suitable tools for editing threaded discussions, and that is better left to DiscussionTools. The Project: (aka Wikipedia:) namespace appears to be used for discussions on that wiki, as evidenced by the link provided in the description:

Yeah, I'm aware of that fact, but Wikipedia namespace is also used for policies and guidelines, which are editable content.

In T159711#3077099, @Jdforrester-WMF wrote:

For NS_PROJECT, our advice is that VE isn't a great editing experience on pages that are signed (like village pumps or deletion discussions) and never will be, so we leave it to wikis' communities to decide. Several wikis have opted in, with good results, but I'm nervous.

Per this, I guess we can enable it since the community supported it and there are wikis which opted in.

I strongly believe that Winston will be a great addition to the team! Based on the previous cooperation, I got the impression that he is a very accommodating and reliable contributor. These privileges will help him better manage tasks in the language converter area.

Update: I'll finish purging pages using API sandbox. I think I found a good method.

Thanks, Zabe! However, that didn't really solve my problem. For example, this page is still displayed incorrectly ("Razgovor sa korisnikom" instead of "Razgovor s korisnikom"). Manually purging 71,000 pages is a huge job.

Scheduled for deployment

Scheduled for deployment

Change deployed.

Scheduled for deployment

Change deployed.

Scheduled for deployment

Change deployed.

Patch updated, community notified.

Oh, I didn't know about that limit. I'll update the patch and inform the community, consequently.

The word list is already present here. Not sure if it has to be updated or smth.

Album names (and, in fact, most English-language proper nouns) arе not transcribed even on the Serbian Wikipedia. For example, see this article.

I don't think so, removed

Marking this as invalid since the variants ekavsk and ijekavsk are only defined for sr, per Fomafix.

didn't know the sh code is deprecated... I guess we can then go with the bhs code and the corresponding subcodes (bhs-Cyrl-ekavsk, bhs-Cyrl-ijekavsk, bhs-Latn-ekavsk, and bhs-Latn-ijekavsk? Is that okay?

Same problem on the Gerrit's web interface. Sorry, unable to help.

There are no big differences, but I know some users who would rather use sh-Cyrl-ekavsk instead of sr-Cyrl-ekavsk. Besides, the community supported the introduction of four interface variants.

Sorry for being imprecise. I was thinking of the user interface language.

@Fomafix, I guess you can help out with this considering that you've already initiated the same process for sr-ec and sr-el language codes.