Maintainership: I'm looking for a new Captain and a new Quartermaster!

[philippeowagner]

This repo will be moved to https://github.com/django-background-tasks and need a new Captain and a new Quartermaster.

Intend to do the same as we did a few weeks ago here https://github.com/django-hijack/django-hijack/issues/209.

Please let me know if you are interested.

[schmave]

I wouldn't have a ton of time for this, but I am willing to review small PRs and help create new releases. This is a nice little library that is very useful.

[Mogost]

I'll just mention here all the open PRs. So that more interested people can see it. #268 #258 #253 #252 #245 #244 #229 #221 #216 #206 #191 #188 #179

[guettli]

Maybe moving ownership to https://github.com/jazzband would make sense.

Here is the guideline for moving a project to the Jazzband: https://jazzband.co/about/guidelines

[schmave]

What does Jazzband provide? I googled around and read their website, but I still don't understand what they are offering, beyond maybe some tooling around releasing new versions to pip, and a Contributor Code of Conduct.

[guettli]

Jazzband provides more people who can merge Pull-Requests.

[philippeowagner]

The only benefit from moving a project to Jazzband is that it takes away your bad conscience.

Either you take care of it or you don't.

We have merely paused the time here.

Giving up – what Jazzband would be – is not an option.

[benzkji]

I wouldn consider Jazzband as giving up. Seeing many useful and important projects living there, for example pip-tools, sorl-thumbnails, django-axes, and beeing under active development.

[fergbrain]

Three questions:

1. What are the responsibilities of the Captain and QM?
2. What would you estimate would be the time commitment?
3. Any overall update on moving to the new repo location?

[philippeowagner]

Hi @fergbrain

1. Managing pull requests, reacting to bugs, triage of issues, fixing bugs, merging pull request, responding to questions, ... At the end of the day it's not an "all or nothing" thing. An option to reduce the load is not accepting PRs including new features (just focusing on compatibility and bugfix).

2. This totally depends on your ambition and circumstances. If you are going to respond to each question and every issue this will take forever. ;)

3. https://github.com/django-background-tasks/ is the next location for this project as soon as we have a solution. We will not give away the ownership but will stay in the background. Why? We made bad experiences in the past stepping back from projects too early.

[fergbrain]

@philippeowagner:

I would be interested in giving it a shot, with the following caveat: My background is in Electrical Engineering not CS, I do program and love Python, but I still have much to learn about best practices and such.

I’m relatively new to Django, but I have extensive experience and history with WordPress (though I’m kind of over it now).

I’m currently using Backgrounds in a SaaS app I’ve launched, so I’d love to be able to give back to this community.

[fergbrain]

Any thoughts @philippeowagner ?

[pssolanki111]

I'd be interested if we still have it open (after @fergbrain of course :D).

My github profile doesn't show any of my significant work as almost all of my actual repositories are private due to them being client projects.

I'd be a better fit for a mod (if that's a thing here? )

Great work on the lib btw : )

[fergbrain]

@pssolanki111: I never heard back from @philippeowagner, so I'm not sure what's going on.

[pssolanki111]

@fergbrain the lib seems to be largely unmaintained for quite a while now...

[meneses-pt]

With the break of this project with Django 4 it would be a good time to hear from @philippeowagner ...

[fabiocaccamo]

If I reach 10 monthly sponsors I will re-develop and maintain a new tasks library. 💯

[longhotsummer]

@philippeowagner are you still interested in taking this project to a new repo and, with community support, keeping it going? We find it very useful.