the future of tedious-connection-pool

[ben-page]

Hi,

I'm the maintainer of the tedious-connection-pool library. I took over from pekim in January of 2015. However, late last year I stopped actively using SQL Server with Node.js, though I still use it with C#. I don't indend to abandon the project, but I'd like to see more collaboration between the two projects. It may even make sense to merge the connection pool features directly into tedious.

So, I'm suggesting that we create a single github organization to maintain both projects. And of course all active tedious collaborators would become collaborators in the organization. And whoever you all feel should be an owner of the organization, would be.

What do the tedious collaborators think?

[arthurschreiber]

@ben-page A tedious organization would be a great start. I'd like to welcome additional contributors here, but I'm not an admin of the repository here.

I just created a new organization, called node-tedious (tedious and tediousjs were already taken). If you can come up with a better name, we can change this.

Pinging @pekim to see if he would be open on transferring the repository to that organization.

[pekim]

Sure, I'd be happy with that.

[ben-page]

That's great!
I actually created tediousjs the other day. I just invited you both to be owners of the organization.

[arthurschreiber]

Thanks for setting that up! @pekim Would you mind transferring this repo to the tediousjs organization?

[ben-page]

@pekim, will you transfer tedious-connection-pool as well, please?

[arthurschreiber]

@pekim Thank you for transferring the repo!

[GuyHarwood]

@arthurschreiber @ben-page should tedious-connection-pool no longer be used? it doesn't appear to have been touched in a long time, or is that because it is just assumed to work?

we are seeing very strange connection pool saturation issues with tedious v3 + sql azure.

Any suggestions greatly appreciated