We're looking for maintainers

[ewjoachim]

For a few years, I've spent limited time maintaining Procrastinate. I don't find it thrilling to maintain the project alone, so I tend to spend my free time elsewhere and just take care of upgrading what needs to be upgraded so everything stays secure.

If there are other people willing to share design discussions, I'll be glad to share the burden, and I'll be glad to take some time to show you the in-and-outs of the project.

If you're interested, join the Discord

[jerluc]

@ewjoachim are you still looking for some help from folks? If it helps I'd be open to reviewing some issues/PRs and contributing the occasional bugfix/feature as needed.

FWIW I only have a few months of experience using procrastinate in production, so I'm not yet super familiar with its internals, but I could probably pick things up given some guidance!

[ewjoachim]

Ah, definitely! If you want, I'd love to show you around (assuming you don't already know more than me 😄). We can try and find a time if you want this to be sync. Feel free to reach out via Discord if you use that (@ewjoachim).

In the meantime, I can try and answer questions you may have on existing issues.

Let's get this going! Thank you a lot ! <3

[ewjoachim]

(So, there's a discord server now: https://discord.gg/JWZeNq6P6Z . Feel free to join :) )

[zschumacher]

I'm happy to help out, love the idea of this project

[ewjoachim]

Great ! I think I'll setup a discord server with the (few) people who expressed their interest, so we can keep some kind of communication channel to organize ourselves, and get to know each other.

https://discord.gg/JWZeNq6P6Z
If Discord is ok with you, feel free to join. If you'd rather stick to GitHub, let's discuss how to onboard you :)

[pantlavanya]

I too love the idea of this project, can help out.

[ewjoachim]

Great :) Since this was posted, the project gained a co-maintainer and some contributors. That said, if you'd like to help out, please chime in in (well you guessed it) the discord server :)

[auvipy]

I like the projects Idea. I want to learn from this project and see how we could utilize it celery in future :)

[medihack]

Hi @auvipy, it's great to see you here! Before I started using Procrastinate and became a co-maintainer of the project, I worked with Celery for quite a while. Please feel free to ask any questions.

[auvipy]

Is it possible to use it as a back end of celery?

[medihack]

Do you mean as a broker backend? What must it implement for that? Are there any specifications (e.g., an abstract class to inherit)?

[auvipy]

Yes, like we got sqlalchemy broker now

[ewjoachim]

Note

Don't read this as a way to refuse anything, but 100% as a mark of my lack of understanding of what we're talking about.

Is there a precedent of Celery brokers that are not just message passing solutions, but task processing libs? Like: is there a dramatiq broker for Celery?

I'm a little confused regarding what you're suggesting? Or would the aim be to use the message queue bit but not the worker or the task definition? In that case, it would mean, mostly, that Celery would just reuse the SQL schema and procedures? But then you're saying that there's a sqlalchemy backend, so somehow, Celery already has a working set of SQL queries that allows using postgres as a broker? (and other DBs too)? Or would the aim be to have a more specialized postgres broker that would use listen/notify and locks? I don't think the notion of locks exist in Celery's message protocol (unless I'm mistaken?) and I don't know if we could retrofit procrastinate periodic tasks in celery beat without changes so deep it would completely break the model?