Thanks for working on this, John! I like that they are aspirational goals, being nice to each other shouldn't be that hard.
There are always going to be questions "what exactly is now allowed", but its impossible to enumerate everything. Is it OK to push to somebody else's branch, or change the issue description? Maybe. Surely fixing a typo is OK. But hijacking somebody else's issue to do something that wasn't intended by the author is not OK. Unless you talked about it first, and agreed on it. Then its OK again. Maybe you though the change was welcome, but it turns out it wasn't. Just be nice and reset the branch to the previous state, no harm done. On Wednesday, February 28, 2024 at 10:24:29 PM UTC+1 John H Palmieri wrote: > 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/c4d11498-88c5-4306-8216-e7776c3eff30n%40googlegroups.com.
