Mongokit Future (call for maintainer)

[eneepo]

Mongokit is really aswesome, it has many really nice features that makes it apart from other odms. I want to really appriciate the effort and contribution. But I'm wondering why it's development is so slow and pull requests are left untouched for a long time? Other than being busy is lack of motivation or something?
Can some one shed some light on mogokit situation? I would really apriciate.

[namlook]

Hi,

I'm glad you ask. The last two years, I was into the creation of a startup (http://www.elkorado.com).The project was built on top of MongoKit. This year, a big client asked me if I can port Elkorado to work with his data. The project of the client is quite big and last till the end of 2016 ; plus, the technology used is Node.js.

While using node.js, I'm starting to realize that I wanted to invest more time in this technology and I may not return to Python.

I started MongoKit in 5 years ago while I was loving the python programming language. The development was a bit slow as I was putting all my time in a startup. But MongoKit is open source and I took the time to apply pull requests (thanks to all the contributors btw). Now, I realize that I don't have the motivation anymore. There are some pull requests I'd love to merge (like the python 3 support #151) and I always wanted to give MongoKit a descent website... but I won't be able to do that.

That's why I use this ticket to make a call to maintainer. I hope someone will be motivated enough to bring MongoKit to the next level. Please leave a comment if you are interested. All I ask is to not make dramatically API changes. I suspect some people are using MongoKit in production and it is important to keep the versions retrocompatibles (as far as possible).

MongoKit is not dead (at all), but for me, it's the end of the adventure.

N.

[eneepo]

Hi There.

It's sad to hear you are leaving python, for sure python commiunity will miss you, and hearby let me once again appriciate all of your effort and contribution. Thanks for doing your part of making the world a better place. :)

Since non of existing odms meet my demands and MongoKit being just like using PyMongo, I'm quite passionate about it and I'm using it with my next project and I'm more than eager to help moving it to the next level and making v1.0 happen. What I can do for now(and for sure) is making the descent web site and some improvements on documentaion. But since I don't have your exprtise and it's the first open source project that I'm going to contibute, I don't have the self confidence to take part on the main code(To be honsest there are some parts that I can undersand clearly what's going on - I worked on #151 to make it more compatible with current release and I resolved most of the issues but there are 4 tests that don't pass and I don't know why ecactly). Of course with your supervision and mentorship that can be solved, too.

And one reason I like MongoKit is its simple full featured api, who wants to change that? :)

So where should I start? Some guide lines would be helpful.

[gnowgi]

We are using mongokit for both development and production servers. So, we do have interest to keep the library maintained. Though I cannot promise immediate help, I will look for a person who could join the effort to ensure the project continues.

[gulbinas]

Same here, using on prod and dev servers. Already contributed some patches regarding code quality.
I think, we should clean the code and prepared to accept commits only with tests. So, currently all tests should be passing.

And, in travis i can see you've setuped python 2.5 support test. Do we really need it? Maybe 2.7 and 3?

[namlook]

I added @eneepo and @gulbinas as collaborators for this repository.

You're in charge now guys, you can start branches and merge pull requests. Tell me if you have any troubles to find repositories.

[sylvinus]

(Just wanted to drop in and say that we also use MongoKit in production. Glad to see a new team stepping in! Thanks in advance!)

[eneepo]

Thanks, some great surprises are on the way so make sure you're checking the project reguarly, they will be anounced really soon. Who knows, maybe on christmas ;)

[AlmogCohen]

Is it dead again? No pull request and no issues responses

[namlook]

I reopen this issue as it seems the project needs more maintainers...

(I also added a note at the beginning of the README.)

[sylvinus]

Awesome.

Future maintainers may use some of the code we've done at https://github.com/pricingassistant/mongokat to support PyMongo 3.0+

[panchr]

I've been using MongoKit a lot lately and I like it - so I could also help with some maintenance. I'm also working on a separate project and starting college soon, so I don't think I can do too much, but I can help every now and then.

I might start with just updating the documentation and fixing any grammatical/spelling errors, but I'll do that as a pull request soon.

[IuryAlves]

MongoKit is awesome. I would be glad to help in anything.

[omarkhd]

I would like to contribute. I'm about to start using it in 2 projects that will be on production in the first half of the year, and to contribute would be great.

Are there some guidelines or requirements? How can I start contributing?

[omarkhd]

@eneepo, @gulbinas do you need some help?

[jsw883]

I'm also doing some dedicated work with pymongo this year, and have been rolling my own ORM along similar lines to https://github.com/slacy/minimongo, but structured in a cleaner way, with support for 3.0 and 3.2 (although 3.2 isn't tested, there shouldn't be any issues). I would be interested in contributing to the project as time allows?

[geeksambhu]

Any updates on pymongo 3.0 support ??

[Windfarer]

We have ported this great project to python 3 and pymongo 3. And thanks a lot to namlook for creating this project.

https://github.com/Windfarer/mongokit-ng

The first step is done, we can use this library in python 3 now, but we only tests on MongoDB 4.0, and Python 3.5~3.8. And because the underlying pymongo3 api has changed, some of the APIs are marked as deprecated, we are not move to new API currently, but in the next version we will solve this issue.

Welcome anyone to try this library, and give us some feedback.