You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find myself checking the repo after seeing it as a dependency in wild. I got involved with this project around 2019, after using it for a commercial projects and seeing that maintainers are needed. At the time, strawberry was relatively new and Django integration was weak / non-existent. After giving my best effort to keep the project alive for a year, I came to a point of realization that this is not feasible and it's time to consider the alternatives.
It's been 6 years and I see that the project is still in a similar state. There was another "should we kill it" discussion a couple years ago, but there wasn't unanimous decision and no action taken. Right now, the current state of the project may be still somehow useful, but I think keeping it alive is doing more harm than good:
GitHub's "Security and quality" page has 44 active warnings.
We are still supporting EOL'd Python versions but nothing with active support.
We are still supporting EOL'd Django versions but not 6.0
There are tons of issues about the internal workings of the library and almost noone to fix them.
Last patch release was a year ago. The previous patch release was in 2024.
I believe it's clear that the project is not maintained anymore and creating a secure setup with a direct pip install will get impossible soon, but GitHub's "used by" count is 16k, which means we are creating security and performance risks for 16k+ projects. Considering that AI agents are much less picky about dependencies and not everyone has enough time / knowledge to understand the current status of the project, not having any "not maintained" note in the readme creates an active risk for anyone using the package.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hey all, 👋🏻 from an old maintainer.
I find myself checking the repo after seeing it as a dependency in wild. I got involved with this project around 2019, after using it for a commercial projects and seeing that maintainers are needed. At the time, strawberry was relatively new and Django integration was weak / non-existent. After giving my best effort to keep the project alive for a year, I came to a point of realization that this is not feasible and it's time to consider the alternatives.
It's been 6 years and I see that the project is still in a similar state. There was another "should we kill it" discussion a couple years ago, but there wasn't unanimous decision and no action taken. Right now, the current state of the project may be still somehow useful, but I think keeping it alive is doing more harm than good:
I believe it's clear that the project is not maintained anymore and creating a secure setup with a direct pip install will get impossible soon, but GitHub's "used by" count is 16k, which means we are creating security and performance risks for 16k+ projects. Considering that AI agents are much less picky about dependencies and not everyone has enough time / knowledge to understand the current status of the project, not having any "not maintained" note in the readme creates an active risk for anyone using the package.
All reactions