New Maintainers are here needed!

[daviddias]

Hi everyone!

Apologies for the silence/huge delay on getting back to y'all. Unfortunately, I haven't had the chance to dedicate any time to node-spdy at all for the last year (as you might have noticed) and that translated to a bunch of PRs and issues going without response for ages, I'm sorry to everyone that has been waiting.

I want to increase the number of maintainers and I believe a way to do it is to adopt a similar strategy I created for the IPFS, libp2p and IPLD ecosystem of packages, the Lead Maintainer Protocol. Me and @indutny can continua acting as the tech leads and give space for new lead maintainers to appear and take ownership of getting the 4 modules of node-spdy into a great shape.

Looking forward to hear your thoughts.

[coolaj86]

cc/ @anandsuresh @JeffreyAngell @jakearchibald @frank-dspeed @deveshmehta7 (since you all have open PRs)

[coolaj86]

Also: If no one else volunteers to help maintain, I'd be interested in getting the v10.x fix merged in and adding engines to package.json so that v8.x users don't get it (and perhaps a major semver rev is in order). I probably wouldn't make a great maintainer, but I could follow a checklist to make sure that ci passes before a merge, the new version is tagged and published, etc.

At this point (over two months seems like a long time), if someone doesn't take over to get fixes in, and if none of the 191 forks doesn't get a blessing, the project may very well... die...

So perhaps even imperfect maintainership will be better than no maintainership.

[daviddias]

Thank you for volunteering @coolaj86! Perhaps a good solution that is today available in the Node.js community (https://changelog.com/jsparty/48 reminded me of this), is to ask for umbrella on the JS/Node.js Foundation so that this module can get proper dedicated resources.

@bnb, @dmethvin any advice on how we could make this work?

[dmethvin]

@diasdavid What sort of help are you looking for?

[daviddias]

Maintaining the 4 modules that are on this org https://github.com/spdy-http2. They are pretty well tested and have been built for a while + SPDY and HTTP2 is a protocol that is very well spec'ed out. We could use some extra hands to ensure that the community keeps getting their PRs in.

[AdamMagaluk]

I am willing to lend a hand, I haven't contributed before but have spent quite a bit of time with the module and internals to build a project I maintain.

[jimmiehansson]

Is this project still in need of maintainers?

[frank-dspeed]

@jimmiehansson i don't think so as spdy is deprecated you can now use always http2

[jimmiehansson]

@frank-dspeed Thanks. That clarifies it!

[yindia]

@daviddias pass me whatever help you needed 💯

[deveshmehta7]

I am willing to contribute for same.

…

On 06-Jan-2019 10:01 AM, "Yuvraj" ***@***.***> wrote: @daviddias <https://github.com/daviddias> pass me whatever help you needed 💯 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#339 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AnQH8be0s1YmPx2gAHXGDHto96wmcICnks5vAXwagaJpZM4VcP0r> .