microsoft / microsoft/language-server-protocol
Reconsider having a community space for server and client implementors
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
The only prior discussion I can find is here: https://github.com/microsoft/language-server-protocol/issues/429
I think it would be quite valuable to have an "offical" LSP community space for discussions. There are three big classes of topic which I think would benefit a lot from discussion:
- Issues around the protocol itself. The previously linked issue argues that this should happen on github issues, and I think that's a reasonable choice, but it would be nice to be able to talk more informally also.
- Issues around implementing servers. As a server implementor, I would love to have a place I could go to find other server implementors and discuss issues that arise when writing servers, find out how they dealt with them, etc. At the moment there is no easy way for me to do this. I can reach out to people directly, but it would be quite helpful to lower the barrier, especially for new people trying to implement a server.
- Issues around implementing clients. I have observed quite a lot of discussion on clients about how to implement certain features. Often there are ad-hoc references to other clients (often vscode), but I can't help but think that it would be helpful for these people to also have a place where they can talk to each other and ask questions.
If the feeling is still that protocol issues should be discussed only on github, then I think it would still be very valuable to have a "LSP implementors" community. I'd be happy to set something like that up. But it would really help if it was linked to from the main specification, because otherwise people won't find it and it loses a lot of its value.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the prior discussion in issue #429 and compare its conclusions with this proposal. Define whether an official LSP implementors community space should be created and linked from the main specification; the issue is done when the project has a decided community location and a documented link or a clear decision not to proceed.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100