We can always move things to a private room if needed, but generally the more discussion that happens here or on Meta - more people can benefit from it. Only if it's something relating to a topic where a moderator has pledged to keep certain things private do we handle things in that manner.
@bmike Ok. Makes sense. I had recently voted to reject some edit suggestions and noticed that on all three (links coming momentarily) @patrix, or you came through and approved them.
As you can see I voted to reject for a variety of reasons. But, should I more loose with my approvals? I appreciate that users are taking the time to edit, but all of them specifically either fit in the rejection criteria, or don't address more then one problem in the Q/A.
Thoughts?
I really try to play by the rules, but, honestly, collaboration is almost more important to me. : )
Rule A - (and there is no order to the rules AFAIK) - don't put signatures, TIA, needless text in posts.
Rule 1 - Don't make edits that are trivial.
I looked at what had happened - a very new user (1 rep) made a post that ended with Thanks.
A new to us user (but veteran user on other SE sited) culled that thanks but needs someone here to green light their change. Yes it would be too trivial to approve if it was picking nits elsewhere - but I wanted the new user to get the experience that others will help edit things and agree that getting rid of the thanks was more important than brushing that new to us user away from minor edits.
If that user keeps doing minor edits - we can / will handle it - but I'd rather people OK honest attempts to help - whether it's in culling needless boilerplate or making substantial improvements.
I'll never fault a user for doing what you did and deny that small an edit. There is a rule to not approve edits that are trivial - and it's only a very few reviewers that care and know to look for exceptions to that rule.
Here's another instance where we ignore the trivial edit rule. When someone drops the f-bomb
1. I was thinking it should be another answer. 2. It may have seemed - at first glance - better if it was an overhaul instead of just appending. 3. The last two paragraphs didn't seem to add at. (but this is kind of a mute point because I do know I could have "improved" it).
If the editor hadn't been anonymous and we had any chance at getting them to answer - we could try that.
But in the end - why ask someone to make a duplicate answer. It's really the same steps as the existing one - just explained a whole lot more carefully
@bassplayer7 Do these changes make the post more appropriate? (or should they be rolled back)
That's another thing to consider. When you approve an edit - anyone can see the edit and roll it back. But if we deny too many changes - they never hit the system and are lost forever.
It's odd - the biggest problem we have with reviewers is that some are too accepting and approve anything and everything.
Yet here I am asking you to approve more. Just keep rejecting the trivial things that have no chance of making things better and you'll be perfect!
@bmike Sure. That makes sense. Some great thoughts. Thanks for the taking the time to explain/clear things up. I was scratching my head a little yesterday when I saw. : )
@bmike This is actually a really good point. Something I hadn't though much about.
I need a small graphical utility, using which I can ssh to a server and see all the files and copy and paste (drag and drop) into my local machine.
I am running Snow Leopard.
I need a small graphical utility, using which I can ssh to a server and see all the files and copy and paste (drag and drop) into my local machine.
I am running Snow Leopard.
