On 17/01/2008, Simetrical Simetrical+wikilist@gmail.com wrote:
On 1/17/08, Thomas Dalton thomas.dalton@gmail.com wrote:
Oversight is used in cases where information needs to be removed from sight, including the sight of admins, deleting revisions doesn't achieve that. That's why we have oversight.
Well, yes. That doesn't have much of anything to do with the question of admin deletion, which is what this entire thread is about. They're different privileges.
That was my point. You were the one suggesting they could be merged:
"Oversight is not in the core software, to start with. This is. Your question could be rephrased: why doesn't oversight use the built-in deletion interface? Maybe sometime it will, once there *is* a built-in deletion interface for single revisions. Probably it would be nicer, once rev_deleted is in, to just have a checkbox on the "delete revision" page for those with the appropriate privileges.
Essentially, you're asking about interface/naming details. It's the same feature either way."
Of course, that's why we like all actions to be reversible. Deciding who can do what isn't really for us to do - it should be a setting in LocalSettings.php.
Of course it's for you to do, more or less, within Foundation mandate. Projects get to request changes to their settings in LocalSettings.php (within reason -- asking for all sysops to get oversight or checkuser isn't going to fly).
I meant "us" as in "the people on wikitech-l". It's important not to forget non-wikimedia wikis that use Mediawiki as well - they're needs are often very different in matters of security.