Skip to main content

Timeline for Questions about code translation

Current License: CC BY-SA 3.0

9 events
when toggle format what by license comment
Aug 7, 2014 at 7:58 comment added James Khoury I have posted my best explaination. Please disagree with me.
Aug 7, 2014 at 7:45 comment added 200_success Mod @JamesKhoury I suggest that you post an answer.
Aug 7, 2014 at 7:44 comment added James Khoury I'm disagreeing because you're advocating for NOT using custom close reasons as they can confuse. I'm advocating for better custom close reasons instead because a user may not understand how the rules apply to their question. (running on the assumption people actually read them and want to post within the guidelines)
Aug 7, 2014 at 7:40 comment added 200_success Mod @JamesKhoury Each voter can only choose one close reason — either a standard or a custom one. Multiple close reasons would be posted only if the users chose different reasons.
Aug 7, 2014 at 7:38 comment added James Khoury Correct me if I am wrong but both the Custom and the generic close reasons show don't they? So therefore the user asking the question can see a general rule and a specific explanation. This I believe is the correct way to do it unless it it blindingly obvious.
Aug 7, 2014 at 7:12 comment added 200_success Mod @JamesKhoury But closing a question with a custom reason causes the reason to be posted as a comment as a side-effect. Custom close reasons have the potential to enable users to make up the ad hoc closure decisions. (Example)
Aug 7, 2014 at 6:55 comment added James Khoury I'd challenge all of us to put great worded comments rather than worrying about a user misunderstanding a comment. Comments are comments not close reasons. And explaining how the close reason applies is definitely better than no comment at all.
Aug 3, 2014 at 12:13 vote accept nhgrif
Aug 3, 2014 at 0:17 history answered 200_successMod CC BY-SA 3.0