Timeline for What is our site policy on code/command edits?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2017 at 17:17 | comment | added | Jacob Vlijm | ? Well, I believe @Zanna's post expresses all quite well, but yes, let's end this then. | |
| Jan 19, 2017 at 16:02 | comment | added | terdon Mod | @JacobVlijm then I would ask you to kindly stop this discussion and post your own answer if you believe there is a difference in our positions. | |
| Jan 19, 2017 at 15:48 | comment | added | terdon Mod | @JacobVlijm good for you. This question, however, is explicitly asking for site policy and site policy is that anything that can be improved, should be improved. Sure, people can choose to leave a comment or edit, that's up to each user. But policy is that yes, code can be edited. | |
| Jan 19, 2017 at 15:11 | comment | added | Jacob Vlijm | @terdon Now that is a matter of policy and taste. I happen to believe in practice, there is a difference in what is applied already. I can't remember a single occasion of edits on my scripts without getting involved in the process, apart from an occasional inexperienced user. I've had (and edited in) many, many good suggestions though. | |
| Jan 19, 2017 at 14:35 | comment | added | terdon Mod | @JacobVlijm I am not fighting anything at all. I am simply pointing out that there is absolutely no difference between correcting a mistake in grammar and correcting one in code. The same rules and guidelines apply to the entire post irrespective of if it is code, prose, an image or whatever. | |
| Jan 19, 2017 at 14:33 | comment | added | Jacob Vlijm | @terdon We are discussing a policy here. Not what we can do or not. Of course anyone can edit code in any way, even change it 100%. That does not make it bad to be restraint in doing so, and preferably involve the poster to make sure to always respect the original author, as the guidelines suggest. I don't understand btw why you are fighting what seems to be the practiced policy among higher rep users anyway. | |
| Jan 19, 2017 at 13:53 | comment | added | terdon Mod | @JacobVlijm no, posting an answer constitutes releasing it. It no longer belongs to you, it is now in the public domain under the CC license. Therefore, you can adapt it. Here. | |
| Jan 19, 2017 at 7:53 | comment | added | Jacob Vlijm | As already mentioned in chat, I don't see how the site's license: Share — copy and redistribute the material in any medium or format Adapt — remix, transform, and build upon the material, is in contradiction with being restraint in editing code on the post. It just means anyone may take the code, use it, change it under certain conditions. It mentionsnothing at all on the policy on editing code on a post. We are then back to discussing an opinion. | |
| Jan 18, 2017 at 10:09 | comment | added | Jacob Vlijm | Just a side note, I know I am sensitive to editing my code, and what I say easily explained in that context, but that is really (and honestly) not my point. | |
| Jan 18, 2017 at 10:04 | comment | added | terdon Mod | @JacobVlijm improvements are always good. Whether they improve code or prose is completely irrelevant. I get that you object to this (you have very often made that clear in the past) and that's fine, you're entitled to your own opinion. Nevertheless, there is nothing special about code. it's still text and it can still be edited (as long as you improve it and don't introduce errors). If you don't like it, roll it back. | |
| Jan 18, 2017 at 10:01 | comment | added | Jacob Vlijm | Sure, but my point is, driving a 40 ton truck in the center of Amsterdam requires more responsibility then riding a bike in the forest. In other words; the threshold to edit code should be higher then correcting a grammar error., unless you know code can be harmful. | |
| Jan 18, 2017 at 9:54 | comment | added | terdon Mod | @JacobVlijm yes, that's why edits can be rolled back. That is not, however, any reason to stop editing. Obviously, bad edits can happen and those should be corrected. Nobody said the opposite. | |
| Jan 18, 2017 at 9:31 | comment | added | Jacob Vlijm | I don't think this is in any way at variance with the policy of the SE network. ^ | |
| Jan 18, 2017 at 9:30 | comment | added | Jacob Vlijm | I don't think it's a secret that I feel more attached to what I write than some others :). That isn't my argument here however. Although in theory there is no difference in editing text or code, in practice there is. Like I mentioned before, I've had edits by excellent users, with a (much) bigger over all knowledge than I, make edits to my code which turned it into a non-working solution. I am sure they knew what they did, but simply made a mistake. People do. You do, I do. That's why I plea for a higher threshold to edit code than for editing out textual explanation or grammar. | |
| Jan 18, 2017 at 9:24 | comment | added | muru | With one important qualification - the core nature of the answer mustn't be changed. I once rolled back an edit to an accepted answer which replaced it entirely with another answer to the same question! | |
| Jan 18, 2017 at 9:01 | history | answered | terdonMod | CC BY-SA 3.0 |