Skip to content
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

Organisational stuff #73

Closed
MichaelAkvo opened this issue Feb 7, 2023 · 2 comments
Closed

Organisational stuff #73

MichaelAkvo opened this issue Feb 7, 2023 · 2 comments

Comments

@MichaelAkvo
Copy link

Hi @GDay ,

like a few others, I was looking for a stable and maintained fork, which yours seems to be. Following Koed00#701 just a few questions:

  • How's the org creation going?
    • Are you still planning on moving it to one?
    • Have you considered jazzband as an option
  • Would you consider activating discussions? I have some simple questions for which discussions are probably better suited, hence this question
@GDay
Copy link
Collaborator

GDay commented Feb 7, 2023

Hi @MichaelAkvo,

How's the org creation going?

That's done now, thanks for reminder. I am not moving it to jazzband at this time. I am still hoping that the original creator of django-q will add either me or someone else to the repo to pick up where it was left. At that point, I would just make this repo read-only and then push the django-q2 pipy package upstream with django-q, so no one gets left behind (regardless of what package they use).
I will give that some more time, I will reconsider jazzband at a later time.

Would you consider activating discussions?

I have enabled that now.

@MichaelAkvo
Copy link
Author

Thanks for the answer and for opening discussions. Hopefully we'll hear from the original creator soon.

This issue is resolved imo. Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants