#36771: Django needs a _massive_ refactor
-------------------------------------+-------------------------------------
     Reporter:  cammil               |                    Owner:  (none)
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Uncategorized        |                  Version:  6.0
     Severity:  Normal               |               Resolution:  invalid
     Keywords:  refactor             |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Jake Howard):

 Where would one start a discussion like this then?

 What discussion are you trying to have? You can't just "upgrade
 everything". If there's an area or feature you think could be improved,
 suggest it. There are lots of open issues in the new-features repo from
 people with similar concerns to you, but with a narrower scope and a more
 concrete plan. That's what's needed.

 Alternatively, if there are already open discussions there you have
 opinions on, contribute to the existing discussions there.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36771#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019ae8aed63f-e7977bb8-9c37-4521-b0b0-0e8ab2d92be7-000000%40eu-central-1.amazonses.com.

Reply via email to