Update the Maintainer details in the readme.

[rozza]

I haven't been a maintainer for a long time, so I think its high time that Rozza was removed from the maintainer details in the readme! The current maintainers are doing a great job and I can't take any credit for that!

Also now would be a good time to see if there is anything else to handover?

[lafrech]

@rozza Perhaps should we open a "call for maintainers" issue like you did with flask-mongoengine (MongoEngine/flask-mongoengine#71). It's not clear who is actually still here and it would be nice to integrate newcomers.

As far as I know, @warvariuc and @wojcikstefan are interested in @MongoEngine/mongoengine or @MongoEngine/flask-mongoengine (or both). See #889 (comment) and MongoEngine/flask-mongoengine#273 (comment)).

Unfortunately, I can't invite them to join the team. I don't have the privileges for that. We should ensure that there's still people in the team with admin privileges... I suppose @thedrow does.

If someone in the team with enough privileges reads this, please consider inviting them, and/or maybe give me admin privileges on those repos. I'm not currently involved in the development, but at least I'll try to help with the transition.

MongoEngine also needs a roadmap. I don't know of any roadmap, currently. There are a few milestones set, but I'm not sure they're up to date. Ultimately, it boils down to who's still here and what are the plans. We should also open a Roadmap issue (in flask-mongoengine, it is the same as the "call for maintainer issue") for people willing to contribute to discuss about the future. Unless they prefer another communication channel, of course.

And @rozza, to finally answer your question, I guess you should ensure the team has the privileges to manage the website and to upload to PyPi. I believe the latter is covered already by @thedrow.

[thedrow]

I can't contribute much code unfortunately since I'm super busy lately. I am able to ensure the longevity of this project.
@MongoEngine/mongoengine I agree that we need a roadmap. We can discuss it over Gitter.
Let's try to coordinate an open development conversation tomorrow or the day after. Is that OK with you?

[thedrow]

@lafrech I just made you the team maintainer of both MongoEngine and MongoEngine-flask so you'd be able to invite people to those repositories.

[thedrow]

@lafrech I tried inviting you to Gitter but your Github email appears to be a fake one.

[lafrech]

@thedrow OK, thanks, so now I can invite people into the teams. I still have access only to MongoEngine repo settings, not flask-mongoengine repo settings, but that's not an issue since the only thing I needed was to let people in and this is a team issue.

Currently, I don't have much time to spend on this either. Here's my position:

• We're developing an application for which we switched to umongo, so I'm more involved in the development of umongo.
• We still have a small ME/flask-ME based app so I'm happy if I can help keeping those alive. This is why I enrolled here. On flask-mongoengine, I could make myself useful with a few improvements and I helped with the issue tracker. There is still a few things I have in mind that I might make at some point. I must admit I can't do as much with ME. It is a huge piece of code and even sorting issue into bugs/questions/duplicates is complicated to me.

My point today was just to ensure I could help integrating new contributors when needed.

I don't know Gitter. My main email address in GitHub is valid. The email address in my commits in ME is valid too. Anyway, considering my involvement, there's probably no point in me joining a discussion about the roadmap. I'll be interested in what comes out of it, though. You can try to invite other potentially still active members of the team, and new comers (@warvariuc and @wojcikstefan).

Thanks.

[wojcikstefan]

Hi, I'd love to get more involved, especially with regards to a) fixing things that are broken, b) simplifying things that are overly complex, c) making things more performant, d) making the code and the documentation clearer.

I'm working on a project where we're using our own fork of MongoEngine right now (https://github.com/closeio/mongoengine), primarily due to its superior performance. Our main MongoDB cluster is nearing 4TB in data and we're serving most of that in real time via the API using our own API framework (https://github.com/closeio/flask-mongorest). I'd love to work on consolidating the performance tweaks and the repos to the point where we can happily use this package. We're also planning to use the upstream version in our new microservice.

Are there any issues that y'all consider to be the highest priority?