iridisi wrote:

I ask not yet handle this request, as long as the discussion moot and inconclusive. The debate on the introduction of the new namespace has not yet been completed.

I believe this request should be withheld until a solid consensus is achieved in Russian community. Marking it as LATER for now.

dendil wrote:

This discussion have TWO totals approved a Arbcom namespace now. Request reopened.

(In reply to comment #2)

I believe this request should be withheld until a solid consensus is achieved
in Russian community. Marking it as LATER for now.

I believe all issues with local consensus are resolved now, and there are no reasons to hold this ticket anymore.

(In reply to comment #0)

• create = autoconfirmed, edit = autoconfirmed, move = autoconfirmed in main,

create = all, edit = all, move = all in talk.

What are you wanting to do here?

(In reply to comment #5)

(In reply to comment #0)

• create = autoconfirmed, edit = autoconfirmed, move = autoconfirmed in main,

create = all, edit = all, move = all in talk.

What are you wanting to do here?

We want to set up full semi-protection on Arbcom namespace. We already use title blacklist for that, but that is sort of hacky.

(In reply to comment #6)

(In reply to comment #5)

(In reply to comment #0)

• create = autoconfirmed, edit = autoconfirmed, move = autoconfirmed in main,

create = all, edit = all, move = all in talk.

What are you wanting to do here?

We want to set up full semi-protection on Arbcom namespace. We already use
title blacklist for that, but that is sort of hacky.

Or, technically speaking, it should be something like

$wgNamespaceProtection[ns id] = array( 'autoconfirmed' )

(in InitialiseSettings format, of course)

All done

(In reply to comment #8)

All done

I'm sorry for not making it clear, but only the namespace itself should be protected; the talk space should not.

Please remove protection from it. Thanks.

Fixed