Gregory Maxwell wrote:
It's a bit unfortunate.. the feature is too blunt. Now LOTS of templates pages are protected because one of their many including pages are protected. Since a lot of protections are there to dampen content disputes and simplistic vandalism, this is unnecessary.
Should we instead just protect the entire template namespace?
I don't quite follow your point here. Cascading protection is an *optional* feature when protecting a page which as far as I know has so far only been applied to the Main Page. Since all templates used on the Main Page would have been protected anyway, I don't see how the number of protected template pages has increased. Virtually all full and semi-protections will continue to affect only the page to which they are applied.
-Gurch