-
Notifications
You must be signed in to change notification settings - Fork 167
looking for maintainers #141
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
Comments
@akosyakov I'd be willing to maintain until Do you have a process for hand off? I'm also willing to chat privately to answer any questions you might have :) |
I've been given maintainership rights, so time to close this 👍 |
Awesome @DonnieWest 🙌 Thank you for willing to continue supporting this repo. |
If this has moved to VS Code, what are all the other editors supposed to do? :-\ |
@DonnieWest would you like some help with this server? I could help handling some PRs at least. I know that Microsoft is supposed to come up with official implementation sooner or later but I think that is not a reason to just stop improving this one. At least until the official one is out and proven to work better in every way.) (I'm one of the maintainers of the Sublime Text LSP) |
@rchl hey, thanks for volunteering! I'd super appreciate some help If it's alright with you, I'll look into adding you at the same permission level that I have |
@DonnieWest sounds good |
@DonnieWest I don't have other means of contacting you so doing it here. Would you (and original maintainers) be fine with also giving me npm publishing privileges? We have some nice fixes lined up for release and it would be good to get those and future fixes out more often. |
Theia moved to use VS Code extension directly to keep pace with VS Code. Unfortunately it means that Theia commiters cannot dedicate their time to maintain this project anymore.
Who will be willing to step up and keep maintaining this project? You will be granted admin rights on this repo and invited as a collaborator on npmjs to allow package publishing.
The text was updated successfully, but these errors were encountered: