📣 looking for maintainers

[jacobian]

I'd adopted this codebase with every intention of being a good maintainer, but that's clearly not happening. There's a backlog of issues I'm unable to get to, and it's clearly leading to some frustration. So, I'm taking the nudge of Volunteer Responsibility Amnesty Day and looking for new maintainers.

If you'd like to pick up maintaining this repo, leave a comment here and let me know. I'll check back in a week or so and do the logistics.

I am mildly wary of supply-chain attacks, so I do have a few requirements to try to protect our users:

1. If more than one person step up I'd like y'all to coordinate creating an organization to transfer this repo to; if it's just a single person I can transfer it to your personal github or a repo, either way.
2. Anyone who's going to be a maintainer needs at least a bit of history here on github -- I won't be ok transferring this to a new account.
3. I'd like you to commit to cutting a new release within a month or so, as a way of notifying users that the ownership has changed. I'll grant you access to PyPI to do the release, but I'll also keep access; I'll had that last bit over once this new release goes out.

Sorry I haven't been a good steward; I'm sure the next folks will do better!

[jacobian]

@dcwatson @ParthS007 y'all have expressed interest in being maintainers in the past; tagging you here in case you're still interested.

[ParthS007]

Hello @jacobian , thanks for tagging. I am still interested.

I plan to do a release by mid of January if it sounds good to you?

[dcwatson]

I'm also still happy to help out (but equally happy not to!)

Without being too long-winded, I think that an org is a good idea for this project, even (/especially?) if there's only one active maintainer. Personally, I would consider transferring it to Jazzband and naming a small number of project "leads" for oversight and PyPI responsibilities.

My ideal for this project would be to get it to a place where people can reasonably extend it for third-party or custom database backends, triage/close all the issues and PRs, make sure the CI keeps chugging along with new Django/Python releases, and pretty much only touch it when something breaks.

[jacobian]

Jazzband would be lovely, but I don't have a strong feeling about specifics. I'll let y'all (and anyone else who wants to volunteer) figure out the details, and once you have a "home" in mind ping me and I'll do the needful. Thank you!

[adamchainz]

Also happy to become maintainer, I maintain a few packages already

[scuerda]

@jacobian saw your blog post and wanted to throw my name in to volunteer. I would prefer to be part of a group.

[mattseymour]

Seconding putting this project into an organization (whether new or existing) is a much better idea than passing onto a single developer, given how well used and how wide reaching dj-database-urls is it makes a lot of sense. It will also give the project a bit more accountability than a single person wanting to move the project in a direction other may question.

Happy to put my name down as a maintainer for this.

[scuerda]

Sounds like we have a group of folks willing to step up? In terms of Jazzband, does anyone have thoughts on if this project is in good enough shape to move there? Would it be reasonable to focus on cutting a release, triaging existing issues, and then move to Jazzband?

Sidenote for @mattseymour, I used to row w/ your COO. Small world.

[pauloxnet]

@jacobian thanks for your work here. I care about this packages and I'm also available to help maintaining it. I suggest too, to move this package to jazzband

[mattseymour]

So we should probably come up with a set of steps to get this moving.

• We should probably ping in @jezdez, and get the application to Jazzband organized.
• We need the following form completed in order to submit to Jazzband.
• The following would need to be submitted by @jacobian, when we are happy with the application.

Notes:

• Those who have expressed interest have been added to the project lead list. I looked through the user list and everyone seems to check out. There is no one on this thread I would be worried about giving access to the project too. (e.g. Account created yesterday, or dodgy project etc.)
• I have done a first pass at the proposal and description etc. Please modify and repost, I am not good at this sort of thing (I will not be offended).
• We would need to include the jazzband contribution and guidelines document. I will add these in a PR for review and link to this issue.

# Project Proposal

Please fill in the details below to confirm you adhere to the [Jazzband Guidelines](https://jazzband.co/about/guidelines), and also add the package name to the issue title.

## Project Details
Django Database urls is a popular package which allows developers to express a database connection as a URL. It is a very popular project with a wide user base.

Description from the readme of the project.
> This simple Django utility allows you to utilize the 12factor inspired `DATABASE_URL` environment variable to configure your Django application.

## Project Description
Dj-database-urls was moved to the ownership of @jacobian following the original package maintainer wanting to step back from the package. We now think this project will be better served under the @jazzband banner of projects where it can get the additional love and support it requires. 

## Project Leads
@mattseymour 
@scuerda 
@adamchainz
@ParthS007
@dcwatson 

## Confirmation of Guidelines

Please confirm the following:

- [ ] I am the project owner, or have permission from the project owner, to request a transfer.

- [ ] This project is a [viable candidate](https://jazzband.co/about/guidelines#viability) for Jazzband.

- [ ] This project fulfills the [documentation requirements](https://jazzband.co/about/guidelines#documentation).

- [ ] This project is [tested](https://jazzband.co/about/guidelines#tests).

- [ ] I am happy to adopt Jazzband's [code of conduct](https://jazzband.co/about/guidelines#conduct) in this project.

- [ ] I am happy to include Jazzband's [contributing guidelines](https://jazzband.co/about/guidelines#contributing-guidelines) in this project.

[jacobian]

Thanks all, I opened jazzband/help#267 to get the ball rolling.

[mattseymour]

So 2 months have gone by and things haven't progressed much further on the jazz-band side, I am thinking it would be good to try and review audit and sort out some of the issues on this repo.

@jacobian would you be happy giving me some enhanced permissions on this repo so I can start to tidy things up and sort out some of the PR's related to dj-database-urls. I am happy to have an offline chat if you would like.

[jezdez]

So 2 months have gone by and things haven't progressed much further on the jazz-band side, I am thinking it would be good to try and review audit and sort out some of the issues on this repo.

@jacobian would you be happy giving me some enhanced permissions on this repo so I can start to tidy things up and sort out some of the PR's related to dj-database-urls. I am happy to have an offline chat if you would like.

Welp, that's on me, I missed this ticket when I first glanced at https://github.com/jazzband/help/issues/267 in January, I've replied now there, giving the go-ahead.

[mattseymour]

@jezdez sorry, and thank you.

[jacobian]

Since @jezdez is 👍🏻 on moving this to Jazzband, I'm just gonna do that now. He can get everyone set up as maintainers over there. Lovely, thanks everyone!

[jacobian]

This is in Jazzband now, so I think we can call this resolved! There's still some work to be done probably but https://github.com/jazzband/help/issues/267 has the rest of it there. Bye y'all, thanks for everyone's help.