I don't think a formal approval/proposal is needed to keep django box under the Django org. For example, tools to help with Django development don't require things like fixing security issues (I hope). As long as it's working as semi-maintained, we can add a link to it from the contributing docs. If it's neglected and becomes an embarrassment then we could remove it.
Hosting on atlas.hashicorp seems fine. If you create an account with some credentials you can share in case you stop maintaining it, that sounds good. I don't want to force any particular development workflow on anyone which is why I'm not thrilled with the idea of including this in the Django repo itself. It might give the impression that all new development work requires you to fix the box as well or if not, then we'll see later commits just fixing the box which sort of clutters Django's commit log. On Monday, August 29, 2016 at 9:07:13 AM UTC-4, Tim Allen wrote: > > I'd be happy to contribute configuration for connecting Django to SQL > Server. I've had to deploy this for some projects at work that don't (yet) > use PostgreSQL. This sounds like a fantastic tool for testing, as well as > examples for people just getting started; wiring up a database for the > first time can be a challenge, with many moving parts in several layers. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9d7d6ae9-dbcd-4f0b-b464-aba049ecc2f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
