-
-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onboarding retext-language-server #57
Comments
LGTM! 👍 |
I'm @aecepoglu and I am offering to contribute retext-language-server to the retextJS organization :) |
Agreed. I also like the idea of a language server engine :) |
Enough time has passed (72 hours) and there are no objections, so @ChristianMurphy and @aecepoglu, feel free to continue with the next steps (4 through 6) and close this. Let me know if I can help. |
Understood. I will handle the rest. |
Friendly ping, what's the status of this? |
Friendly response, I have forgotten about it. Whatever needs to be done to transfer ownership, I'm ready to do it though. |
@wooorm regarding
the link appears to be dead now, I'm not seeing a governance grant page in https://github.com/unifiedjs/governance or https://github.com/unifiedjs/collective, do you happen to know where this documentation moved to? |
|
Based on unifiedjs/unified-language-server#13 I think every CLI based on Since retext doesn’t have a CLI, I don’t think retext should have a language server at this time either. However, it makes perfect sense to me to provide both. |
Closing this for now folks, it’s been a while. Things can also be maintained fine outside of the retextjs org! |
Continuation of https://spectrum.chat/?t=16557712-7029-4718-a2bc-38453fdfb928 and https://github.com/unifiedjs/governance/issues/11
@aecepoglu is offering to contribute
retext-language-server
.https://github.com/unifiedjs/governance/blob/master/governance-grant.md
I think it could be a good fit for the organization, and a good starting point for additional language servers for other
unified
projects.Thoughts @retextjs/core?
The text was updated successfully, but these errors were encountered: