Hi Mitchel, Thanks for submitting a proposal (and for starting the process earlier than 2 days before the deadline). You get extra credit for being ambitious and proposing something that isn't on the suggested projects list :-)
I have three concerns about this project: Firstly, what's the current state of the art for this? Django is a big community, and I'd be surprised if most (if not all) the issues associated with 12 factor haven't been addressed in multiple ways, by multiple people. There's definitely value in formalising and documenting that knowledge, but it isn't clear from this proposal that you're aware what others may have done in this space. To pick an obvious example - you mention integrating Grunt/Gulp: how does this part of your proposal compare to (or intend to leverage) django-compressor, django-pipeline, or any of the other static asset management tools that are out there? Secondly, are you intending to tackle all 12 factors, or just selected ones? My impression is that certain aspects of 12 factor are outside the scope of what Django as a project can enforce. Sure, there might be some fixes to make environment-based deploys easier, but a lot of 12 factor is either "well known best practice" (e.g., "use virtualenv and requirements.txt" is trivial to document, but doesn't require any code changes), specifically *can't* be developed as a general resource (e.g., Factor X) or are outside the scope of Django as a project (e.g., you need to have automated deployment tools - but do you pick chef, salt, ansible, puppet...) Lastly, looking at what I can see as being potentially on topic, I'm not sure I see 12 weeks of work. Most of what I see is documentation, not development, and while documentation is definitely worthwhile, a primarily documentation project is explicitly *not* in scope for GSOC. That said - it's entirely possible that I've missed the point, or have missed a significant body of development work that is required - in which case, I've just given you a hit list of things to you need to improve in your proposal for v2 :-) Yours, Russ Magee %-) On Sun, Mar 15, 2015 at 4:17 PM, Mitchel Cabuloy <[email protected]> wrote: > First of all, here's an incomplete draft of my proposal > <https://gist.github.com/mixxorz/3a34c61a7270d6fbe543>for Google Summer > of Code 2015. > > I'd like to receive some feedback about the idea. It's an obvious one, and > it's not very technical, but I just want to throw it out there. Would this > sort of project (which is probably going to be a third-party project) > applicable for GSoC? Thanks :) > > P.S. I'm Mitch and I'm a 4th year university student currently taking up > B.S. Computer Science with Specialization in Network Engineering at De La > Salle University in Manila. > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/ac044f01-60db-476e-985e-3f03070ff26e%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/ac044f01-60db-476e-985e-3f03070ff26e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84-%2BRUPnNgkw%2BV3W9O8awDeFsJNtLRQgcq6R%3Dy7siCvO%2Bw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
