@szokodiako: No time for maintainance? Here's the idea...

[Ben305]

Hi @szokodiakos,

when you started implementing typegoose almost a year go, you made working with Mongoose and Typescript a lot better.

Here at work, we always use typegoose whenever possible. It's an important piece of software that we deeply rely on. Therefore, we'd like to contribute to make typegoose even better.

We have already submitted multiple PRs, some of them got merged already. Unfortunately, another PR (#77) we sent already in December has not been merged yet (we did not get negative feedback either).

If you don't have time to maintain typegoose any longer, I would appreciate to get write access to this repository. We really don't want to create a private fork, but keep the existing project alive.

Let us bring typegoose together to the next level.

Best,
Ben

[szokodiakos]

Hello @Ben305 (and others who are reading this)!

Thanks for the message and the idea. And also sorry for everyone who might read this and I haven't responded to their PRs, issues, emails.

Unfortunately I did abadon Typegoose lately, as I got other matters to do and don't really have time to maintain it. I should've already put up an unmaintained status and look for folks who would like to continue the project.

When I first published Typegoose, it was more like a proof of concept, that Mongoose can indeed benefit from TypeScript. And now more and more people are using it, which feels absolutely great. However lately when I don't find the time to maintain Typegoose I feel like I'm letting down the community and the project.

My reason to create Typegoose was to tackle a certain problem by providing a solution that can work, and help other fellow developers who seek to close the gap between Mongoose and TypeScript.

And to continue make it happen developers who would like to help to grow this project will be added as contributors. So right now I'll grant you write access and if anyone else seems like a good fit please let me know (by email preferably).

I might return to the project as an active contributor some day, but I will keep an eye out on Typegoose, granting contribution access, etc.

Sorry for the wall of text. :)

Thanks,
Akos

[Ben305]

Thanks Akos, I really appreciate that. I will do my best for typegoose :-)

[carmas123]

@Ben305 this is really a good news for me.
Please can you see the PR from @kevin-frugier ?
He have done a good support for compound indexes and other or see my fork.
Regards.

[Ben305]

@carmas123 Hey, there's no open PR at the moment from kevin, but feel free to submit a PR for support of compound indexes.

[carmas123]

Ok @Ben305 now I make a new forked version from 3.9.0 and add this improvements.

[HardySoftware]

Is the project still being maintained actively? The most recent package released to npmjs was about 3 months ago already. The Mongoose latest version is already 5.4. However this package still depends on 5.0 Mongoose.

Please advice, I have start started some nodejs project. I need to make decision to stick with old school Mongoose (schema and model classes) or I can rely on this project.

I do like the concept of this project quite a lot!

[hasezoey]

@HardySoftware this package is actively maintained (again?)

[hasezoey]

@szokodiakos, if you ever come here again, i would apply as a maintainer to mainly tag issues and close them when needed

btw: how do you think typegoose has evolved since you "abandoned" it?

[Ben305]

It can fully support that, please add @hasezoey as maintainer

[fabioformosa]

@szokodiakos, this project needs a quick action from you, please!
As asked by @Ben305, it needs a second maintainer. Could you grant @hasezoey ?
Otherwise it will be inevitable to abandon this project and move on a fork.
Thank you.