Dear colleagues, I am working on some changes to Sage's Code of Conduct, and I am asking for comments. Once the draft has stabilized, then we will hold a vote on sage-devel to approve (or not) the changes. Please visit https://github.com/sagemath/sage/pull/37501 to see the proposal.
The current Code of Conduct was approved by a vote in sage-devel almost 10 years ago. My intention is not to alter the core principles in the Code of Conduct, but instead to add more details: for example, how should you report a possible violation, what are possible consequences if the Sage Code of Conduct Committee (what has until now been called the Sage Abuse Committee) finds that a violation occurred, how to amend the document, etc. The changes are based in large part on similar documents from SciPy and NumFOCUS: we are not reinventing the wheel. As such, I hope that the proposed changes are (a) not controversial, and (b) a clear improvement. I could certainly be wrong about either of these, but I will make this suggestion: if you agree with me about (a) and (b) and you also want to propose changes that are potentially more controversial, then I would ask that you make that proposal separately so that the Sage community can vote on it separately, and the changes can be merged independently of each other. Please take a look and leave comments on the PR. -- John -- 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/aa75eee6-a2b6-4f0d-8992-4995ed9f4310n%40googlegroups.com.
