Consider creating a GitHub Organization with more maintainers

[mtscout6]

First off I'd like to express my appreciation for this library and for recently bringing in #107 and #116. Some members of my team have struggled with these issues, so it's great to see them applied.

With that said I understand the pressures you can encounter when an OSS library becomes more than you can bare on your own. May I suggest that this repo get transferred to a GitHub Organization where you can assign a team to help you maintain it? By the shear number of stars and pending pull requests it's clear that the work you've done is really appreciated. This is something I did with the react-bootstrap project earlier this year and now that project is thriving well beyond my means to keep up with it. I added some documentation on becoming a maintainer on that repo. It sounds crazy at first, and I wouldn't say just add anyone that chimes in, but many hands are better than one.

My team here at Towers Watson has been building out tooling to assist us with ensuring our code is tested and approved for release to a production environment. We would be more than happy to help as much as we can, seeing as we are actively using it.

/cc @KanoYugoro

[KanoYugoro]

+1

[shermanjoshua]

+1 - happy to help in whatever way I can

[andhernand]

👍 - I would also be happy to help in any way I can.

[mtscout6]

We got tired of waiting for support on this and #122 so we created the jira-node organization and pushed the jira-client npm package which is just a fork of this one. We are open to adding collaborators and working with other folks in the community. If anyone is interested we are looking for collaborators to help support this useful utility.

I didn't realize that tests were failing on master when I pushed that release, but @KanoYugoro is working on fixing those tests and then we'll push another release.