Plan for plugins moving forward

Hello, thanks for starting this community-driven fork 🙏🏻

I noticed that @andfoy has been creating issues in the repositories for different plugins but I wonder if a different approach would be benefitial.

I was thinking the newly formed python-lsp organisation would be a good place to gather these plugins so they’re not only easier to find but can benefit from the shared experience of other plugin and pylsp contributors. These plugins could also be (re)published to PyPI with proper namespacing and maybe a classifier so they’re easier to find.

@andfoy issues are certainly a step in the right direction, but frankly most of the plugins look quite abandoned and some of them already have forks that have been published independently (pyls-mypy for example was forked into mypy-ls), and I don’t have high hopes they will be addressed soon, so, the only solution that comes to mind is forking, with all due respect to the authors of the plugins.

I hope this doesn’t come across as confrontational, I genuinely would like to see an ecosystem of well-maintained plugins for pylsp.

[haplo]

pyls-isort now has a compatible release in PyPI. 🚀

[andfoy]

For those interested, there is a new release available of python-lsp-black! The fork is available at https://github.com/python-lsp/python-lsp-black