ugettext_lazy breaks with Django 4.0 alpha 1 release

[awtimmering]

Can a release be made including #342 (replace ugettext_lazy with gettext_lazy)?

The newly released Django 4.0 alpha 1 has dropped ugettext_lazy.
The latest release of django-dbbackup still uses ugettext_lazy. This was addressed in #342 however not yet released, meaning of dbbackup run into errors and can not try their applications on Django 4.0 alpha 1 until this is done.

[johnthagen]

Related to #381

[johnthagen]

Should also include wheels in the next release: #382

[johnthagen]

If @jonathan-s is no longer maintaining this project, there may need to be a new community fork. There have been no commits for a year.

[pulse-mind]

If @jonathan-s is no longer maintaining this project, there may need to be a new community fork. There have been no commits for a year.

May be @jonathan-s can give us is idea about that ?

I'm interesting by going forward on this subject

[johnthagen]

@pulse-mind Probably what needs to happen is someone volunteers to fork, merges in the necessary 4.0 compatibility patches, and publishes under an available name on PyPI such as django-dbbackup2. We can then advertise the fork on the issues in this repo to make it more discoverable. To be a "friendly" fork, we offer to merge changes back to django-dbbackup if maintainers re-appear or are willing to add new maintainers.

[pulse-mind]

@johnthagen why using a fork, it would be better to have the rights on the repo to do the job?!?
Then it would be possible to accept push requests, release versions...
I do not know how to publish on PyPi, if it is automatic when we create a version...?

[johnthagen]

why using a fork, it would be better to have the rights on the repo to do the job?!?

Ideally yes, but if the maintainers are not responsive, there is no one to grant anyone new permissions to this repo.

[pulse-mind]

why using a fork, it would be better to have the rights on the repo to do the job?!?

Ideally yes, but if the maintainers are not responsive, there is no one to grant anyone new permissions to this repo.

Agree with you.
We can let one week to @jonathan-s to answer ?

May be some others users like @ZuluPro may know something ?

Is it possible to know the list of the members who have this kind of permissions ?

[ZuluPro]

Hi everyone,
I'm sorry for my absence and my late reply.

I absolutely don't have the time to maintain DBBackup but it would be a pleasure to pass the ownership to someone with more time and knowledge.

Who's volunteer to maintain DBBackup ?

[johnthagen]

I have enough time to do very basic maintenance (keep dbbackup working on latest Django / remove deprecation warnings / etc.) I'm currently doing the same for django-solo.

If you also want to grant ability to upload to PyPI my username there is: https://pypi.org/user/johnthagen/

[pulse-mind]

Thank you @johnthagen and @ZuluPro !! If you need help, let me know!

[Archmonger]

Hey @ZuluPro

I'm coming over from the Jazzband GitHub organization. We're currently the biggest organization for OSS Django packages.

I would be interested in taking temporary ownership for this repo and doing the necessary changes to get it transferred to Jazzband.

Including myself, there are various members that I'm sure would support maintenance for this repo.

[ZuluPro]

Hi @Archmonger
Yes Jazzband iis a good idea, I think a bit of maitenance and cleaning should be good before submit Dbbackup.

Hi @johnthagen
Thank you for you time and attention,
I give you the rights for the Github Organization and the the Pypi repo.

But like @Archmonger suggested, it could be a good thing to transfer it to Jazzband

[johnthagen]

I also agree Jazzband would be a very good long term plan.

Thanks @ZuluPro!