[doc] enable wiki

[Freed-Wu]

Enable wiki: https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis and https://docs.github.com/en/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis

It allows user to add their projects based to pygls to the wiki easier than changing https://github.com/openlawlibrary/pygls/blob/master/Implementations.md.

[tombh]

I'm personally not a fan of Github Wikis, I find they too often go out of date. But I'm open to it nevertheless.

I actually have thought a few times that the community implementations list should be in the README (albeit right at the bottom). It's a great selling point for people to see as soon land on our "homepage".

Do you have an implementation you'd like to add?

[Freed-Wu]

• autoconf-language-server: GNU autoconf
• bitbake-language-server: openembedded's bitbake
• pkgbuild-language-server: ArchLinux/Windows Msys2's PKGBUILD
• portage-language-server: Gentoo portage's ebuild
• requirements-language-server: python pip's requirements.txt
• sublime-syntax-language-server: sublime text/bat's sublime-syntax
• termux-language-server: Android termux's build.sh

[Freed-Wu]

Because there are too many language servers which need to be added, add them is very frequent, so I support to enable wiki to make it easier 😄

[Freed-Wu]

Or provide an organization like sphinx-contrib to collect all language servers based on pygls? @tombh

[tombh]

OMG I love your servers!! They're such great uses of Pygls. Pygls isn't just for big serious language servers, it's also hopefully designed in such a way that just like you've demonstrated you can use to make smaller, more focussed language servers.

I personally think yours (especially yours!) and our existing list should all be on the README. Not only do they demonstrate Pygls' popularity, but they're documental in that they document intended usage of the library. We don't have to have the gnarly table like we have in https://github.com/openlawlibrary/pygls/blob/master/Implementations.md, we can just make a list like you have above.

[Freed-Wu]

I project to create more language servers. Can any organization like sphinx-contrib for sphinx extensions, zsh-user for zsh plugins be provided to contain them? It can make more people to find them easier.

[tombh]

I'd never thought of this. And so thinking about it for the first time, and knowing that at least you want to contribute your servers to a dedicated pygls-contrib org, makes me think it's a good idea. We're actually in the process of making a pygls-org org, do when we publicise that, I'll bring up the idea formally.

But basically, yeah, I think it's a good idea.

[Freed-Wu]

makes me think it's a good idea. We're actually in the process of making

Great. I wait your publicizing 😄

[Freed-Wu]

Hey, what is the progress of pygls organization? I am creating a language server to display the translated result of the word of current cursor and complete the words in translate history 😄

[tombh]

Awesome!

I think it'll be a month at the soonest before we get that Pygls org setup.

[Freed-Wu]

it'll be a month

New month is coming 😄 Any progress about it?

[tombh]

You're right, we're still talking about this, sorry 😬

[Freed-Wu]

New month is coming 😄 Can I know what is the obstruct? Is it that the name of organization is hard to determine? Or should the organization be in github or gitlab? Or how to manage the organization? I think there are many organizations can be referred like gnu-octave or sphinx-contrib.

[tombh]

It's more to do with how much responsibility we want to take for the code contained in such an org. Are we prepared to formally approve of the code as if it were our own. If people trust Pygls then should they equally trust the pygls-contrib org?