Perspectives for the project in the future

[ccrvlh]

Hello all. I noticed that the package is no longer being maintained. As much as I understand that using this package is not strictly necessary, I just had a really bad experience integrating Celery with a production application:

• Lot's of headache setting up the project itself in docker-compose
• Lot's of work to refactor the code to pre-register existing functions to be run by Celery
• Incredibly painful to push application context
• Hard implementation of the beats functionality

Among a few other things. There's a package that's currently being actively maintained, called Flask-Execute that I think solves most of these problems in a very nice and simple way. I was wondering if you guys would consider donating the name Flask-Celery to an active project, and maybe even merge some aspects of the project. Just like it's not strictly necessary to use Flask-SQLAlchemy to integrate SQLAlchemy with Flask, it sure makes things a whole lot easier. I think the same applies to Flask-Execute.

What do you guys think? Thanks a lot.