-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this project dead? RFC: Could https://github.com/marshmallow-code be a new home for it? #248
Comments
Sounds good 👍 |
Thanks for bringing this up! There was an attempt to move the support to the sqlalchemy mailing list. Unfortunately, it didn't get any further. @kettenbach-it have you contacted @marshmallow-code already? This is a big undertaking and someone needs to steer it |
Yes, I contacted @marshmallow-code as well as @sqlalchemy. Maybe https://jazzband.co/ could help, but I haven't worked on that, yet. |
I'm happy to have a look at some of the backlog, I rely on it and think it's a really useful extension. Was there a particular issue you were interested in? |
Well, yes, #247 . But I there's a 92 that deserve to be looked after as well... |
I can contribute to the project as well. It would be useful to have better tagging on the issues to prioritise them better. |
I just started to adopt this package, looks very promising, too bad I came across this page too late. Has there been any contact with Jazzband already? Would like to help if possible. Need some auditing for multiple projects anyway, the only option seems to be using this package or moving to Postgres. Guess I would not like to choose the latter. |
Jazzband is for Django. |
Not from my side and not that I know |
As @kvesteri stated in #224 (comment) this project became stale since his company doesn't use it anymore.
Quite a lot if issues and pull requests have stacked up.
I still consider this a very useful and important package.
Maybe the guys who run https://github.com/marshmallow-code could adopt it?
sqlalchemy-continuum fit's perfectly into their portfolio!
The text was updated successfully, but these errors were encountered: