I do not know the back story here, just another aspiring Rustacean from the Python world and minor-league open source maintainer. This is the first time I have ever seen this happen and it saddens me all around. So, I would like to suggest another possibility of governance for this repo, used by Debian for many years, and recently chosen by the Python community as its post-BDFL governance method as well, which can take the pressure off of any single maintainer: Ranked Choice voting, aka the Condorcet method. With it, decisions can be made in an uncontroversial and graceful manner by N maintainers.
I do not know the back story here, just another aspiring Rustacean from the Python world and minor-league open source maintainer. This is the first time I have ever seen this happen and it saddens me all around. So, I would like to suggest another possibility of governance for this repo, used by Debian for many years, and recently chosen by the Python community as its post-BDFL governance method as well, which can take the pressure off of any single maintainer: Ranked Choice voting, aka the Condorcet method. With it, decisions can be made in an uncontroversial and graceful manner by
N
maintainers.https://www.seehuhn.de/pages/vote.html