This message comes from the Code of Conduct Committee, in response to a question from Kwankyu <https://groups.google.com/g/sage-devel/c/N1THlmVDm-w/m/mZY1aEOBCAAJ> (labeled A4 in his message) about the authority to modify a comment by someone else (including PR and issue descriptions).
1. Proposed policy regarding editing comments: of course users can edit their own comments. The Sage Code of Conduct Committee may hide comments if they are found to violate the code of conduct. If part of a comment is problematic but other parts are deemed useful, then the committee may hide the comment and post a new comment, quoting the useful parts. In rare cases, the committee may instead choose to edit the original comment to remove content that is considered too harmful to remain even in hidden form or to remove problematic parts from an otherwise useful message. No one else should edit another person’s comments. 2. Proposed policy regarding editing PR/issue descriptions: anyone with appropriate Github permissions can edit these descriptions, but if the original author objects, then the editor has the responsibility to remove their edits and restore the original content. There are plenty of occasions where people want to add content: fix a typo, fix a dead link, add links to other issues, add context. At least for PRs, the text gets entered into the git log, and so we want the description to be as helpful as possible, and we want the default to be a collaborative environment. Discussion? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/d6f0c927-961c-4aae-8d9f-b83cd89adacan%40googlegroups.com.
