Hi One of the most difficult things for me while preparing my GSoC proposal was getting myself acquainted to Django's humungous code base. To prepare a proposal one should know what modules they would need to modify & what part of the code they will need to work with. To do that one should *at least* know what is the role of a particular module/file in the big picture of Django's code. For me, even though I had drilled down that I had to work just with django/db, I still had the task of figuring out the working of *so* many modules. There were *models.options, models.sql.query, models.sql.compiler, migrations.autodetector, migrations.loader, migrations.optimizer*, *backends.features*, *backends.introspection*, *backends.operations*, *backends.schema* and many more which were somehow connected to each other & doing something but I had no easy way to know what. I think putting an individual README to places like django/core/ <https://github.com/django/django/tree/master/django/core>, django/db/models <https://github.com/django/django/tree/master/django/db/models>/, etc. with even a 1-2 line description of what purpose each of the folder/file (or at least the convoluted ones) in that folder serve might be great help to newbie programmers - just not for GSoC but any new contributor. I understand that the work required to make this happen might be quite big and complex (maybe big enough to make it a GSoC project in itself, but Google doesn't accept purely documentation projects for GSoC IIRC) but might be achievable if merged in parts.
@Parth I am Django's GSoC fellow for 2016. If there is any way I could help you, feel free to reach me out <https://gist.github.com/akki/b438292c2c3cf199012f#5-about-me>. For other fellows, you can search for Django in the archives of GSoC's website <https://developers.google.com/open-source/gsoc/past-summers>. Also, a quick way to ask questions about contributing to Django from the community is the IRC channel #django-dev On Wednesday, 16 January 2019 21:33:55 UTC+7, Tim Graham wrote: > > Org applications for Google's Summer of Code are now open (deadline > February 6). Do you think the Django Software Foundation should participate? > > We haven't had any high quality student applications that we could accept > for the past two years. > > Perhaps it's partly a function of a poor ideas page ( > https://code.djangoproject.com/wiki/SummerOfCode2018). Perhaps we don't > do a great job of publicizing our involvement and attracting high quality > students. Perhaps it's because the student payment isn't all that much > (+/-$6000 USD, depending on student's country)* for the amount of work > involved (also, students have to put in a lot of work up front in their > application, with no guarantee of being accepted into the program). > > If you have any ideas about mentoring or suggesting a project, or if > you're serious about being a student (you should start contributing to > Django now if you don't already), please share. > > * https://developers.google.com/open-source/gsoc/help/student-stipends > -- 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 email@example.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/94246e44-0a18-492e-bae9-5c340c5734a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.