Skip to main content
Commonmark migration
Source Link

##Disagree.

Disagree.

Hence -1 vote.

(This is based on my experience of reviewing edits on SO.)

The resistance for rejection of edits (I've rejected plenty, both before the reason was added and since) is not much friction. There is more effort in making the choice of whether to accept or reject. If a reviewer isn't putting the effort in to the review then all their reviews are invalid, whatever the default result.

Therefore I see no need to "balance the paths".

Additional On further thought: the reason for the reject reasons is to tell the editor why it was rejected, so they can avoid such edits in the future. With an accepted edit the feedback is already there: accepted.

The reasons given in this question would make more sense for the editor to provide to the reviewers. But the reviewer would then need to additionally agree or disagree with the reason. Then we would need a mechanism to handle the case where the reviewer agrees with the edit but not with the reason for the edit. Finally with the edit privilege you don't have any of this (an edit roll-back doesn't give a reason), so it would be even more inconsistent.

Summary: the reject reason is to inform the edit of why it is was rejected. This is useful in helping that editor suggest better edits. An accept reason wouldn't.

##Disagree.

Hence -1 vote.

(This is based on my experience of reviewing edits on SO.)

The resistance for rejection of edits (I've rejected plenty, both before the reason was added and since) is not much friction. There is more effort in making the choice of whether to accept or reject. If a reviewer isn't putting the effort in to the review then all their reviews are invalid, whatever the default result.

Therefore I see no need to "balance the paths".

Additional On further thought: the reason for the reject reasons is to tell the editor why it was rejected, so they can avoid such edits in the future. With an accepted edit the feedback is already there: accepted.

The reasons given in this question would make more sense for the editor to provide to the reviewers. But the reviewer would then need to additionally agree or disagree with the reason. Then we would need a mechanism to handle the case where the reviewer agrees with the edit but not with the reason for the edit. Finally with the edit privilege you don't have any of this (an edit roll-back doesn't give a reason), so it would be even more inconsistent.

Summary: the reject reason is to inform the edit of why it is was rejected. This is useful in helping that editor suggest better edits. An accept reason wouldn't.

Disagree.

Hence -1 vote.

(This is based on my experience of reviewing edits on SO.)

The resistance for rejection of edits (I've rejected plenty, both before the reason was added and since) is not much friction. There is more effort in making the choice of whether to accept or reject. If a reviewer isn't putting the effort in to the review then all their reviews are invalid, whatever the default result.

Therefore I see no need to "balance the paths".

Additional On further thought: the reason for the reject reasons is to tell the editor why it was rejected, so they can avoid such edits in the future. With an accepted edit the feedback is already there: accepted.

The reasons given in this question would make more sense for the editor to provide to the reviewers. But the reviewer would then need to additionally agree or disagree with the reason. Then we would need a mechanism to handle the case where the reviewer agrees with the edit but not with the reason for the edit. Finally with the edit privilege you don't have any of this (an edit roll-back doesn't give a reason), so it would be even more inconsistent.

Summary: the reject reason is to inform the edit of why it is was rejected. This is useful in helping that editor suggest better edits. An accept reason wouldn't.

Expand
Source Link
Richard
  • 9.1k
  • 15
  • 5

##Disagree.

Hence -1 vote.

(This is based on my experience of reviewing edits on SO.)

The resistance for rejection of edits (I've rejected plenty, both before the reason was added and since) is not much friction. There is more effort in making the choice of whether to accept or reject. If a reviewer isn't putting the effort in to the review then all their reviews are invalid, whatever the default result.

Therefore I see no need to "balance the paths".

Additional On further thought: the reason for the reject reasons is to tell the editor why it was rejected, so they can avoid such edits in the future. With an accepted edit the feedback is already there: accepted.

The reasons given in this question would make more sense for the editor to provide to the reviewers. But the reviewer would then need to additionally agree or disagree with the reason. Then we would need a mechanism to handle the case where the reviewer agrees with the edit but not with the reason for the edit. Finally with the edit privilege you don't have any of this (an edit roll-back doesn't give a reason), so it would be even more inconsistent.

Summary: the reject reason is to inform the edit of why it is was rejected. This is useful in helping that editor suggest better edits. An accept reason wouldn't.

##Disagree.

Hence -1 vote.

(This is based on my experience of reviewing edits on SO.)

The resistance for rejection of edits (I've rejected plenty, both before the reason was added and since) is not much friction. There is more effort in making the choice of whether to accept or reject. If a reviewer isn't putting the effort in to the review then all their reviews are invalid, whatever the default result.

Therefore I see no need to "balance the paths".

##Disagree.

Hence -1 vote.

(This is based on my experience of reviewing edits on SO.)

The resistance for rejection of edits (I've rejected plenty, both before the reason was added and since) is not much friction. There is more effort in making the choice of whether to accept or reject. If a reviewer isn't putting the effort in to the review then all their reviews are invalid, whatever the default result.

Therefore I see no need to "balance the paths".

Additional On further thought: the reason for the reject reasons is to tell the editor why it was rejected, so they can avoid such edits in the future. With an accepted edit the feedback is already there: accepted.

The reasons given in this question would make more sense for the editor to provide to the reviewers. But the reviewer would then need to additionally agree or disagree with the reason. Then we would need a mechanism to handle the case where the reviewer agrees with the edit but not with the reason for the edit. Finally with the edit privilege you don't have any of this (an edit roll-back doesn't give a reason), so it would be even more inconsistent.

Summary: the reject reason is to inform the edit of why it is was rejected. This is useful in helping that editor suggest better edits. An accept reason wouldn't.

Source Link
Richard
  • 9.1k
  • 15
  • 5

##Disagree.

Hence -1 vote.

(This is based on my experience of reviewing edits on SO.)

The resistance for rejection of edits (I've rejected plenty, both before the reason was added and since) is not much friction. There is more effort in making the choice of whether to accept or reject. If a reviewer isn't putting the effort in to the review then all their reviews are invalid, whatever the default result.

Therefore I see no need to "balance the paths".