Organisation

[jogibear9988]

Hello, maybe you should create a github organisation so if you also stop to work on this, others can still support ?

I do this for all my projects. see: https://github.com/node-projects

I also use quagga and will switch to your fork.

[jogibear9988]

You also could use my org if you'd like, and I will add you as owner.

for example I've done it the same way for my iobroker adapter. and now the community already has 22 members.
see https://github.com/iobroker-community-adapters
so if anyone leaves the others still could access the repo and npm

[jogibear9988]

And appveyor could now be replaced by github actions

[ericblade]

I just want to respond to this so you know i'm not ignoring it .. but I don't have a well thought out response at the moment.

I don't disagree with your point here -- we've already seen the original repo go into an unmaintainable state. I don't want to see that happen again, so I definitely want to include other people that have an interest in continuing, and make sure that multiple people have complete access.

At this time, however, I have not really encountered anyone else who is wanting to take a vested interest in continuing. Clearly we do have a few users, and lots of installs from npm and such, but at this time, no one else has really stepped up to say "well if you get hit by a bus tomorrow, i'd carry on"... not that i've asked, i've been spending a lot of time here at year end with my regular job, and holidays and family and such, but i've also done a fair amount of stuff to try to improve this repo.

Fwiw, I do have CI setup with Github Actions, I'm not entirely certain what you were saying about actions there.

[jogibear9988]

If you'd like I could help with typescript porting ...

[ericblade]

Let's discuss that on #4 ..