WANTED: More maintainers 🔧🙋‍♀️🙋🏾‍♂️🙋🏼

### 🤔 What's the problem you've observed?

This project, and its supporting projects the [language-service](https://github.com/cucumber/language-service), [cucumber-language-server](https://github.com/cucumber/language-server) and [gherkin-utils](https://github.com/cucumber/gherkin-utils/) need a lot of love and attention. We currently have 25+ open issues across all three projects combined. The environment around VS Code is also quite dynamic and we've seen things break in non-obvious ways (https://github.com/cucumber/vscode/issues/155, https://github.com/cucumber/vscode/issues/164, https://github.com/cucumber/language-service/issues/174). And so far we are very happy with @xeger tackling some of these issues. But this is too much work for one person.

So we really need more people who also use the tool to help us look after it.

### ✨ Do you have a proposal for making it better?

@kieran-ryan you've been making stellar contributions recently. Would you be interested in helping keep this plugin and the surrounding projects up to date?

In return, you will get the 🎉 and ❤️ of the Cucumber community, and a great new way to spend your spare time. :wink:

### 📚 Any additional context?

Publishing to the VSCode Marketplace just got fixed. So the project should be ready to go. :smile:

Review the open issues in cucumber/vscode and the linked language-service, cucumber-language-server, and gherkin-utils projects, starting with the referenced issues 155 and 164 and language-service issue 174. The issue names no single code change or test; done would mean agreeing to maintain the plugin and surrounding projects and keep them up to date.

Written by the indexing model from the issue text.