Hi Jacob, Your explanations are rather right to understand the main hindrance to the success of this change. I personally tried some alternative django admins and even have some analysis with django admin internals too. I initially thought If I could start the work immediately then it could be done before 1.11 but from your previous experience now It's clear that it will take much longer time and dedication from multiple peoples.
I personally is willing to start the initial work's and will continue to communicate and push the works regularly myself. But for the money I don't have any initial source to manage It. I would dedicate my personal time to it and also manage volunteers from my country's python django community who got the ability to contribute to django. For the technical perspective can you guide/ show me any previous work/discussion/technical specs etc? I personally found django-admin2 internals quite modern and liked most of their approach. Though django have its own limitations of bc so I would like to hear from core members about the works right directions. I personally know about thing though. Another thing I want to know as I'm based on south asia, so if some time later the south asian developers participate then in future if serious funding is needed then it might be lesser expensive then other parts of the world as far I know. [don't get me wrong about the topic,] Thanks Asif On Thursday, May 26, 2016 at 2:16:53 AM UTC+6, Jacob Kaplan-Moss wrote: > > Hi Asif - > > I don't think a DEP is the right approach. The problem isn't a > controversial feature or a hard-to-design-API; it's that this is going to > take a lot of time or money, and probably both. Writing a DEP won't answer > the question of "how the heck are you going to find a half-dozen people who > can spend a year on this?" > > Or, let me ask this question in a different way. I did some analysis on > what it might cost to hire a team to build a new admin. I've worked as a > consultant, on similar tasks, so I have some experience costing our > projects like this. At market rates, I came up with over $1 million -- > which passes a sniff test given the effort involved. So to put a real point > on it: how are you going to raise that money, or find the equivalent level > of dedication from volunteers? > > If you want to see this happen, you need to answer these fundamental > question. And the way to answer it is *by doing it* -- write code, raise > money, build a team. Writing a DEP is going to be a waste of your time. > > I'm sorry if this sounds harsh, but I really want to make sure you > understand exactly what you're proposing here. If you want to be > successful, you need to demonstrate your ability to make progress where so > many others have tried and failed. > > Jacob > > On Wed, May 25, 2016 at 12:26 PM, Asif Saifuddin <auv...@gmail.com > <javascript:>> wrote: > >> Hi jacob, >> >> happy to see your insightful reply. I think I'm going to start the >> process with a draft dep soon and I'm planning to devote my engagement in >> the development too. >> >> Will keep you suggestions in mind :) >> >> thanks, >> >> Asif >> >> On Wednesday, May 25, 2016 at 2:45:42 PM UTC+6, Asif Saifuddin wrote: >>> >>> Hi, >>> the admin app of django is consists of many old day codes. How about >>> rewriting it with present day approaches? adopting ideas from django-admin2 >>> where possible? and how about using jinja2 templates as default for admin? >>> >>> thanks, >>> >>> asif >>> >> -- >> 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 <javascript:>. >> To post to this group, send email to django-d...@googlegroups.com >> <javascript:>. >> 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/38fc9cbb-d82a-4665-bab5-ba68b8249316%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/38fc9cbb-d82a-4665-bab5-ba68b8249316%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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4a5db986-1dfb-4b02-8e46-3943fc92ef17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
