Hi folks -
I’d like to gauge interest in adopting dj-database-url
) as an official project
This is my pre-proposal. I think dj-database-url is very widely-used, and
scratches a specific but annoying itch. Maintenance burden is minimal, but
What do other folks think? DEP 7 asks us to
> solicit feedback from the community and work out if there is rough agreement
> that the project is a good thing for Django to adopt, particularly focusing on
> any alternative approaches to the same problem and the relative merits of them,
> including code design, scalability, alignment with existing Django design and
> philosophy, and having an available development and maintenance team.
So - thoughts?
I'm volunteering to be the shepherd, but do intend to form a larger team.
I've also opened https://github.com/jacobian/dj-database-url/issues/120
as another place for this discussion. Please feel free to comment either
[Backstory, and why this is living on my github right now. @kennethreitz was
looking for a new maintainer, and reached out to me to see if Django might be
interested. I thought perhaps so, and offered to take over maintainership in the
meantime while we work through the DEP 7 process. If it turns out that an
Official Project is the wrong home for this, I'll either maintain it long-term
or transfer it again.]