<sladen> sinzui: so to confirm. During a rename, the requestee is not explicitly asked if a redirect is required. Because few requestees explicitly ask for a redirect, the common-case is not to provide one; and therefore the common-case is set as the default?
<sinzui> The common case is someone is squating on a name or the name is given to a project group!
<sladen> sinzui: sounds like two separate use-cases. (a) Projects changing name. (b) Tackling squatters/vandalism. ; the difference being whether the $old_name is cause of the admin actions, or whether $new_name is the initiator
<sinzui> It's the same screen
<sladen> so the problem is one of overloading. A low-impact action performed frequently is masking a high-impact action performed infrequently (Quantity masking Quality)
Rationale (snipped for length):
<sladen> sinzui: so to confirm. During a rename, the requestee is not explicitly asked if a redirect is required. Because few requestees explicitly ask for a redirect, the common-case is not to provide one; and therefore the common-case is set as the default? vandalism. ; the difference being whether the $old_name is cause of the admin actions, or whether $new_name is the initiator
<sinzui> The common case is someone is squating on a name or the name is given to a project group!
<sladen> sinzui: sounds like two separate use-cases. (a) Projects changing name. (b) Tackling squatters/
<sinzui> It's the same screen
<sladen> so the problem is one of overloading. A low-impact action performed frequently is masking a high-impact action performed infrequently (Quantity masking Quality)