Docformatter needs a maintainer

[robmoss2k]

This is a similar problem to the isort one. Questions were first raised on Discord on January 17th. So far, there have been no useful replies apart from a note on February 14th that @weibullguy should have some time to work on docformatter a week later. 11 weeks on and there's no traction.

Per my comment on isort, something is fundamentally broken here. We all have real lives and jobs, but these tools are important for thousands of Python projects. Right now, workflows are broken. If a new docformatter release is not made quickly, people will stop using it, and a useful tool will be lost.

I am happy to take over and make a new release. I will likely do a worse job than the official maintainer were they able to make a release, but in light of the fact that they cannot, a new release is important.

A wider discussion on PyCQA's maintainer rules should happen. I will give this some thought over the next few days and raise a separate issue. This issue is just about the process we must follow to revive docformatter.

[DanielNoord]

I can cut a release if this is desired but last time there was a lot of push back on doing this.

In the meantime I can only recommend to check out my own "fork" in https://github.com/DanielNoord/pydocstringformatter, which we built for pylint a couple of years ago when docformatter didn't fit our needs anymore. It should be compatible with most setups.

I'd be happy to remove this recommendation to not "compete" with docformatter as soon as we do cut a release :)

[sigmavirus24]

I think that competitor is more than fair as often times there are and should be forks as necessary. No need to remove it.

@weibullguy has addressed this repeatedly that they are working to make time to create a new release. They have not abandoned the project as far as I understand, they're just low on time. As such I would defer to them to invite someone to help

[robmoss2k]

@weibullguy - as mentioned, happy to help.