Alarming lack of support

[nfantone]

As AMQP is a popular choice of transport and one of the main reasons to move towards robust microservices in node.js, it strikes me as very odd that one of the top npm modules for building them has shown no support or releases for this transport in over a year.

For that reason, we have created seneca-amqp-transport. I realize there are other attempts out there to placate this problem, and everyone is welcome to give them a try, but we are aiming at becoming the definitive solution in providing Seneca.js services over AMQP.

So, to the Seneca guys: @mcdonnelldean, @geek, @mcollina, @rjrodger and co., are you willing to join forces and merge all of this efforts into a single de-facto plugin? I can offer my time to participate actively in this and maintain it.

And to everyone else coming here in disappointment, for the time being, give seneca-amqp-transport a try.

DISCLAIMER: I am one of the collaborators on seneca-amqp-transport.

[geek]

@nfantone are you interested in taking over seneca-rabbitmq-transport as the lead maintainer?

[nfantone]

@geek Sure am. Would you consider deprecating this plugin in favor of seneca-amqp-transport? Not only it is better named, but most of the things I'd like to see here are already implemented there.

[geek]

Absolutely, we can add a message about it not being supported and a link to your module. After a couple of weeks we can deprecate it.

[nfantone]

Great! Any specific guidelines or requirements? Testing envs? Coverage?

[geek]

@nfantone will leave that up to you since you are the maintainer. But these are general guidelines: http://senecajs.org/contribute/details/guidelines.html

[mcdonnelldean]

@nfantone @geek This is super news, yeah we have been a bit stretched so any help on maintainership is more than welcome. @AdrieanKhisbe has a great idea on how to 'standardise' a repo but as @geek says the final decisions would come down to you as maintainer.

[nfantone]

@mcdonnelldean Any idea is welcome. I'm up for "standarising". Also, could any one of you take a look at latest develop branch of seneca-amqp-transport and comment on it? It'd be nice to receive feedback from core devs and start laying out a roadmap for features. From there, we can schedule a new release.

[nfantone]

So... nothing?

I take it you guys are not actively working on Seneca as of late?

[mcdonnelldean]

@nfantone Sorry,

We are working actively but we are just super busy. I'll respond in detail soon. Just in meetings now.

[nfantone]

@mcdonnelldean Don't be sorry. It's great to hear that the project is moving forward.

I was just pinging to make sure I wasn't the only person in the planet that cares about this 🐑 .

[mcollina]

@nfantone Seneca has lots of plugins, and maintaining everything is a lot of work. "Not actively working on Seneca" is a strong sentence, because there has been a lot of recent activity. This plugin might have a bit neglected :(.

[mcdonnelldean]

Let's put it down to @nfantone wanting to get started. We should probably help get this over the line so @nfantone I'd say the best thing to do is add a concrete list of what you need to get set up and ready to run as the lead maintainer. We can organise to get this done then.

[AdrieanKhisbe]

I pass by quickly,

Just added label to https://trello.com/c/3KeYsAQV/11-seneca-rabbitmq-transport

We should push this trello forward. That will help us far more manage the ecosystem:
https://trello.com/b/gr5agWi3/seneca-ecosystem

cf senecajs/senecajs.org#159 😃

[nfantone]

@mcollina It sounded like a strong sentence. I apologize for that. Didn't mean to be mean. All in all, it was kinda worthwhile as it seems I got more responses in these past 20 minutes than in the last ten days. So, thank you for that!

@mcdonnelldean I'll come up with such list in short. Stay tuned.

@AdrieanKhisbe Nice to meet you! Trello board is not publicly accessible, so I couldn't take a peek. But sure, moving it this to your todos seems lke a step forward.

[rjrodger]

@nfantone I completely understand your frustration - and we are in fact very grateful to have you on board. Please reach out also on the main Seneca gitter: https://gitter.im/senecajs/seneca as that tends to be more "real time" :)

[nfantone]

@rjrodger Thanks for your words. 👍 on the use of gitter.

[mcdonnelldean]

@nfantone Where are we on this? Do we need to do anything more on either end?

[nfantone]

@mcdonnelldean I'd very much like to hear back from those of you who have tested out the plugin. I'd also like to compile a list of needed features or roadmap. Those "ideas" on repo standarization would also be good to hear.

Lastly, we need to push latest master to npm as a new release. @disintegrator should be on it.