> > 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. > > I was kind of thinking along the same lines. We aren't deploying packages and it won't be a critical piece of infrastructure to any users projects.
> 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. > Seems reasonable to me. > > 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. > > Yeah I feel the same here. Although it'd be nice to be able to do a simple `vagrant up` and get working on Django itself, it comes with quite a bit of overhead for everybody else. Having it hosted outside of the core repo means we can move at a different pace which is a good thing for a "newer" project. -- 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/fe6336a2-ba69-46a2-8b62-999690d8f9b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
