Hi Josh,

There are two technical problems that need to be solved in order to make
this happen.

   - Implement the packaging definitions to allow for multiple packages.
   - Clean up dependencies between components. Despite the best of
   intentions, there are some interesting dependencies between modules, some
   of which may need to be clarified or separated.

The aim of this project would be to clean up one or more of Django's
internal "parts" so that it could be delivered as a standalone package.
This may not be something that can be immediately delivered - for example,
it may be necessary to move or rename components to enable separate
packaging. In this case, the project deliverable would be to document the
strategy, and provide whatever initial moves in that direction are possible.

A simpler version of this project would be to enable separate packaging and
distribution of Django's contrib apps.

alongside reduce tight coupling how should I approach to following part?

"A simpler version of this project would be to enable separate packaging
and distribution of Django's contrib apps."


I am looking for dev teams suggestions


./auvipy





On Mon, Feb 2, 2015 at 9:58 PM, Asif Saifuddin <auv...@gmail.com> wrote:

> Hi Fabio,
>
> Thank you for your project ideas. I'm going to follow the ideas from
> https://code.djangoproject.com/wiki/SummerOfCode2015
>
>
> for your babel porting probably Aymeric Augustin's template refactor
> project have some plan with babel integration, but I'm willing to work on
> reduce decoupling/Improve template dispatching for first priority from my
> side till now.
>
>
> Regards
>
> ./auvipy
>
> On Mon, Feb 2, 2015 at 9:39 PM, Fabio Caritas Barrionuevo da Luz <
> bna...@gmail.com> wrote:
>
>> Some ideas. (which still require approval of the core developers):
>>
>>
>> * Improve database backend base API and related features(including
>> introspection feature used by inspectdb), so that it is less complicated to
>> add in the future support the specific features of some backends. eg
>> multiple database schemas (common used in Oracle and PostgreSQL) and/or
>> Oracle synonym tables
>>
>> * port Django i18n and i10 and related translation features to use Babel:
>> http://babel.pocoo.org/
>>
>>
>>
>> Em terça-feira, 27 de janeiro de 2015 14:15:20 UTC-3, Asif Saifuddin
>> escreveu:
>>
>>> 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 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-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/cbb457c7-66cb-4370-99de-c9cfcd2a5622%40googlegroups.com
>> <https://groups.google.com/d/msgid/django-developers/cbb457c7-66cb-4370-99de-c9cfcd2a5622%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/CAKAqTgpmtLaNke2%3DaRC%2BPitvpdyfA_9uWdON%2BJc-5GTVTvJekQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to