I don't think there is enough time in GSOC to properly extract so many components into separate packages. I don't even know if this would be a long term goal for Django. Even if it were, there's more to it than just creating a new repository. Maintainers would have to put their hand up to manage the new repo. Testing and CI will have to be setup. Dependencies and release management would have to be looked at.
If this project interests you, I think you should investigate ways to reduce tight coupling whilst keeping the majority of components where they are. Examples of tight coupling include relying on global settings (settings.py/django.conf), various utils modules that are referenced from all over the code base, and knowledge of internal APIs across components. Some of the work that Aymeric has done with the Templates refactor in 1.8 is a good example of reducing tight coupling in a single component. - Josh On Sunday, 1 February 2015 20:21:19 UTC+11, Asif Saifuddin wrote: > > Hi, > > For the Reducing coupling of Django components project I have some broader > Aim and objectives in my which I am planning to propose. > > The main goal of this project proposal is to lay down the stepping stones > for reducing coupling in django internal components. To achieve the goal > > 1. Analyze and find out which components need to be included in django > proper and which need to be shipped in a different package. > > 2. There are Contrib Apps which are mainly django applications and can be > moved and evolved as different packages outside django repo. like > dj-admin/django-admin, django-gis/geodjango etc > > 3. Django ORM, Forms, Test, template this need work for moving as single > packages. Probably django-orm/django-db, django-forms etc. > > This are the basic objectives of my proposals in very brief. > > > I would like to propose more detail one with with technical details and > my plans to make this project success after having some feedback from core > dev teams. > > > Looking forward to some feedback if my initial move is okeyish? > > ./auvipy > > On Wed, Jan 28, 2015 at 2:19 PM, Asif Saifuddin <auv...@gmail.com > <javascript:>> wrote: > >> Hi, >> >> Thank you both of you for your response with guidelines. >> >> I found a old project >> Reducing coupling in Django components >> >> - *Complexity:* Hard >> >> >> and a newer project >> >> Improving URL dispatch >> <https://code.djangoproject.com/wiki/SummerOfCode2015#ImprovingURLdispatch> >> >> - "Complexity:" Hard >> >> >> Interests me. >> >> >> >> >> With the first project I have some concrete ideas on mind to share with >> technical aspects and my proposed terms to be reviewed by the core team. I >> will soon share my understanding and proposal about this project. >> >> With The second project I'm still not fully sure about the technical >> implementation and I need some more analysis to understand. >> >> >> ./auvipy >> >> On Wed, Jan 28, 2015 at 1:41 AM, Tim Graham <timog...@gmail.com >> <javascript:>> wrote: >> >>> I've created a wiki page for this year. It includes some ideas from past >>> years which may or may not still be relevant (I did some light editing). Of >>> course, you are welcome to propose something entirely different related to >>> your interests. >>> >>> https://code.djangoproject.com/wiki/SummerOfCode2015 >>> >>> On Tuesday, January 27, 2015 at 2:01:33 PM UTC-5, Marc Tamlyn wrote: >>>> >>>> Anything not done from previous years is likely to be suitable yes. >>>> >>>> It would also be very beneficial to familiarise yourself with the >>>> contributing guidelines for Django[1] and take on some small fixes, >>>> perhaps >>>> in related areas to your interests for GSOC. >>>> >>>> Marc >>>> >>>> [1] https://docs.djangoproject.com/en/1.7/internals/contributing/ >>>> >>>> On 27 January 2015 at 17:15, Asif Saifuddin <auv...@gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> Although probably It's quite very early to ask about GSOC 2015 in >>>>> January, I would like to start analyzing to prepare myself for choosing >>>>> a >>>>> correct project and submitting a good proposal for that to get selected. >>>>> I >>>>> haven't found any GSOC 2015 project ideas pages yet. But got some older >>>>> idea pages of year 2013 and 2014. Should I look forward to the ideas >>>>> that >>>>> were unimplemented or wait for gsoc 2015 wiki ideas page? >>>>> >>>>> ./auvipy >>>>> >>>>> -- >>>>> 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-develop...@googlegroups.com. >>>>> To post to this group, send email to django-d...@googlegroups.com. >>>>> 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/92f8aa3d-69da-4be2-af5a- >>>>> b2a0f55d616b%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/django-developers/92f8aa3d-69da-4be2-af5a-b2a0f55d616b%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 a topic in the >>> Google Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/django-developers/WF3My-cZNtY/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> django-develop...@googlegroups.com <javascript:>. >>> To post to this group, send email to django-d...@googlegroups.com >>> <javascript:>. >>> 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/cfe3dfff-2099-4715-a04c-f43c3120a6c3%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/django-developers/cfe3dfff-2099-4715-a04c-f43c3120a6c3%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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/ff71aaa1-904c-4f42-ab65-5ef896712eb2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
