Transfer Out: django-dbbackup

[Archmonger]

Things have been moving slowly on #196, which has caused us to be hesitant of significant overhauls to django-dbbackup due to the inevitable need for admin management caused by changing CI workflows. Additionally, the jazzband user registration workflow has been broken for many users, making it hard to add new maintainers.

While #196 is still being handled I'd like to transfer the repo out of Jazzband directly to my GitHub username the django-dbbackup org.

[benjaoming]

@Archmonger FYI, there's also the organization that it used to be in: https://github.com/django-dbbackup

[Archmonger]

I was going to port to my username while we discuss what org it should go to.

We'll probably decide to put it back in the original org ultimately. But there are other candidates, such as revsys.

Do you have time to have this discussion pre-transfer out?

[benjaoming]

@Archmonger I'm still an admin in the old org, so LMK if you wanna use it and I'll add you as an admin 👍

[johnthagen]

This seems to be fundamentally blocked on

• We need more roadies in jazzband #196

@jezdez Would you be able to help us with this ticket? Thank you.

[benjaoming]

@johnthagen @Archmonger you are both owners of https://github.com/django-dbbackup so you can use that for the transfer, if you want 👍

Edit: Oh I see that's already reflected in the issue description!

[jezdez]

Hey there, thanks for the issue, I'll have time end of this week to go through some of the requests like this.

But from the original issue description from a month ago, I'm not sure if I understand @Archmonger's argument how #288 and #196 impact django-dbbackup. Could you elaborate how the rare user registration bug based on GitHub API throttling impacted maintenance of the project? Why is the roadie staffing issue limiting django-dbbackup's future?

For the record: obviously @johnthagen and @Archmonger ARE the project leads and can decide to go elsewhere. Just want to make sure I understand why and not go through the process if it's not warranted.

Thank you!

[Archmonger]

The user registration issue not getting handled is more of a sign of the times. We don't have a specific user we were trying to onboard, but if we did and they had registration troubles they'd be stranded.

You have too little time on your hands to handle org issue tickets, which causes a huge burden of delays. I do love the concept of Jazzband, but things have been moving painfully slow.

Here's a big issue I forgot to mention in the original post:

• django-dbbackup: jazzband.co PyPI release internal server error #287

In our experience it's usually 8+ months between when you get time to look at our issues in the jazzband/help backlog. It pretty brutal to develop with those massive delays.

[jezdez]

The user registration issue not getting handled is more of a sign of the times. We don't have a specific user we were trying to onboard, but if we did and they had registration troubles they'd be stranded.

Thanks for elaborating your concerns.

You have too little time on your hands to handle org issue tickets, which causes a huge burden of delays. I do love the concept of Jazzband, but things have been moving painfully slow.

That's not an accurate picture you're painting here, you're projecting your experience with a few projects onto the whole org, while in fact there have been many releases done via Jazzband (~900) quietly working out okay. That's not an excuse for your release problems, but should provide some context.

Here's a big issue I forgot to mention in the original post:

#287

Thanks for the pointer!

In our experience it's usually 8+ months between when you get time to look at our issues in the jazzband/help backlog. It pretty brutal to develop with those massive delays.

Phew, "pretty brutal". Not sure what I feel about that. I'm interpreting that as your expectations not being met by my volunteer work, and that it has been a disappointment how slow bugs have been fixed. Is that correct?

In my OSS experience, 8 months is not really long in terms of development or releases. What would be an appropriate response time for you?

[Archmonger]

I just want to be clear that I'm not trying to personally attack you. I apologize if it came off that way.

We moved the repo to Jazzband to increase maintainability. However, the cumulation of everything caused even more maintainability issues.

[jezdez]

I just want to be clear that I'm not trying to personally attack you. I apologize if it came off that way.

We moved the repo to Jazzband to increase maintainability. However, the cumulation of everything caused even more maintainability issues.

Thanks @Archmonger, much appreciated!

[johnthagen]

I'll echo what @Archmonger said. It's really the loss of being able to administer project-level things on our GitHub repo. It's hard to expect one person in their free time to manage all those little things. Being in our own org means we can take that responsibility and work on ourselves.

In any case, thank you for your work on Jazzband and helping us address this issue.

[johnthagen]

@jezdez Just checking in again if you could transfer the django-dbbackup repo for us. Thanks!

[johnthagen]

@jezdez Another friendly ping if you could help us with the django-dbbackup transfer. It would really help us move our project forward. Thank you.

[johnthagen]

@jezdez Any chance you could help us with this? 🙏

[Archmonger]

@jezdez Apologies for the ping, but this ticket has been open for 1.25 years 😭

[jezdez]

@Archmonger

Archmonger/django-dbbackup already exists and You can only transfer a repository from an organization to yourself at this time

[johnthagen]

@jezdez If @Archmonger deletes his fork, can you transfer this repo to Archmonger/django-dbbackup and then he can transfer it himself to django-dbbackup/django-dbbackup?

Thanks.

[Archmonger]

I've renamed my fork to free up the Archmonger/django-bbackup namespace.

[johnthagen]

@jezdez Can you perform the transfer now? Thanks.

[jezdez]

@Archmonger

Archmonger already has a repository in the jazzband/django-dbbackup network and You can only transfer a repository from an organization to yourself at this time

[Archmonger]

I'm a bit confused by that error. Is it implying that you have to transfer it to jezdez/django-dbbackup as an intermediary step?