This bug is invalid, as far as I'm concerned. It's still unclear what's going to happen to the wiki at wiki.toolserver.org, but I can't fathom a reason that we would need to protect outdated/historical pages such as the Toolserver account approval policy. And protecting individual pages on a wiki (or not) is outside the scope of Bugzilla.

(In reply to comment #1)

This bug is invalid, as far as I'm concerned. It's still unclear what's going
to happen to the wiki at wiki.toolserver.org, but I can't fathom a reason
that
we would need to protect outdated/historical pages such as the Toolserver
account approval policy. And protecting individual pages on a wiki (or not)
is
outside the scope of Bugzilla.

Regarding the first aspect, I didn't look for a reason, but the pages are protected currently, and I see no reason not to transfer that setting that has been enabled for years; if we found some time in the future that this was a mistake or just unnecessary, it would take a couple of clicks to unprotect them.

Regarding the second aspect, this bug is "part" of the mother bug 60220. It's a small, actionable item with clear dependencies so that it is not missed in a gush of text and comments. Its topic isn't protecting pages on a wiki, but preserving the protection status as part of the migration.