Since a redirect is just a peiece of article text it would be hard to add permissions to it and i don't think that its goes with our openess policies

Output of MWBOT Bot
<mwbot> Wikis are designed for openness, to be readable and editable by all. If you want a forum, a blog, a web authoring toolkit or corporate content management system, perhaps >don't use wiki software. There is a nice overview of free tools available at http://www.opensourcecms.com/ including the possibility to try each system. For ways to restrict access >in MediaWiki, see !access.

catlow wrote:

This is actually *pro*-openness, since it would enable most edits in the namespace to still be permitted, while otherwise it might prove necessary to protect the whole namespace to close the vulnerability to redirect vandalism.

PhiLiP.NPC wrote:

When a category redirect was changed, the redirect target won't be changed automatically. So don't be worried. This just like when a template changed its category, the categories of articles which transcluded the template won't be changed automatically. People need to refresh those articles or wait for system refreshing.

(In reply to comment #2)

This is actually *pro*-openness, since it would enable most edits in the
namespace to still be permitted, while otherwise it might prove necessary to
protect the whole namespace to close the vulnerability to redirect vandalism.

Stop exaggerating. Anytime you restrict an action to a subset of a group, it's being more restrictive, not open.

I can't see any huge purpose in this, nor do we have the right code in place to allow only editing certain text for certain groups (related bugs on this?)

ipatrol6010 wrote:

We do have the $wgProtectedNamespaces right, but I don't see a point. Most vandalism reversion is done to quickly for watchlists to be of use, most is reverted by bots and semi-automated programs. I really dobut the need to make a shell change for a piddly little possibility. If someone wants to troll the web looking for evidence the vandals have discovered this change, go ahead. Otherwise, suggestion WONTFIX.

Should've WONTFIX'd this 2 years ago.