If you really think you want to work on a deployment project, you should get the requirements together very quickly, so someone on this list can sanity check that it's something both feasible and useful.
I have done a **lot** of different deployments, and other than deploying to heroku, they have never been the same. I'm rather skeptical that some tool can be built for deploying a Django application that didn't already mimic an existing tool like Ansible or Salt (or Heroku CLI). Examples: what application server (gunicorn, uwsgi, mod_wsgi)? What web server (nginx, apache, caddy)? What database server, and is it remote or local? How are environment variables securely provisioned and deployed? Where is static content served from, and do you need S3 keys? How are you managing TLS certificates? Start a new thread on this list when you have an outline for what you want to do. At that stage we should be able to tell you if you should proceed with a detailed project scope or not. I don't want you to work on a detailed project scope and then get knocked back for the idea being infeasible. Remember, the project would need to be very useful for Django users. I'd also just like to call out that projects like Django Channels would likely be in scope too, provided the current maintainers felt comfortable mentoring a student. A quick note about Channels specifically - the current maintainers have **just** taken up that mantle, so you should have a specific idea in mind if that's what you're interested in, not ask the team for ideas. On Friday, 15 February 2019 20:53:34 UTC+11, Shashank shet wrote: > > That's a good idea. I'll start working on a draft for the deployment > support project. > > On Friday, February 15, 2019 at 2:58:45 PM UTC+5:30, Carlton Gibson wrote: >> >> The timeline for GSoC is here: >> https://summerofcode.withgoogle.com/how-it-works/#timeline >> >> Applications are ≈ a month away. >> >> Here's an example from a previous year: >> https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 >> >> I'd suggest drafting things in more detail and starting a new thread to >> invite discussion. >> >> I don't know what'll be suitable: it depends on the proposal: >> >> - something not in core? Yeah, maybe. >> - Something for deployment? Well, seems a bit ambitious, but again >> maybe... >> - Bringing the two(?) community Redis cache backends into one in core? >> Reasonable idea perhaps, yes. >> - A cross-db JSONField etc. Yep, great... >> >> ...and so on. What do you want to work on? >> >> >> -- 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/350d7430-5644-4faa-8019-6e0968e554f1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
