Re: GSOC 2015 project ideas suggestion

It still doesn't interest me enough to provide any additional feedback. On Thursday, March 26, 2015 at 1:20:42 AM UTC-4, Asif Saifuddin wrote: > > Hi, > > I have been updating my proposal and as the deadline is friday Your > feedback will help me to make it better in technical point of view > >

Re: GSOC 2015 project ideas suggestion

Hi, I have been updating my proposal and as the deadline is friday Your feedback will help me to make it better in technical point of view https://gist.github.com/auvipy/1da0d96f826bd8da4d47 Regards -- You received this message because you are subscribed to the Google Groups "Django

Re: GSOC 2015 project ideas suggestion

I have updated the proposal with what I'm planning to acheive in the program and updating with my analysis and plans to acheive the goal. still in draft and am editing according the goal I wanted to acheive/implement in this project proposal. -- You received this message because you are

Re: GSOC 2015 project ideas suggestion

I agree with Tim's assessment - this is not a compelling proposal at the moment. There is value in converting *some* of the function based views to CBVs, but unilaterally converting all of them doesn't seem especially worthwhile. The key thing is to identify what features need to be factored out.

Re: GSOC 2015 project ideas suggestion

Sorry, but to be honest I am not enthusiastic about this proposal. I'm not sure there's a great need or value in converting all function based views to class-based views. Your plans regarding django-extra-views and admin improvements have not been described in sufficient detail that give me a

Re: GSOC 2015 project ideas suggestion

Have a look. though rough draft and many place for improvment https://gist.github.com/auvipy/1da0d96f826bd8da4d47 On Mon, Mar 23, 2015 at 4:43 AM, Tim Graham wrote: > Please explain what you plan to implement in the other apps rather than > what's already been implemented

Re: GSOC 2015 project ideas suggestion

For the wont fix ticket I'm considering that to introduce django extra view like features in django will help fix many problem related to FormSet and ModelFormSet and then use them in improving django admin and possibly django-admin2 like features in django. On Monday, March 23, 2015 at

Re: GSOC 2015 project ideas suggestion

Please explain what you plan to implement in the other apps rather than what's already been implemented in contrib.auth. You'll also need to explain your reasoning for addressing a ticket that's been marked as "won't fix." On Sunday, March 22, 2015 at 4:36:26 PM UTC-4, Asif Saifuddin wrote: >

Re: GSOC 2015 project ideas suggestion

I do belive to implement auth patch cleanly wont take more then a few days. But I have plans with django admin app and others which will need more tasks and also thinking about working with formset . The part I posted here is just a very little/start point of my proposal :) And I am working on a

Re: GSOC 2015 project ideas suggestion

I see there's already a patch attached to the ticket that implements your proposal. While it likely needs to be updated to apply cleanly, I don't imagine that will take more than a few days? On Sunday, March 22, 2015 at 2:19:37 PM UTC-4, Asif Saifuddin wrote: > > Hi All, > > during my analyzing

Re: GSOC 2015 project ideas suggestion

Hi All, during my analyzing and making proposal for django best practices updates (class based view etc) I found this ticket related https://code.djangoproject.com/ticket/16256 [though closed by a core dev I think this should be addressed to resolve some issues in admin as per

Re: GSOC 2015 project ideas suggestion

Thanks a lot tim! that will be really helpful! On Wed, Mar 11, 2015 at 6:42 AM, Tim Graham wrote: > It's up to you to convince the value in your ideas. The more specific you > can be, the easier we'll be able to give feedback. Here's a related ticket > about using

Re: GSOC 2015 project ideas suggestion

It's up to you to convince the value in your ideas. The more specific you can be, the easier we'll be able to give feedback. Here's a related ticket about using class-based views in contrib.auth which may be helpful: https://code.djangoproject.com/ticket/17209 On Monday, March 9, 2015 at

Re: GSOC 2015 project ideas suggestion

About the best practice project idea I'm analyzing contrib apps. I found Admin docs app using class based views and probably it's almost up to date. for admin and some other apps there are no class based views used. for revamping django admin as a part of best practice update hoow about extending

Re: GSOC 2015 project ideas suggestion

I have seen that error on my own system Ubuntu 14.04 & Python 3.4.2 (installed from source), but didn't investigate the cause. I just installed Python 3.4.3, however, and don't have the problem there. Now I've reinstalled 3.4.2 and the error is resolved there as well. On Thursday, March 5,

Re: GSOC 2015 project ideas suggestion

Hi, running django test suite under python 3.4.3 on my ubuntu 14.10 produce the below output ERROR: test_extract_function (utils_tests.test_archive.TestBzip2Tar) -- Traceback (most recent call last): File

Re: GSOC 2015 project ideas suggestion

Thanks Russell. Investigating contrib apps I can see some are django apps using django framework and some are modules which is used to extend django frameworks functionality. For admin app theres is no use of urls.py for the admin app but admin_urls in template tags, admin_lists etc. isn't it

Re: GSOC 2015 project ideas suggestion

Hi Asif, The "Best Practices" project requires a bit of investigation on your part. The project description gives one suggestion (expanding the use of Class-based views), but essentially, pick any feature that has been added in the last 5 years, and see if Django is making good use of that

Re: GSOC 2015 project ideas suggestion

What about a built-in models.BitField ? Or a generic tagging function giving related items recommended by TF-IDF ? On Monday, February 23, 2015 at 4:01:11 AM UTC+11, Asif Saifuddin wrote: > > Seems my previous

Re: GSOC 2015 project ideas suggestion

Seems my previous idea is not well suited for gsoc right now. have to look for more convanient ideas then. what about best practise update? where will I get Ideas about what are considered as best practise in django 1.8/+? or other suggestions? Regards On Sun, Feb 22, 2015 at 6:36 AM, Russell

Re: GSOC 2015 project ideas suggestion

To my mind, the goal of this project isn't to replace Django's routing infrastructure - as Josh and Florian have pointed out, unless you can provide a backwards compatible interface as well as tangible API improvements, we're unlikely to adopt that code. However, there *would* be benefit in

Re: GSOC 2015 project ideas suggestion

To expand on Florians reply, why do you think replacing the routing infrastructure is a good idea? Is there any tangible benefit in doing so? Can you demonstrate that you can stay completely backwards compatible while realising those benefits? If there answer is no to benefits or backwards

Re: GSOC 2015 project ideas suggestion

Hi Aisf, while it theoretically would be possible to replace all of Django's request/response handling with Werkzeug, there is not much gain in it currently -- especially when considering backwards compatibility etc… Cheers, Florian On Saturday, February 21, 2015 at 9:14:27 PM UTC+1, Asif

Re: GSOC 2015 project ideas suggestion

Hi, Analyzing django code base docs and other tools I'm thinking of using werkzeug's routing infrastructure for developing django's one. django http mechanism can e re written using webOb/werkzeugs utilities too. this will need working django urlresolve, urls, middlewares, views, http and some

Re: GSOC 2015 project ideas suggestion

On Wed, Feb 4, 2015 at 1:49 AM, Asif Saifuddin wrote: > Thank you both for the feedback. I will continue my analysis to understand > django well and also try to contribute some patch on django if I can. > > > For django URL dispatcher improvement I am also looking for some >

Re: GSOC 2015 project ideas suggestion

Thank you both for the feedback. I will continue my analysis to understand django well and also try to contribute some patch on django if I can. For django URL dispatcher improvement I am also looking for some suggestions. Should I also look to some tool like werkzeug, webob along side django

Re: GSOC 2015 project ideas suggestion

On Mon, Feb 2, 2015 at 11:58 PM, Asif Saifuddin wrote: > Hi Fabio, > > Thank you for your project ideas. I'm going to follow the ideas from > https://code.djangoproject.com/wiki/SummerOfCode2015 > While this is definitely a safe option, don't rule out a

Re: GSOC 2015 project ideas suggestion

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

Re: GSOC 2015 project ideas suggestion

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

Re: GSOC 2015 project ideas suggestion

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

Re: GSOC 2015 project ideas suggestion

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

Re: GSOC 2015 project ideas suggestion

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

Re: GSOC 2015 project ideas suggestion

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 - "Complexity:" Hard

Re: GSOC 2015 project ideas suggestion

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

Re: GSOC 2015 project ideas suggestion

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]