Looking for maintainers

[zxh0]

This project is currently unmaintained, and I’m looking for new maintainers to take over development and review pull requests.

If you are interested in maintaining this VSCode extension, please comment on this issue.

Thank you for supporting the project!

[DrBlury]

Previously:

I'd be happy to become a maintainer or merging and reviewing pull requests.
Also opened a pull request and looking forward to continuing support of this extension

Edit:
Sadly it is impossible to publish new versions of the extension under the original creators user in the marketplace. A deprecation notice has been placed and I am trying to build a more extensive extension. Please be mindful of the transition. It is NOT the same extension. It is a fully new codebase.
I created my own extension that was developed to solve some feature needs that I personally had. I'll continue to extend and maintain
https://github.com/DrBlury/protobuf-vsc-extension if you are interested.
Please report any regressions in the GitHub issues there.

[zxh0]

Hi @DrBlury

Thanks a lot for your interest in maintaining the project, and for already opening a pull request — really appreciate it!

I've added you as a collaborator. Once you accept the invitation, feel free to start reviewing/merging PRs and helping guide the project forward.

Also, thanks for sharing your own extension. Great to see alternative approaches — I’ll definitely take a look.

Let me know if you need any additional permissions or context about the project. Happy to have you onboard!

[DrBlury]

@zxh0 Oops I think I still need permission to set secrets for codecov. If you could set up a codecov organization or add the secret as well, that would be great!

[DrBlury]

@zxh0 we would need to be able to publish new extension versions.
Please either give us access to publish the extension manually or set up a release pipeline. Alternatively we could think about either deprecating the extension in favor of another.

It's up to you!
I did some cleanup and addressed the most important issues but there is still so much more to do to get this back to the glory this extension once had!

[zxh0]

Hi! DrBlury

Thanks a lot for all the work you’ve already put into this extension — I really appreciate the effort and care you’ve contributed.

To be honest, I don’t have the time or energy to continue maintaining this project, including publishing new extension versions.
Given this, I think the best long-term solution would be:

You can freely fork the project and publish your own extension version.
I will archive this repository so that it stays available but clearly marked as unmaintained.

This way you can continue development independently without having to rely on permissions from me.

Thanks again for your support and contributions!

[DrBlury]

@zxh0 I understand. Thank you very much for your trust.
I will try to get the extension published under your user, marked as deprecated on the marketplace as well. VS Code has this feature that will guide users to an alternative extension then. Hopefully we can migrate users this way.
Thanks for letting me take over and continuing support. :)

[zxh0]

Thanks again for taking over the maintenance!

If you end up forking the repository and publishing your own version of the extension, please feel free to let me know. I will add a notice at the very top of the README pointing users to your new repository and extension, so people can easily migrate.

Thanks for your support and for keeping the project alive!

[Tubbles]

I got the deprecation warning this morning in vscode. Gotta say, going from installing a 2M+ plugin to one that has 31 installs with initial commit from last week makes me a little uneasy