Ideas about the future of this project

[srs]

Hi everyone.

I am posting this here as an issue since I have no idea where to post such a message :-) I started this project some time ago to solve my own problem. It seems that a lot of other developers out there had the same problem. I realize that a lot of users are now dependent of this plugin and would like to discuss how to move forward so it will be maintained by more than me.

My ideas for the future is as follows (open for input):

• Move the project to a new organization node4j (https://github.com/node4j). This will make it easier for other developers to take ownership of the project and help me maintain it.
• Better documentation and more reliable versioning (compatibility matrix).
• Maintain a clear roadmap of things to come in next versions of the plugin.

Also this "organization" would host a node maven repo and npm/yarn maven repo that will also be maintained by this "organization". This repository does not actually contains the binaries but acts as a proxy. See https://github.com/node4j/node-repo-proxy. This will make it easier for the plugin to download node and npm/yarn versions.

What do you think about this?

BR, Sten Roger

[web-devel]

Hi,

First of all, thanks for your work on the plugin!

The idea of organization sounds very promising. With regarding to repository - does it mean that we will have yet another point of failure? Can we think on how to distribute the plugin and everything else using existing well-known repositories like jcenter? (Btw do you plan to publish latest version of the plugin on jcenter)?

[juddgaddie]

Whatever will get the development going on this is a good thing. Just do it!

[epeee]

I like the idea. Furthermore, I might be able to help you maintaining the plugin. btw, thx a lot for your work!

[sleicht]

Is this still under discussion? Can I help in any way?