Please link to a comment by the chapter/community consenus that they want this change.

EN.WP.ST47 wrote:

Invalid until the requestor provides a link to community consensus for this proposal. Once you have consensus to make this change, please reopen this bug with a link to that consensus.

Whoops, Forgot to comment on the bug.

User has contacted me and is a member of the SE chapter board, They has also checked with other board members.

Is there really need for a link when a board member asks for this? Or when the chairman does?

EN.WP.ST47 wrote:

Oh. Someone should probably just do this then. I didn't realize that the requestor was a board member.

This cannot be currently done with just MediaWiki

Maybe with the lockdown extension, but it's not a an extension that is reviewed for deploy.

A bug to allow this in core could be created, and put as a blocker against this one

Oh, I did not realize that since it was possible for the Projekt: namespace. Is it something special about that one that made it possible?

(In reply to comment #7)

Oh, I did not realize that since it was possible for the Projekt: namespace. Is
it something special about that one that made it possible?

The projekt namespace is setup in a strange away, and I've no idea how it even works...

Couldn't we just open the wiki up, then wgNamespaceProtection every namespace to their member usergroup and leave user unprotected?

As the result would be exactly what we want, I am totally behind that proposal. Oh, but don't forget to also leave Projekt: unprotected then.

(In reply to comment #9)

Couldn't we just open the wiki up, then wgNamespaceProtection every namespace
to their member usergroup and leave user unprotected?

Yes, this should do the job. Reopening the bug.

• This bug has been marked as a duplicate of bug 39671 ***