PROJECT TO BE ARCHIVED

[davidlday]

On June 16, 2018, Adam Voss (@adamvoss), creator of this plugin, created an organization called @languagetool-language-server and added me as co-owner. Adam and I never met, nor had we ever exchanged emails. I had made one small contribution to this project just updating the version of LT to be current since it hadn't been updated in a while. I thought it strange he added me to his org without any conversation, but accepted anyhow, thinking it was a cool effort that would better enable developers to use LanguageTool in their favorite IDE, and to have it behave like their other tools.

On December 12, 2018, I received a brief email from Adam's father letting me know he'd passed away on July 11, 2018.

I've asked the kind folks over at LanguageTool if they'd accept Adam's work on the Language Server implementation as a contribution to their project, and they've tentatively agreed. My current focus is on getting this added to their project as a submodule and eventually archiveing this repo. Until this, I don't plan on directly addressing any open issues, but will consider PRs.

[ruipimentel]

Wow, this is very, very sad to hear.

I wish the best of luck to the project and hope I can be of any help.

Thank you for your time and for the notice, David.

[davidlday]

I've forked the languagetool repo and have started working on integrating languagetool-languageserver into it. Contributions are welcome at languagetool-language-server/languagetool.

[davidlday]

I have a quick update for anyone interested.

I will be archiving this and the other languagetool-language-server projects sometime within the next couple of weeks. There are two possible alternatives:

1. LT_EX, which is a fork of @adamvoss original work by @valentjn and thus is preserving his code and memory, which was the most important thing that kept me hanging on to these projects.
2. LanguageTool Linter, which is a new extension I've authored based on the Atom Linter LanguageTool extension, which I use and have participated in.

I choose to take a different approach to the extension based on my opinions about client and server accountability and LanguageTool's stance on implementing format parses in the server, but having a choice is good for the community, and I'm glad to see Adam's code is being preserved. I won't delete these projects, but I will make an update to their READMEs and then archive them for posterity's sake.

Hopefully Adam's contribution to the Open Source community has had a positive effect on many of you. Peace.

[jcs090218]

@davidlday Hi, I am interested in working on the language server for language tool. Base on your context, would this project be further develop? Thanks!

[davidlday]

@jcs090218 - I don't have the time or the interest to continue working on this, but I'm open to the idea of adding others to the organization to continue the work @adamvoss started. Can you tell me a little more what your vision is for this project?

UPDATED: I saw your email. Would you mind repeating here for others to see as well, particularly about using Emacs? I'll look into how best to add you, probably as a Code Owner. And we'll need to get contributors guidelines updated. Probably a couple of other things I'm not thinking of yet.

[valentjn]

@jcs090218 Maybe as a heads up, in case you don’t know it, there is a fork of languagetool-languageserver that’s actively developed and used (there are clients for VS Code and Sublime Text): valentjn/ltex-ls. You might want to check it out to avoid reinventing the wheel. (Disclaimer: I am the maintainer of ltex-ls.)

[jcs090218]

UPDATED: I saw your email. Would you mind repeating here for others to see as well, particularly about using Emacs?

Sure, I am planning on continue the development of this project since I would need a Language Server up and running for editors other than VSCode. e.g. Emacs, Vim, etc. Having a language server is a lot more valuable and it's the current best solution for cross editors solution.

@jcs090218 Maybe as a heads up, in case you don’t know it, there is a fork of languagetool-languageserver that’s actively developed and used (there are clients for VS Code and Sublime Text): valentjn/ltex-ls. You might want to check it out to avoid reinventing the wheel. (Disclaimer: I am the maintainer of ltex-ls.)

Ah.. Great to know! Your project looks promising yet I would still like to continue the work on this project. I was planning to learn LSP and pick up my Java skill from the past! And I am also looking forward for other contributors like me to join the development too and share the view of this project! :)