Any interest in transferring maintenance of this project to the Mongoose team?

[vkarpov15]

Hi @dsanel , I just wanted to bump up my comments here: would you be open to transferring this project to the mongoosejs GitHub org and handing maintenance over to the Mongoose team? No pressure, this is your project if you want to keep maintaining it, I wanted to ask just in case.

[dsanel]

Hi @vkarpov15, I noticed your comment but didn't manage to answer earlier.

I created this plugin back in 2015, and since then, I've tried to maintain it as much as I can. To be completely honest, I'm not sure how to fully transfer the project to the mongoosejs org... Currently, it has 30-40k weekly downloads, and I'm really proud of this small piece of code.

A few questions if we transfer it to mongoosejs:

• Will it remain a standalone plugin?
• What will happen with my name:
  • as a contributor on GitHub
  • as a collaborator on NPM

I haven't encountered this situation before, so I'm not 100% sure what the procedure and best practices are.

[vkarpov15]

You should be proud of this code, you've done a great job with it. It would remain a standalone plugin and we can keep your name as a contributor on GitHub and npm if you want it to. Again, no pressure, you can say no and I'll close this issue. I'm just offering support in case maintaining this package has become a burden.

[vkarpov15]

Also, I'm not sure if you've noticed, but this package is eligible for income from Tidelift: https://tidelift.com/lifter/search/npm/mongoose-delete. Currently 50 USD/mo.

[gl-aagostino]

@vkarpov15 if you guys take over this, are you converting to TS? The current types package has a few incorrect types causing big headaches.

[vkarpov15]

We would not convert this project to TypeScript. I wouldn't be opposed to adding an index.d.ts file though.

[jdhrivas]

+1 great idea... and great work @dsanel