search

BeanieODM / beanie

Asynchronous Python ODM for MongoDB
http://beanie-odm.dev/
Apache License 2.0
2.02k stars 213 forks source link

Concerns and Suggestions Regarding Beanie Library #922

Closed alm0ra closed 4 days ago

alm0ra commented 5 months ago

I wanted to raise some concerns regarding the current state of the Beanie library, particularly in its role as an async ODM in Python.

As a user of the library, I've noticed that the maintainer seems to be unavailable, which has raised some concerns about its suitability for use in our production environment. Additionally, I've observed that there are numerous open issues and pull requests that often take a month or longer to be reviewed.

In light of these observations, I believe it might be beneficial to explore some potential solutions to improve the maintenance and responsiveness of the project. Here are a few suggestions:

  1. Consider Turning the Project into an Organization: By transitioning the project to an organization, it could attract more contributors and potentially alleviate the burden on a single maintainer.

  2. Engage with MongoDB: Since Beanie is closely related to MongoDB, it might be worthwhile to reach out to the MongoDB community for support or collaboration opportunities.

  3. Expand the Maintainer Team: Adding more maintainers to the project could help distribute the workload and improve the speed of issue resolution and pull request reviews.

I believe implementing one or more of these suggestions could greatly benefit the Beanie library and its users. I'm eager to hear your thoughts and discuss potential next steps.

b-simjoo commented 5 months ago

I hope they see this issue as soon as possible!

alm0ra commented 4 months ago

It seems this issue fixed Thanks @roman-right

Diegovsky commented 1 month ago

beanie is still not ready for production, so I wouldn't mark this as closed.

07pepa commented 1 month ago

I belive @roman-right is busy ATM.

But as far as I know points 1. and 3. were done (curetnly there are 9 devs on project including me)

for 2. i am not sure I do not know if roman reached biger mongo comunity. But just in case what is best/correct way do do it ?

I am reopening it since only 2/3 were done.

from my point of view there is better testing

gsakkis commented 1 month ago

Point 2 is the least of the problems. With all due respect, the number of open issues (mostly bugs) has gone up, not down, since 1 and 3 were done. I'm not even counting the dozens that are autoclosed "due to inactivity". I'm still stuck on 1.23.6 and can't/won't upgrade anytime soon due to (at least) one regression and general uncertainty about the quality of the project.

adeelsohailahmed commented 1 month ago

Point 2 is the least of the problems. With all due respect, the number of open issues (mostly bugs) has gone up, not down, since 1 and 3 were done. I'm not even counting the dozens that are autoclosed "due to inactivity". I'm still stuck on 1.23.6 and can't/won't upgrade anytime soon due to (at least) one regression and general uncertainty about the quality of the project.

Please create an issue for the regression you mentioned. And, of course, PR addressing the issue is always welcome.

gsakkis commented 1 month ago

It's https://github.com/BeanieODM/beanie/issues/829 but that's not the point, the point is it could be any subset of the (currently) 64 open and 89 closed "stale" bugs. Expanding the maintainer team from 1 to 9 doesn't seem to have addressed the concerns raised in this issue.

github-actions[bot] commented 2 weeks ago

This issue is stale because it has been open 30 days with no activity.

github-actions[bot] commented 4 days ago

This issue was closed because it has been stalled for 14 days with no activity.