# Is it appropriate to prune code blocks by editing out irrelevant Javadoc comments?

I've just did a compulsive edit on this question, essentially removing @author, @version and @since comments, to prune the code block (From 584 lines -> 491). I absolutely forgot that I don't have full edit privileges, and the "Thanks for your edit!" note made me wonder a bit if my edit was appropriate.

My reasoning was that the comments are absolutely unnecessary for a code review, and since OP already had a link to the proper version hosted on GitHub, it wasn't really a big deal. Ordinarily by posting to any Stack Exchange site, you implicitly accept the terms of the CC licence, and it shouldn't really matter.

My edit was accepted, but I think that some people may consider @author comments a bit special and will not appreciate such edits.

What do you think? Are such edits appropriate or frowned upon?

• I'm interested to find out how to community feels about this. For my part, I'll generally approve comment edits, but not code edits. If the author doesn't like that he can always roll back. – Michael K Jan 26 '12 at 16:45
• I was speaking in general :) I feel that most of the time you can assume that if an edit is bad/not useful, someone (the approver, an author, a moderator pulled in by a flag) will roll it back. – Michael K Jan 26 '12 at 16:56
• If it makes the post easier to read and as you said, "prunes" it down a bit then sure I dont see why you shouldn't as long as its in good faith. – DarkMantis Jan 26 '12 at 17:20

• I think that the comments are relevant to the code review Why? – yannis Jan 26 '12 at 18:12
• @yannis On OP's they can be relevant. Comments are fair game for review IMO. @uathor tags - less so. For answers I can see more aggressive editing of such items - not as much for OPs. – Michael K Jan 26 '12 at 18:20