In some sense, this is a recreation of #399 (which was closed). But, probably, this is - the right place to discuss the project maintainership, instead of the sympy's maillists (where I can't reply, while your project is an important dependency for me).
@fredrik-johansson , while I strongly appreciate your efforts to find new maintainers in the sympy community - moving your project to the sympy github group umbrella will mean, that you block me from the mpmath development entirely. Perhaps, I will be not alone. Do I did something wrong or disrespectful for you or your projects? (BTW, perhaps from the Diofant & me - you got not too less merged pull requests then from SymPy devs ;))
I hope, this issue may be solved without sharing the toxic CoC (Contributor Covenant) policy, which was
adopted by the sympy folks. For example, you can create a separate organization just for this project (e.g. mpmath),
transfer the project and invite some contributors (e.g. those who will come from your sympy maillist thead); you call
this - a second choice. (I think, you can even add an entirely some group of developers, e.g. sympy.) But you - will be the community leader and you - will decide on the project policy matters. I believe - this will be an easy task; I don't remember that you block anyone on wipe out issues and/or comments.
PS: Maybe it's even worthless to transfer the project - just invite someone to help with this repo.
In some sense, this is a recreation of #399 (which was closed). But, probably, this is - the right place to discuss the project maintainership, instead of the sympy's maillists (where I can't reply, while your project is an important dependency for me).
@fredrik-johansson , while I strongly appreciate your efforts to find new maintainers in the sympy community - moving your project to the sympy github group umbrella will mean, that you block me from the mpmath development entirely. Perhaps, I will be not alone. Do I did something wrong or disrespectful for you or your projects? (BTW, perhaps from the Diofant & me - you got not too less merged pull requests then from SymPy devs ;))
I hope, this issue may be solved without sharing the toxic CoC (Contributor Covenant) policy, which was
adopted by the sympy folks. For example, you can create a separate organization just for this project (e.g. mpmath),
transfer the project and invite some contributors (e.g. those who will come from your sympy maillist thead); you call
this - a second choice. (I think, you can even add an entirely some group of developers, e.g. sympy.) But you - will be the community leader and you - will decide on the project policy matters. I believe - this will be an easy task; I don't remember that you block anyone on wipe out issues and/or comments.
PS: Maybe it's even worthless to transfer the project - just invite someone to help with this repo.