#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 cammil):
Of course I am not suggesting that we "just 'upgrade everything' ". What I
am asking is, if there is a better way to drive significant change -
better than a somewhat transactional ticketing approach, which has _not_
worked. My observation is not a novel one, and perhaps the cause of the
bloat is caused by a pure ticketing approach, or a lack of contributors,
or something else. Perhaps it is inevitable that a project of this size
and scope just simply had to be restarted in another form - FastApi, or
another. So, perhaps we are flogging a dead horse.
However, you have made a suggestion, and I have not tried it. So, let me
see if I can be more concrete with ask, or try to find those discussions
happening already in other tickets.
--
Ticket URL: <https://code.djangoproject.com/ticket/36771#comment:4>
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/0107019ae96af5b2-a67c0131-3001-497e-8fe1-e23f54719685-000000%40eu-central-1.amazonses.com.
