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> 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-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/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/CAK8PqJGNJOeAs1QX_5DLb%3D6H8ra8qsLiqrYLnegkE9G2XaEd5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to