As I have explained to the current, semi-anonymous sage-abuse committee in private communication:
The framing of the dysfunction in the affected PRs https://github.com/sagemath/sage/pulls?q=is%3Aopen+is%3Apr+label%3Adisputed as mere "disputes" or "controversies" is misguided and harmful. We do not have a problem of project governance. We have a problem of persistent, aggressive, escalating Code of Conduct violations from a very small number of developers. (Key example with pointers to other examples: https://github.com/sagemath/sage/pull/36726; Trigger Warning: abusive language). And we have the problem of a lack of enforcement of the Code of Conduct. Easy to read overview on best practices: https://opensource.guide/code-of-conduct/ One key quote: - "A code of conduct that isn’t (or can’t be) enforced is worse than no code of conduct at all: it sends the message that the values in the code of conduct aren’t actually important or respected in your community." So I think we should start with electing a new sage-abuse committee that is willing to publicly affirm and enforce the Code of Conduct. I would suggest that nominations (including self-nominations) be sent to this list by Jan 24. The new committee should work with the community to clarify the Code of Conduct and spell out its procedures and the range of sanctions that it will conisder (see https://github.com/sagemath/sage/pull/36844). Matthias On Wednesday, January 10, 2024 at 6:50:10 AM UTC-8 William Stein wrote: > Dear Sage Developers, > > 1. There are over 20 pull requests labeled as "disputed" [1]. To > resolve these pull requests, we will be appointing an editor with no > direct involvement in the pull request to make a judgement call on > that particular pull request. We will then fully support the > decision of this editor. If you have the time to be the (possibly > anonymous) editor for a disputed pull request, please email us > (wst...@gmail.com, vbrau...@gmail.com) and we'll add your name to > our list. > > 2. There are numerous recent reports of violations of the code of > conduct to the sage-abuse mailing list. The code of conduct should > not be used as a tool in case you don't agree with somebody else. For > now, the main act of censure that the sage-abuse committee will be > taking going forward will be to delete comments (on github and mailing > lists) that violate the code of conduct. > > We do not have much time to devote to Sage development. However, we > both very much want things to move forward in a friendly and > encouraging way, and we would greatly appreciate it if the community > of Sage developers will support the above plan to move things forward > and ensure a positive experience for everyone participating in Sage > development. > > Best regards, > > Volker Braun and William Stein > > [1] > https://github.com/sagemath/sage/pulls?q=is%3Aopen+is%3Apr+label%3Adisputed > > -- > William (http://wstein.org) > -- 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/dc2fe40c-5ae7-4554-9e29-a71aa5841b92n%40googlegroups.com.
