binary-parser Maintainers wanted

I created this package a long time ago when I was primarily developing in JavaScript. It has been seven years since then and I am no longer an active user of node.js and the broader JavaScript ecosystem.

However, it seems like this package is still widely used and relied upon by ~500 repositories and ~100 npm packages. Therefore, I think it is my responsibility to look for maintainers who could help maintain this package and potentially take over in the future. Let me know if you are interested.

Thanks, Keichi

May 14 '20 13:05 keichi

Hi @keichi, I'd like to become a maintainer of this package! First time I've seen your API, I was so much impressed and wrote enhanced typings of it. Could you add me as a collaborator on GitHub, and add me as an owner on NPM?

Mar 16 '21 18:03 yuhr

@yuhr Your help is highly appreciated! I will add you as a collaborator to this repository. We converted our codebase from JavaScript to TypeScript at some point, but unfortunately the typings are not as accurate as yours... I hope you can help in this area.

I am a bit hesitant about the NPM ownership though. I've set up a GitHub CI pipeline to automatically publish a new version on NPM if a release is created. So once I add you as a collaborator on GitHub, you should be able to create new releases on NPM. Would that be ok?

Mar 17 '21 15:03 keichi

I am a bit hesitant about the NPM ownership though. I've set up a GitHub CI pipeline to automatically publish a new version on NPM if a release is created. So once I add you as a collaborator on GitHub, you should be able to create new releases on NPM. Would that be ok?

Oh, then it's all okay 😆 Thanks!

Mar 17 '21 17:03 yuhr

I’ve sent you an invitation. Please check your inbox.

-- KT

On Mar 18, 2021, at 2:54, Yu Shimura @.***> wrote:

I am a bit hesitant about the NPM ownership though. I've set up a GitHub CI pipeline to automatically publish a new version on NPM if a release is created. So once I add you as a collaborator on GitHub, you should be able to create new releases on NPM. Would that be ok?

Oh, then it's all okay 😆

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Mar 18 '21 00:03 keichi

Thanks, I'm going to start by reviewing existing PRs and Issues.

Mar 18 '21 13:03 yuhr